Skip to content
External endpointresponds

cdc-health-mcp-server

MCP server for discovering and querying CDC public health datasets via the Socrata SODA API.

Endpoint URL
https://cdc.caseyjhand.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:00 AM UTC
Check
MCP initialize · 8s limit
Latency
368 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.cyanheads/cdc-health-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
cdc-health-mcp-server
Version
0.8.4
Capability keys
logging, resources, tools, prompts
Tool names
cdc_discover_datasets, cdc_get_dataset_schema, cdc_query_dataset, cdc_query_wonder
Instructions excerpt

Use the cdc_* tools to access CDC public health data. Most tools query the CDC Open Data portal (~1,080 datasets) via the Socrata SODA API: search the catalog, inspect dataset schemas, and run SoQL queries across vaccinations, behavioral risk, surveillance, and other domains. Datasets are addressed by four-by-four IDs (e.g. bi63-dtpu); the catalog is heterogeneous, so the workflow is discover → inspect schema → query. All Socrata values come back as strings, and a column like "year" may be numeric in one dataset and text in another — match WHERE literals to the actual dataType from the schema. Separately, cdc_query_wonder queries CDC WONDER — a different CDC system — for national mortality statistics (deaths, population, crude/age-adjusted rates), grouped by year/age/sex/race and filtered by ICD-10 cause; its database input selects one of five mortality databases (final and provisional, underlying-cause and multiple-cause) covering 1999 through the current year. It is nationa

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 · 147ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 401ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 290ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 368ms