Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hospital Ratings and CMS Star Ratings MCP

REMOTE · HOSPITAL-RATINGS-CMS-STAR-RATINGS-MCP.LIPMICHAL.WORKERS.DEV

CMS hospital star ratings, patient survey stars and ER wait times for US hospitals (Care Compare).

67 Trust /100

Last scanned (19 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 674 tokens (~224/item across 3 items; 3 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 3 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
What we tested

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 →

Changelog

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 65

    First indexed and scored.

Diagnostics

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://hospital-ratings-cms-star-ratings-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 hospital-ratings-cms-star-ratings-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://hospital-ratings-cms-star-ratings-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://hospital-ratings-cms-star-ratings-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~560 tokens

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 →

Tool Tokens
hospital_compare ~104

Compare 2 to 5 hospitals side by side on CMS overall stars, patient survey stars, the share of patients rating it 9 or 10 and who would recommend it, ER median time, left before being seen, sepsis care and mortality, safety and readmission measures better or worse than national. Names which hospital leads each.

NameTypeReqDescription
hospitalsarrayyes2 to 5 hospitals, each { facility_id } or { name, state } (city optional).

No output schema declared.

No examples provided.

hospital_ratings ~218

Full CMS Care Compare ratings for one hospital (by facility id, or name with state or city): overall star rating with the reason when unrated; how many mortality, safety and readmission measures are better, no different or worse than the national rate; HCAHPS patient survey stars overall and by topic (nurses, doctors, cleanliness, quiet, discharge), share rating it 9 or 10 and who would recommend it against national; ER median time from arrival to leaving, left without being seen, sepsis care and staff flu vaccination, each against the state and national average.

NameTypeReqDescription
citystring–City. Narrows a name lookup.
facility_idstring–CMS facility id (CCN), 6 characters such as 220071. Best when known (hospital_search returns it).
namestring–Hospital name or part of it, such as "Mass General" or "Brigham and Women's".
statestring–State code or name. Narrows a name lookup.

No output schema declared.

No examples provided.

hospital_search ~238

Find US hospitals by state, city, county, ZIP code (5 digits, or a 3-digit prefix for the area) or name, with each hospital's CMS overall star rating (1 to 5), HCAHPS patient survey summary stars, type, ownership and ER availability. Best rated first, with the count at each star level. Filter by type, minimum stars or emergency services.

NameTypeReqDescription
citystring–City, such as Boston.
countystring–County (needs state), such as Suffolk.
emergency_servicesboolean–Only hospitals with an emergency department.
hospital_typestring–Hospital type. Default all.
limitinteger–How many hospitals to list, 1 to 50. Default 20.
min_starsinteger–Only hospitals with at least this overall star rating.
namestring–Part of the hospital name.
statestring–State code or name, such as MA or Massachusetts.
zipstring–ZIP code (02114) or a 3-digit ZIP prefix for the surrounding area (021).

No output schema declared.

No examples provided.

Install

How do I install the Hospital Ratings and CMS Star Ratings MCP server?

Hospital Ratings and CMS Star Ratings MCP is a hosted endpoint at https://hospital-ratings-cms-star-ratings-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 · hospital-ratings-cms-star-ratings-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-hospital-ratings-cms-star-ratings 'https://hospital-ratings-cms-star-ratings-mcp.lipmichal.workers.dev/mcp'
Common questions

What is the Hospital Ratings and CMS Star Ratings MCP server?

Hospital Ratings and CMS Star Ratings MCP is listed in the public MCP registry as io.github.theluckystrike/hospital-ratings-cms-star-ratings…. CMS hospital star ratings, patient survey stars and ER wait times for US hospitals (Care Compare). This page covers its hosted endpoint (https://hospital-ratings-cms-star-ratings-mcp.lipmichal.workers.dev/mcp).

Is the Hospital Ratings and CMS Star Ratings MCP server safe to use?

Hospital Ratings and CMS Star Ratings MCP scores 67 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 Hospital Ratings and CMS Star Ratings MCP server expose?

Hospital Ratings and CMS Star Ratings MCP exposes 3 tools: hospital_search, hospital_ratings, hospital_compare. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

Does the Hospital Ratings and CMS Star Ratings MCP server require authentication?

No. We connected to Hospital Ratings and CMS Star Ratings MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Hospital Ratings and CMS Star Ratings MCP server still maintained?

Hospital Ratings and CMS Star Ratings 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 Hospital Ratings and CMS Star Ratings MCP server?

VerifyMCP ran 12 checks on Hospital Ratings and CMS Star Ratings 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 Hospital Ratings and CMS Star Ratings 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.