MCP server for academic papers, citations, authors, ECOS dossiers, and Federal Register text.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"paper-chaser": {
"env": {
"PAPER_CHASER_ENABLE_CORE": "false",
"PAPER_CHASER_ENABLE_ARXIV": "true",
"PAPER_CHASER_TOOL_PROFILE": "guided",
"PAPER_CHASER_HIDE_DISABLED_TOOLS": "true",
"PAPER_CHASER_ENABLE_SEMANTIC_SCHOLAR": "true"
},
"args": [
"-m",
"paper_chaser_mcp"
],
"command": "python"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for academic papers, citations, authors, ECOS dossiers, and Federal Register text.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@modelcontextprotocol/inspector' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
MCP Inspector is Vulnerable to Potential Command Execution via XSS When Connecting to an Untrusted MCP Server
An XSS flaw exists in the MCP Inspector local development tool when it renders a redirect URL returned by a remote MCP server. If the Inspector connects to an untrusted server, a crafted redirect can inject script into the Inspector context and, via the built-in proxy, be leveraged to trigger arbitrary command execution on the developer machine. Version 0.16.6 hardens URL handling/validation and prevents script execution. > Thank you to the following researchers for their reports and contributi
MCP Inspector proxy server lacks authentication between the Inspector client and proxy
Versions of MCP Inspector below 0.14.1 are vulnerable to remote code execution due to lack of authentication between the Inspector client and proxy, allowing unauthenticated requests to launch MCP commands over stdio. Users should immediately upgrade to version 0.14.1 or later to address these vulnerabilities. Credit: Rémy Marot <bughunters@tenable.com>
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in education / search
Web and local search using Brave Search API
Production ready MCP server with real-time search, extract, map & crawl.
Multi-engine MCP server, CLI, and local daemon for agent web search and content retrieval — skill-guided workflows, no API keys.
MCP server for Firecrawl — search, scrape, and interact with the web. Supports both cloud and self-hosted instances. Features include web search, scraping, page interaction, batch processing, and LLM-powered content analysis.
MCP Security Weekly
Get CVE alerts and security updates for io.github.joshuasundance-swca/paper-chaser-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Release status: The repository, CLI, Docker image metadata, and public MCP identity are now aligned on
paper-chaser-mcp. GHCR images and GitHub Release assets are the primary public distribution channels; PyPI remains intentionally gated until account recovery and trusted-publisher setup are complete.
An MCP server for academic research — search papers, chase citations, look up authors, repair broken references, explore species dossiers, and retrieve regulatory text, all from one FastMCP server that AI assistants can call directly.
Providers: Semantic Scholar · arXiv · OpenAlex · CORE · SerpApi Google Scholar (opt-in, paid) · Crossref · Unpaywall · ECOS · FederalRegister.gov · GovInfo
Paper Chaser MCP is now guided-first: the default public surface is designed to be hard to misuse and explicit about trust.
research handles discovery, known-item
recovery, citation repair, and regulatory routing in one trust-graded path,
with a server-owned quality-first policy for guided use.follow_up_research answers against one saved
searchSessionId; if you omit it, the server only infers a session when the
choice is unique. Saved-session follow-up can classify mixed source sets into
on-topic evidence, weaker context, and off-target leads when the stored
metadata is already sufficient.executionProvenance, and
ambiguous follow-up or source-inspection flows return structured
sessionResolution / sourceResolution payloads instead of opaque errors.resolve_reference handles DOI/arXiv/URL,
citation fragments, and regulatory-style references, and exact DOI/arXiv/
paper-URL inputs resolve as exact anchors rather than falling through to fuzzy repair.
Ambiguous title-only or conflicting metadata matches can now return
multiple_candidates or needs_disambiguation; treat those as candidate
anchors, not citation-ready resolutions.research leads with a short
recommendation-first summary, while keeping the structured evidence,
leads, and provenance fields available below it.inspect_source exposes one sourceId with
provenance, trust state, weak-match rationale, and quality-aware direct-read next steps; omitted searchSessionId
is only accepted when one compatible saved session exists.get_runtime_status surfaces active profile/transport and
provider-state warnings wi