clinicaltrialsgov-mcp-server and medical-mcp
The MCP servers are complementary, with A specializing in ClinicalTrials.gov data and B providing broader medical information from multiple authoritative APIs, suggesting they could be used together to enrich LLM capabilities for healthcare data interoperability.
About clinicaltrialsgov-mcp-server
cyanheads/clinicaltrialsgov-mcp-server
MCP server for the ClinicalTrials.gov v2 API. Allow LLMs to search trials, retrieve study details, compare studies, analyze trends, and match patients to eligible trials.
Implements 7 tools spanning search, results extraction, and patient matching via a type-safe client for ClinicalTrials.gov REST API v2, with features like geographic proximity filtering, results summary mode (~200KB→5KB compression), and eligibility matching from patient demographics. Built on the MCP TypeScript framework with dual stdio/HTTP transport, pluggable auth, and structured error handling with exponential backoff retry logic. Available as npm package, Docker image, or public HTTP endpoint requiring zero setup.
About medical-mcp
JamesANZ/medical-mcp
An MCP server that provides comprehensive medical information by querying multiple authoritative medical APIs including FDA, WHO, PubMed, Google Scholar, and RxNorm
Implements an in-memory caching layer with source-specific TTL policies (FDA: 24h, PubMed: 1h, WHO: 7d, RxNorm: 30d) and LRU eviction to reduce API latency from 800-1500ms to <10ms. Runs as a Node.js/TypeScript MCP server compatible with Cursor and Claude Desktop, requiring zero API keys while querying live FDA, WHO, PubMed, RxNorm, Google Scholar, and AAP endpoints with specialized tools for drug nomenclature, health statistics, clinical literature, and pediatric guidelines.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work