Measles Cases by State and Outbreak MCP
REMOTE · MEASLES-CASES-BY-STATE-OUTBREAK-MCP.LIPMICHAL.WORKERS.DEV
US measles cases by state, outbreak count, hospitalizations, weekly trend and MMR rates from CDC.
Available components
Last scanned (15 hours ago)
Scores higher than 52% 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
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 656 tokens (~164/item across 4 items; 4 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 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
- Authorization
- 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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 66
First indexed and scored.
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://measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebf145553d5751d20e0d3cd51e3d7a94 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev/mcp | Inconclusive | 405 |
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 →
measles_cases_by_state Measles cases by state ~160
Confirmed measles cases by state from CDC. With a state: its cases this year, last year and the year before, its rank, and its kindergarten MMR coverage. Without a state: every state ranked by cases this year and the states with none. New York City is reported separately from the rest of New York State; "NY" adds both.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | State name or two-letter code, "New York City", "New York State" or "DC". Omit for all states. |
| top | integer | – | How many states to list in the summary when no state is given. Default 15. |
| year | integer | – | Year, one of the last three. Default the current year. |
No output schema declared.
No examples provided.
measles_cases_history Measles cases history ~136
US measles case history from CDC. view yearly (default): confirmed cases per year from 1985 to this year, with the highest and lowest year in the range. view weekly: cases per week by rash onset for one year (2022 on), monthly totals, the peak week and the recent trend.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | integer | – | yearly: first year. Default 2000. |
| to_year | integer | – | yearly: last year. Default the current year. |
| view | string | – | yearly (default) or weekly. |
| year | integer | – | weekly: the year. Default the current year. |
No output schema declared.
No examples provided.
measles_cases_us US measles cases this year ~106
Confirmed US measles cases for this year (or 2025) from CDC: the total, the number of outbreaks and the share of cases that are outbreak-associated, jurisdictions with cases, cases by age, vaccination status, percent hospitalized, deaths, the previous year for comparison and the trend over the last complete weeks.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Year. Default the current year. Full breakdowns exist for this year and last year; earlier years give the total only. |
No output schema declared.
No examples provided.
mmr_vaccination_rates Kindergarten MMR vaccination rates ~144
Kindergarten MMR vaccination coverage (2 doses) from CDC. With a state: its rate for the latest or a given school year, its rank, the change since 2019-20 and the trend. Without a state: every state ranked from lowest, how many are below the 95% herd immunity target, and the state median. School years 2009-10 to the latest.
| Name | Type | Req | Description |
|---|---|---|---|
| school_year | string | – | School year such as 2025-26 (or 2025). Default the latest. |
| state | string | – | State name or code, "New York City" or "Houston". Omit for all states. |
No output schema declared.
No examples provided.
How do I install the Measles Cases by State and Outbreak MCP server?
Measles Cases by State and Outbreak MCP is a hosted endpoint at https://measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev/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 · measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-measles-cases-by-state-outbreak-m 'https://measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev/mcp'
What is the Measles Cases by State and Outbreak MCP server?
Measles Cases by State and Outbreak MCP is listed in the public MCP registry as io.github.theluckystrike/measles-cases-by-state-outbreak-mcp. US measles cases by state, outbreak count, hospitalizations, weekly trend and MMR rates from CDC. This page covers its hosted endpoint (https://measles-cases-by-state-outbreak-mcp.lipmichal.workers.dev/mcp).
Is the Measles Cases by State and Outbreak MCP server safe to use?
Measles Cases by State and Outbreak MCP scores 68 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 Measles Cases by State and Outbreak MCP server expose?
Measles Cases by State and Outbreak MCP exposes 4 tools: measles_cases_us, measles_cases_by_state, measles_cases_history, mmr_vaccination_rates. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.
Does the Measles Cases by State and Outbreak MCP server require authentication?
No. We connected to Measles Cases by State and Outbreak MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Measles Cases by State and Outbreak MCP server still maintained?
Measles Cases by State and Outbreak MCP 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 Measles Cases by State and Outbreak MCP server?
VerifyMCP ran 12 checks on Measles Cases by State and Outbreak MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Measles Cases by State and Outbreak MCP: HTTPS. 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.