What tools does the cdc-health-mcp-server MCP server provide?

cdc-health-mcp-server exposes 4 tools: cdc_discover_datasets, cdc_get_dataset_schema, cdc_query_dataset, cdc_query_wonder. This list was returned by the running server when we connected to it.

Does cdc-health-mcp-server require an API key?

No. cdc-health-mcp-server answered a tools/list request without credentials.

How do I install cdc-health-mcp-server?

Run: claude mcp add --transport http cdc-health-mcp-server https://cdc.caseyjhand.com/mcp. One-click install links for Cursor and VS Code are also available on the server's page.

Connection check verified live · 27h ago

cdc-health-mcp-server

Search and query CDC public health data — mortality, vaccinations, surveillance, behavioral risk.

Databases & SQL Web search & scraping Code & repositories

Install

Remote (HTTP)

claude mcp add --transport http cdc-health-mcp-server https://cdc.caseyjhand.com/mcp

Tools 4

GitHub stars 5

Installs / wk 192

Licence Apache-2.0

Transport streamable-http, stdio

Last checked 27h ago

Tools & capabilities

4 tools

Read from the running server on 27h ago.

cdc_discover_datasets read-only tagslimitorderquerydomainoffset +1

Search the CDC dataset catalog by keyword, category, or tag. Returns IDs, names, truncated descriptions, asset types, column counts, and update timestamps. The catalog also holds c…

cdc_get_dataset_schema read-only domaindatasetId*column_limitcolumn_offset

Fetch the column schema for a CDC dataset — names, data types, descriptions, row count, and last-updated timestamp. Returns the first 100 columns by default; wide datasets continue…

cdc_query_dataset read-only grouplimitorderwheredomainhaving +4

Execute a SoQL query against any CDC dataset. Supports filtering, aggregation, sorting, full-text search, and field selection. Use cdc_discover_datasets to find dataset IDs and cdc…

cdc_query_wonder read-only sexlimitoffsetdatabasegroup_bymcd_icd10 +3

Query CDC WONDER for national US mortality statistics — deaths, population, and crude/age-adjusted death rates — across its five mortality databases, selected with the database inp… Query CDC WONDER for national US mortality statistics — deaths, population, and crude/age-adjusted death rates — across its five mortality databases, selected with the database input: final underlying-cause data for 1999–2020 (the default) or 2018–2024, provisional data running from 2018 through the current year, and two multiple-cause databases covering the same two eras. Break results out by year, age group, sex, and/or race, and filter by ICD-10 cause of death, sex, age group, or year range; on a multiple-cause database, mcd_icd10 additionally matches a cause listed anywhere on the death certificate rather than only the one certified as underlying. Each database holds a different span of years (1999–2026 across all of them) and a request whose year_range falls outside the selected one's span is rejected with that span named. WONDER is a separate CDC system from the Socrata datasets the other cdc_* tools query. Data is national only — sub-national (state/county) breakdowns are not available through the API (CDC vital-statistics policy). Cause of death is a filter, not a grouping. Some measure cells come back as a CDC status token rather than a number — "Suppressed" (withheld for confidentiality), "Unreliable" (a rate from fewer than 20 deaths), or "Not Applicable" (no population denominator); those cells read null in rows and each one is listed in cellNotes with its token. CDC also drops whole rows before sending the table — strata with zero deaths, and strata whose death count is suppressed — so a stratum can be missing from rows entirely; messages carries CDC's statement whenever that happened. The whole table comes back by default; a broad grouping can run past a thousand rows, so set limit to take it a page at a time and follow the nextOffset the response reports. Paging shapes the response only — WONDER is asked once either way, and the figures, caveats and hidden-row notices are the same on every page. CDC rejects requests made less than 15 seconds apart across all five databases, so consecutive calls are spaced automatically and a follow-up call may wait about 16 seconds before it runs.