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.

DimensionPerplexity API PlatformReal-time search, reasoning, and research through Perplexity's API.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS64 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • AI assistants that need real-time web search
  • Users needing Perplexity Agent API research and reasoning capabilities
  • Developers using MCP-compatible client tools
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Local tasks that do not need internet or an external API
  • Environments without a Perplexity API key
  • Immediate-use scenarios that cannot wait for research runs lasting several minutes
  • 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 access to PERPLEXITY_API_KEY
  • Requires network access to the Perplexity API and the internet
  • HTTP deployments may require network binding and host, origin, and port configuration
  • 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 must be configured through the environment and should not be exposed.
  • Setting BIND_ADDRESS to 0.0.0.0 exposes the HTTP service on all network interfaces.
  • Setting ALLOWED_ORIGINS to * permits cross-origin browser requests from any origin.
  • Deep research runs may take minutes and may require a higher timeout.
  • 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 Code, Codex, Cursor, Claude Desktop, Kiro, Windsurf, VS CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools411