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.

DimensionExa MCP ServerExa's official MCP server for web search and crawling built for AI applicationsBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS73 / 100 · B75 / 100 · B
Reliability12 / 2010 / 20
Security and permissions13 / 2016 / 20
Maintenance16 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience16 / 2014 / 20
Best for
  • Q&A and research scenarios that need real-time, clean web content
  • Users with an existing Exa account who want a zero-deployment remote option
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Scenarios requiring a strict allowlist of search sources that can't use a third-party search service
  • Budget-sensitive, high-volume search scenarios (remote/API calls may incur cost)
  • 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 an Exa API key for full functionality; OAuth login is optional in remote mode
  • web_fetch_exa retrieves content from a specified URL; agent_run performs multi-step autonomous actions and needs the user to have clear expectations of Agent behavior
  • 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 API key should be stored carefully — avoid leaving it in plaintext in client config files on untrusted machines
  • agent_run is a multi-step autonomous tool with a longer action chain — try it on low-risk tasks first
  • 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 Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, AntigravityClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools411