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.

DimensionOpenConnectorConnect once. Use everywhere.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS52 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation13 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Agent products that need access to many SaaS, developer, data, or communication services
  • Teams that need inspectable Action request and response contracts
  • Developers and teams that want control over credentials and runtime deployment
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Simple integrations that need only one service and no connector gateway
  • Users who require a documented list of specific MCP tool identifiers or client integrations
  • Users who do not want to manage credentials, deployment, or runtime configuration
  • 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
  • API keys, OAuth clients, and provider-specific scopes may need to be configured
  • The runtime may require connections, runtime tokens, and Action allow or block policies
  • Required permissions depend on the connected provider and executed Action
  • 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
  • Connected third-party accounts may let an agent access or modify user data
  • Incorrect scopes, Action policies, or runtime-token settings may broaden access
  • Credentials, transit files, and run logs must be protected in the deployment environment; logs support redaction but still require review
  • Third-party provider APIs, permissions, and availability can affect execution results
  • 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, Codex, Other MCP stdio clients
Tools011