F
licenseB
qualityD
maintenanceProvides access to the ClinicalTrials.gov API, enabling search, analysis, and retrieval of clinical trial data through MCP tools.
17
8
-
mcp-clinical-doc-agent
Related Servers
Alternatives to mcp-clinical-doc-agent
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables biomedical research workflows via MCP, including experiment and document search, PDF text extraction, evidence retrieval, and validation with provenance tracking.10MIT
- FlicenseNot gradedqualityDmaintenanceAnalyzes clinical trial site feasibility, enrollment velocity, eligibility criteria, and benchmark performance across ClinicalTrials.gov's registry via a structured MCP interface.-
- FlicenseNot gradedqualityCmaintenanceEnables searching a synthetic healthcare document repository and saving validated document metadata through MCP tools.-
- AlicenseAqualityCmaintenanceClinical research MCP server providing real-time access to PubMed (35M+ papers) and ClinicalTrials.gov (400K+ trials). Built for trial coordinators and life sciences teams. No API key required.33MIT
- AlicenseNot gradedqualityBmaintenanceEnables clinical workflows including search and summarization of synthetic FHIR patient records, PubMed literature search, and HIPAA Safe Harbor de-identification of text, via any MCP client.MIT
TDQS
A4.3/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: listing documents, extracting entities, clustering adverse events, and summarizing protocols. No overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case (e.g., cluster_adverse_events, extract_entities), making them predictable and easy to distinguish.
Tool Count5/5
With 4 tools, the server is well-scoped for its purpose of clinical document analysis. Each tool fills a necessary role without redundancy or excessive granularity.
Completeness4/5
The set covers key functions: discovery, entity extraction, AE clustering, and summarization. Minor gaps exist (e.g., no search or cross-protocol comparison), but core workflows are supported.
Maintenance
ActivityInactive
ResponsivenessNo issues