CDC Mortality (WONDER)
REMOTE · MCP.OLYPORT.COM
Leading causes of death, mortality rates, infant mortality, and drug overdose data
Available components
Last scanned (21 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 800 tokens (~160/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.olyport.com/cdc-wonder/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.olyport.com | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 54d0df51fa6c4f014f3cea8d4e2cde78ed1 |
| SANs: mcp.olyport.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.olyport.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| olyport.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.olyport.com/cdc-wonder/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.olyport.com/cdc-wonder/mcp | HTTPS enforced | 308 | https://mcp.olyport.com/cdc-wonder/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_drug_overdose_deaths ~152
Get provisional drug overdose death data by state. Returns provisional counts and rates of drug overdose deaths from the National Vital Statistics System (NVSS). Includes data on opioid, synthetic opioid, and other drug-involved deaths. Updated monthly. Args: state: Filter by state name (e.g. 'West Virginia', 'Ohio'). Case-insensitive. Returns all states if not specified. year: Filter by year. Returns all available years if not specified. limit: Maximum number of records to return (default 25, max 1000).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| state | string | – | – |
| year | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_infant_mortality ~130
Get infant mortality rates by state and race/ethnicity. Returns infant mortality data including rates per 1,000 live births, broken down by state and race/ethnicity. Infant mortality is a key indicator of community health status used in CHNAs. Args: state: Filter by state name (e.g. 'Ohio', 'Georgia'). Case-insensitive. Returns all states if not specified. year: Filter by year. Returns all available years if not specified.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | – |
| year | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_leading_causes_of_death ~178
Get leading causes of death with death counts and age-adjusted rates. Returns data from the NCHS Leading Causes of Death dataset, which provides national and state-level mortality statistics by cause of death, year, and age-adjusted death rate per 100,000 population. Data spans 1999-2017. Args: state: Filter by state name (e.g. 'California', 'Texas'). Case-insensitive. Returns all states if not specified. year: Filter by year (e.g. 2017). Returns all available years if not specified. limit: Maximum number of records to return (default 25, max 1000).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| state | string | – | – |
| year | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_mortality_by_state ~147
Compare mortality rates across states for a specific cause or all causes. Returns age-adjusted death rates by state, useful for comparing mortality burdens across geographies. Data from NCHS Leading Causes of Death. Args: cause: Cause of death to filter by (e.g. 'Heart disease', 'Cancer', 'Unintentional injuries', 'Alzheimer\'s disease'). Partial match supported. Returns all causes if not specified. year: Filter by year (e.g. 2017). Defaults to most recent available year if not specified.
| Name | Type | Req | Description |
|---|---|---|---|
| cause | string | – | – |
| year | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_provisional_mortality ~193
Get most recent provisional mortality data including COVID and other causes. Returns provisional death counts from the NVSS, covering major cause groups including COVID-19, respiratory diseases, circulatory diseases, and more. Data is updated weekly and covers the most recent periods. Args: state: Filter by state/jurisdiction name (e.g. 'New York', 'Florida'). Case-insensitive. Returns all jurisdictions if not specified. cause_group: Filter by cause group (e.g. 'COVID-19', 'Respiratory', 'Circulatory', 'Malignant neoplasms'). Partial match supported. Returns all cause groups if not specified. limit: Maximum number of records to return (default 50, max 1000).
| Name | Type | Req | Description |
|---|---|---|---|
| cause_group | string | – | – |
| limit | integer | – | – |
| state | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the CDC Mortality (WONDER) MCP server?
CDC Mortality (WONDER) is a hosted endpoint at https://mcp.olyport.com/cdc-wonder/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.olyport.com
claude mcp add --transport http com-olyport-cdc-wonder 'https://mcp.olyport.com/cdc-wonder/mcp'
What is the CDC Mortality (WONDER) MCP server?
CDC Mortality (WONDER) is an MCP server listed in the public MCP registry as com.olyport/cdc-wonder. Leading causes of death, mortality rates, infant mortality, and drug overdose data. This page covers its hosted endpoint (https://mcp.olyport.com/cdc-wonder/mcp).
Is the CDC Mortality (WONDER) MCP server safe to use?
CDC Mortality (WONDER) scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CDC Mortality (WONDER) MCP server expose?
CDC Mortality (WONDER) exposes 5 tools: get_leading_causes_of_death, get_mortality_by_state, get_infant_mortality, get_drug_overdose_deaths, get_provisional_mortality. Their descriptions and schemas cost roughly 800 tokens of context every time the server is loaded.
Does the CDC Mortality (WONDER) MCP server require authentication?
No. We connected to CDC Mortality (WONDER) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CDC Mortality (WONDER) MCP server still maintained?
CDC Mortality (WONDER) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CDC Mortality (WONDER) MCP server?
VerifyMCP ran 12 checks on CDC Mortality (WONDER), covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CDC Mortality (WONDER): Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.