F
licenseNot graded
qualityD
maintenanceEnables searching and retrieving detailed clinical trial information from ClinicalTrials.gov via the official API.
1
-
Clinical Trials MCP Server
Related Servers
Alternatives to Clinical Trials MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables searching clinical trials, retrieving trial details, matching patient profiles to recruiting trials, and extracting eligibility criteria from ClinicalTrials.gov.-
- FlicenseNot gradedqualityDmaintenanceEnables searching and retrieving information from the ClinicalTrials.gov database of over 400,000 clinical studies, including trial details, eligibility criteria, locations, and results across 220+ countries.5-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve clinical trial data from ClinicalTrials.gov, supporting filters, study details, metadata, and statistics.-
- FlicenseBqualityDmaintenanceProvides access to the ClinicalTrials.gov API, enabling search, analysis, and retrieval of clinical trial data through MCP tools.178-
- AlicenseBqualityDmaintenanceProvides programmatic access to ClinicalTrials.gov API with 18 specialized tools for searching, analyzing, and retrieving detailed information about 400,000+ clinical trials worldwide, including filtering by condition, location, phase, sponsor, eligibility criteria, and outcomes.178 npm4MIT
TDQS
B3.3/5.0
Scored across 3 tools
Disambiguation4/5
The three tools have distinct primary purposes: get_trial_details retrieves comprehensive information for a specific trial, search_by_location focuses on geographic proximity, and search_clinical_trials provides general keyword-based searching. However, there is some overlap between the two search tools, as both can filter by location and return similar result sets, which could cause minor confusion for agents.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case: get_trial_details, search_by_location, and search_clinical_trials. The naming is predictable and readable, with clear action-object relationships throughout the set.
Tool Count3/5
With only three tools, the server feels thin for a clinical trials domain that typically involves complex queries and data retrieval. While the tools cover key functions, the count is borderline low, as agents might expect additional operations like filtering by status, saving searches, or accessing trial phases and outcomes more granularly.
Completeness3/5
The tool set covers basic retrieval and searching, but there are notable gaps for a clinical trials server. For example, there are no tools for updating trial information, managing user preferences, accessing historical data, or handling more advanced analytics. The surface is functional but incomplete for comprehensive agent workflows in this domain.
Maintenance
ActivityInactive
ResponsivenessNo issues