M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionPaperGraph MCPRead math papers with evidence, not guesses.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS55 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Math-paper readers who need a strict separation between evidence and guesses
  • Researchers who want an AI agent to help map theorems and dependencies inside a local workspace
  • People who want reading artifacts as Markdown they can keep in Git or notes
  • Users who want to review external references before importing them
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • People expecting the tool to prove or verify mathematical correctness
  • Anyone wanting automatic infinite crawling of the citation chain (A cites B, B cites C)
  • Users needing semantic theorem matching or equivalence judgments for similarly worded results
  • Users with scanned or OCR-heavy PDFs where extraction may be sparse
  • Users who expect a full TeX engine for complex projects
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Read and write SQLite workspace files at user-chosen local paths
  • Read user-supplied local LaTeX projects and local PDF files
  • Download e-prints from arXiv's fixed e-print endpoint
  • Query public metadata services (Crossref, OpenAlex, arXiv) when the user runs a reference search
  • Write generated Markdown reports and manifest files into a user-specified artifact directory
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • The workspace stores text, source spans, and proof evidence extracted from papers, so committing databases or private manuscripts can leak content
  • The Scholarly Reference Resolver only searches public metadata and stops with explicit boundaries for ambiguous, old, paywalled, or metadata-only literature, requiring manual sourcing
  • An empty dependency result only means no resolvable theorem-label references were found under the current rule; it is not evidence that the theorem has no mathematical dependencies
  • Scanned PDFs may yield sparse text and missing evidence
  • The parser is not a full TeX engine, so complex projects may need an explicit main_file
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsMCP clients accepting JSON-style stdio configurationClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools5411