CDC MMWR Reports
REMOTE · MCP.OLYPORT.COM · SCANNED SEP 20
Morbidity and Mortality Weekly Reports and disease surveillance
Available components
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 4 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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 446 tokens (~111/item across 4 items; 4 tools + 0 resources), lean.Pass
- 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the CDC MMWR Reports MCP server?
CDC MMWR Reports is a hosted endpoint at https://mcp.olyport.com/cdc-mmwr/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-mmwr 'https://mcp.olyport.com/cdc-mmwr/mcp'
{
"mcpServers": {
"com-olyport-cdc-mmwr": {
"url": "https://mcp.olyport.com/cdc-mmwr/mcp"
}
}
} {
"servers": {
"com-olyport-cdc-mmwr": {
"type": "http",
"url": "https://mcp.olyport.com/cdc-mmwr/mcp"
}
}
} [mcp_servers.com-olyport-cdc-mmwr] url = "https://mcp.olyport.com/cdc-mmwr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-olyport-cdc-mmwr": {
"type": "remote",
"url": "https://mcp.olyport.com/cdc-mmwr/mcp",
"enabled": true
}
}
} openclaw mcp add com-olyport-cdc-mmwr --url 'https://mcp.olyport.com/cdc-mmwr/mcp' --transport streamable-http
mcp_servers:
com-olyport-cdc-mmwr:
url: "https://mcp.olyport.com/cdc-mmwr/mcp" {
"McpServers": {
"com-olyport-cdc-mmwr": {
"Transport": "http",
"Url": "https://mcp.olyport.com/cdc-mmwr/mcp"
}
}
} assistant mcp add com-olyport-cdc-mmwr -t streamable-http -u 'https://mcp.olyport.com/cdc-mmwr/mcp'
{
"mcpServers": {
"com-olyport-cdc-mmwr": {
"type": "http",
"url": "https://mcp.olyport.com/cdc-mmwr/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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 20 Sept 2026 · Probed https://mcp.olyport.com/cdc-mmwr/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=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6ab1c2dfb0fcb68c1046393bb51c5b1117b |
| SANs: mcp.olyport.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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. | present | 19718 | 13 | Verified |
| olyport.com. | absent | 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-mmwr/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.olyport.com/cdc-mmwr/mcp | HTTPS enforced | 308 | https://mcp.olyport.com/cdc-mmwr/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_disease_surveillance ~116
Get current surveillance data for a notifiable disease from MMWR/CDC. Searches recent MMWR articles for surveillance reports and case counts related to a specific notifiable disease. Useful for tracking disease trends, outbreak reports, and current epidemiological data. Args: disease: Name of the disease (e.g. 'measles', 'tuberculosis', 'salmonella', 'pertussis', 'hepatitis A').
| Name | Type | Req | Description |
|---|---|---|---|
| disease | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_recent_reports ~107
Get recent MMWR weekly reports and recommendations from CDC. Returns the most recent Morbidity and Mortality Weekly Report articles published by the CDC, including titles, publication dates, and PubMed IDs. MMWR is the CDC's primary vehicle for scientific publication of timely, reliable, and authoritative public health information. Args: limit: Maximum number of reports to return (default 20, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_report_detail ~98
Get the full abstract and metadata of an MMWR article by PubMed ID. Returns the complete abstract, authors, publication date, volume/issue, and any MeSH subject headings. Use PMIDs from search_mmwr or get_recent_reports results. Args: pmid: PubMed ID of the MMWR article (e.g. '38271059').
| Name | Type | Req | Description |
|---|---|---|---|
| pmid | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_mmwr ~125
Search MMWR articles by topic via PubMed. Searches the Morbidity and Mortality Weekly Report journal for articles matching your query. Use for finding CDC guidance, outbreak reports, surveillance summaries, and public health recommendations. Args: query: Search terms (e.g. 'COVID-19 vaccine effectiveness', 'influenza surveillance', 'measles outbreak 2024'). limit: Maximum number of results to return (default 20, max 100).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the CDC MMWR Reports MCP server?
CDC MMWR Reports is an MCP server listed in the public MCP registry as com.olyport/cdc-mmwr. Morbidity and Mortality Weekly Reports and disease surveillance. This page covers its hosted endpoint (https://mcp.olyport.com/cdc-mmwr/mcp).
Is the CDC MMWR Reports MCP server safe to use?
CDC MMWR Reports 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 MMWR Reports MCP server expose?
CDC MMWR Reports exposes 4 tools: get_recent_reports, search_mmwr, get_report_detail, get_disease_surveillance. Their descriptions and schemas cost roughly 446 tokens of context every time the server is loaded.
Does the CDC MMWR Reports MCP server require authentication?
No. We connected to CDC MMWR Reports without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CDC MMWR Reports MCP server still maintained?
CDC MMWR Reports is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.