Skip to content
External endpointresponds

clinicaltrialsgov-mcp-server

MCP server for ClinicalTrials.gov v2 API. Search, retrieve, compare, and analyze trials.

Endpoint URL
https://clinicaltrials.caseyjhand.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
365 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.cyanheads/clinicaltrialsgov-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
clinicaltrialsgov-mcp-server
Version
2.8.5
Capability keys
logging, resources, tools, prompts
Tool names
clinicaltrials_search_studies, clinicaltrials_get_study_record, clinicaltrials_get_study_count, clinicaltrials_get_field_values, clinicaltrials_get_field_definitions, clinicaltrials_get_study_results, clinicaltrials_find_eligible
Instructions excerpt

Use the clinicaltrials_* tools to access the ClinicalTrials.gov registry — public, read-only, ~577K studies. Studies are addressed by NCT ID (NCT followed by 8 digits). Field names for the fields, advancedFilter, and sort parameters are PascalCase leaves (NCTId, OverallStatus, EnrollmentCount) — call clinicaltrials_get_field_definitions to discover them and clinicaltrials_get_field_values for valid enum values. Typical workflow: clinicaltrials_search_studies (pass fields to trim ~70KB records) → clinicaltrials_get_study_record → clinicaltrials_get_study_results (only when hasResults=true). Use clinicaltrials_get_study_count for cheap breakdowns and clinicaltrials_find_eligible for patient matching.

Reported Aug 17, 2026, 05:00 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 109ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 622ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 264ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 365ms