← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionPaper Search MCPMCP server for searching and downloading academic papers from multiple sourcesBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS62 / 100 · C75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Researchers needing to search and download papers from multiple open-access sources
  • Developers wanting to integrate paper retrieval into MCP clients like Claude Desktop
  • Cost-conscious users who prefer free public data sources
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users needing full features from commercial databases (e.g., IEEE, ACM)
  • Users requiring complete full-text downloads without configuring optional API keys or proxies (some sources are limited)
  • Users running in environments without network access or strict firewalls
  • 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
  • Requires network access to call multiple academic APIs
  • May need to write to the local filesystem to download PDFs
  • Optional environment variables for API keys, stored in the user config 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
  • Dependency on external API stability; some sources may fail due to upstream limitations
  • Google Scholar may trigger bot detection and require proxy settings
  • Use of Sci-Hub carries legal and policy risks; users are responsible
  • 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 clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools211