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.

DimensionClinicalTrials.gov MCP ServerSearch ClinicalTrials.gov trials, retrieve study details and results, and match patients to eligible trials via MCP.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS60 / 100 · C75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Clinical researchers
  • Healthcare professionals
  • Patient navigators
  • AI agents needing access to clinical trial data
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Not an official source for clinical trials; it's a wrapper for ClinicalTrials.gov
  • Does not provide medical advice
  • Not suitable for use with data sources other than ClinicalTrials.gov API
  • 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
  • No API keys required; uses the public API
  • May require network access to reach the hosted instance or install packages
  • If self-hosting, may require permissions to execute and run on your system
  • 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
  • Reliance on the ClinicalTrials.gov API, which may change or become unavailable
  • Data fetched from the API may be incomplete or outdated
  • Fuzzy matching in search may return irrelevant trials
  • Public hosted instance may be rate-limited or have privacy concerns
  • 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, Cursor, VS CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools711