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.

Nursing Home Ratings MCP

REMOTE · NURSING-HOME-RATINGS-MEDICARE-CARE-COMPARE-MCP.LIPMICHAL.WORKERS.DEV

Medicare Care Compare nursing home star ratings, staffing, inspections and fines for US facilities.

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 Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 790 tokens (~263/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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 0
    • 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://nursing-home-ratings-medicare-care-compare-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 nursing-home-ratings-medicare-care-compare-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://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp Verified 200
http (plaintext) http://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~671 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
nursing_home_compare ~95

Compare 2 to 5 nursing homes side by side from CMS Care Compare: the four star ratings, nurse and RN hours per resident per day, staff turnover, health deficiencies in the latest inspection cycle, fines, abuse icon and Special Focus status, with the leader on each measure and the state averages.

NameTypeReqDescription
facilitiesarrayyes2 to 5 facilities, each as {ccn} or {name, state}.

No output schema declared.

No examples provided.

nursing_home_ratings ~243

Full CMS Care Compare profile of one nursing home by ccn (or name and state): overall, health inspection, staffing and quality measure star ratings (long-stay and short-stay) with the CMS footnote that explains a blank or 1-star rating, nurse and RN staffing hours per resident per day and weekend staffing against state and US averages, nursing staff and RN turnover, the last inspections, recent cited deficiencies with scope and severity (actual harm, immediate jeopardy), fines and payment denials of the last 3 years, abuse icon, Special Focus status, ownership, chain and the Medicare.gov link.

NameTypeReqDescription
ccnstring–CMS Certification Number (6 characters, e.g. 475014), from nursing_home_search. Most exact.
citystring–City, to narrow a name match.
deficienciesinteger–How many of the most recent cited deficiencies to list, 0 to 50. Default 10.
namestring–Facility name or part of it, if no ccn.
statestring–State as a two-letter code (VT) or name (Vermont).

No output schema declared.

No examples provided.

nursing_home_search ~333

Find Medicare and Medicaid certified nursing homes near a ZIP code (default 10 miles) or latitude and longitude, or in a city, county or state, or by name, ranked by CMS overall star rating (or inspection, staffing, quality, nurse hours, distance or name). Each result has the four star ratings, beds, ownership, nurse hours per resident per day, staff turnover, fines, the abuse icon, Special Focus Facility status and the ccn for nursing_home_ratings.

NameTypeReqDescription
citystring–City or town (use with state).
countystring–County or parish (needs state).
exclude_abuse_iconboolean–Leave out facilities CMS flags with the abuse icon.
exclude_special_focusboolean–Leave out Special Focus Facilities and candidates.
latitudenumber–Latitude to search around (with longitude).
limitinteger–How many facilities to return, 1 to 50. Default 15.
longitudenumber–Longitude to search around (with latitude).
min_overall_ratinginteger–Only facilities with at least this many overall stars.
namestring–Part of the facility name.
radius_milesnumber–Radius around the ZIP or point, 1 to 50 miles. Default 10.
sortstring–Sort order. Default overall (ties by inspections, staffing, then distance).
statestring–State as a two-letter code (VT) or name (Vermont).
zipstring–5-digit ZIP code to search around.

No output schema declared.

No examples provided.

Install

How do I install the Nursing Home Ratings MCP server?

Nursing Home Ratings MCP is a hosted endpoint at https://nursing-home-ratings-medicare-care-compare-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 · nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev

# add to Claude Code
claude mcp add --transport http theluckystrike-nursing-home-ratings-medicare-car 'https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp'
Common questions

What is the Nursing Home Ratings MCP server?

Nursing Home Ratings MCP is listed in the public MCP registry as io.github.theluckystrike/nursing-home-ratings-medicare-care…. Medicare Care Compare nursing home star ratings, staffing, inspections and fines for US facilities. This page covers its hosted endpoint (https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp).

Is the Nursing Home Ratings MCP server safe to use?

Nursing Home 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 Nursing Home Ratings MCP server expose?

Nursing Home Ratings MCP exposes 3 tools: nursing_home_search, nursing_home_ratings, nursing_home_compare. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.

Does the Nursing Home Ratings MCP server require authentication?

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

Is the Nursing Home Ratings MCP server still maintained?

Nursing Home 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 Nursing Home Ratings MCP server?

VerifyMCP ran 12 checks on Nursing Home 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 Nursing Home 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.