Home Health and Hospice Ratings (Care Compare) MCP
REMOTE · HOME-HEALTH-HOSPICE-RATINGS-CARE-COMPARE-MCP.LIPMICHAL.WORKERS.DEV
Medicare Care Compare ratings for home health agencies and hospices: stars, surveys, quality by ZIP.
Available components
Last scanned (14 hours ago)
Scores higher than 51% 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1124 tokens (~281/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.
- 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.
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://home-health-hospice-ratings-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 home-health-hospice-ratings-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://home-health-hospice-ratings-care-compare-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://home-health-hospice-ratings-care-compare-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 →
home_health_ratings Home health agency ratings and quality measures ~231
Full Medicare Care Compare profile of one home health agency by ccn (or name and state): quality of patient care star rating with the state and national median, patient survey stars and the four survey topics with state and national percentages, would definitely recommend, 13 quality measures (timely start of care, improvement in walking, bathing, breathing and taking medicines, falls with major injury, pressure ulcers, discharge function, flu shot check) against state and national averages, discharge to community and preventable hospital readmissions and hospitalizations against the national rate, Medicare spending per episode, number of ZIP codes served, services and the Medicare.gov link. A missing value carries the CMS footnote that explains it.
| Name | Type | Req | Description |
|---|---|---|---|
| ccn | string | – | CMS certification number (6 characters, from the search tool). Preferred when known. |
| city | string | – | City of the agency office, to narrow a name lookup. |
| name | string | – | Agency name or part of it, used when no ccn is given. |
| state | string | – | State name or two-letter code, to narrow a name lookup. |
No output schema declared.
No examples provided.
home_health_search Find and rank home health agencies ~284
Find Medicare-certified home health agencies that serve a ZIP code (as reported to Medicare), or that have an office in a state or city, or by name, ranked by the CMS quality of patient care star rating (1 to 5 in half stars), patient survey (HHCAHPS) stars or name. Each result has both star ratings, the share of patients rating it 9 or 10 and who would recommend it, services offered (nursing, physical, occupational and speech therapy, medical social services, home health aide), ownership, phone and the ccn for home_health_ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City of the agency office (needs no ZIP). |
| limit | integer | – | How many agencies to return. Default 15. |
| min_stars | number | – | Minimum quality of patient care star rating (half stars allowed). |
| name | string | – | Agency name or part of it. |
| services | array | – | Only agencies offering all of these services. |
| sort | string | – | quality (default), patient_survey or name. |
| state | string | – | State name or two-letter code (all agencies in the state, or narrows a ZIP or city search). |
| zip | string | – | 5-digit ZIP code of the patient's home: lists every agency that serves it. Best for "near me" questions. |
No output schema declared.
No examples provided.
hospice_ratings Hospice ratings and quality measures ~234
Full Medicare Care Compare profile of one hospice by ccn (or name and state): family caregiver survey star rating and the seven survey results (communication, timely help, respect, emotional support, help with pain and symptoms, rating 9 or 10, would recommend) against state and national averages, comprehensive assessment at admission, nurse or social worker visits in the last days of life, the Hospice Care Index score and its 10 indicators with national percentiles (live discharges, nursing visit gaps, nurse minutes, spending per beneficiary), average daily census, diagnosis mix, where care is given (home, assisted living, nursing facility) and ZIP codes served. A missing value carries the CMS footnote that explains it.
| Name | Type | Req | Description |
|---|---|---|---|
| ccn | string | – | CMS certification number (6 characters, from the search tool). Preferred when known. |
| city | string | – | City of the agency office, to narrow a name lookup. |
| name | string | – | Agency name or part of it, used when no ccn is given. |
| state | string | – | State name or two-letter code, to narrow a name lookup. |
No output schema declared.
No examples provided.
hospice_search Find and rank hospices ~274
Find Medicare-certified hospices that serve a ZIP code (as reported to Medicare), or that have an office in a state, city or county, or by name, ranked by the family caregiver survey (CAHPS Hospice) star rating, the Hospice Care Index or name. Each result has the family survey stars (or the reason there are none), the share of caregivers rating it 9 or 10 and who would definitely recommend it, the Hospice Care Index (0 to 10), ownership, phone and the ccn for hospice_ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City of the hospice office. |
| county | string | – | County of the hospice office (needs state). |
| limit | integer | – | How many hospices to return. Default 15. |
| min_stars | integer | – | Minimum family caregiver survey star rating. |
| name | string | – | Hospice name or part of it. |
| sort | string | – | family_rating (default: stars, then would recommend), care_index or name. |
| state | string | – | State name or two-letter code (all hospices in the state, or narrows a ZIP, city or county search). |
| zip | string | – | 5-digit ZIP code where care is needed: lists every hospice that serves it. Best for "near me" questions. |
No output schema declared.
No examples provided.
How do I install the Home Health and Hospice Ratings (Care Compare) MCP server?
Home Health and Hospice Ratings (Care Compare) MCP is a hosted endpoint at https://home-health-hospice-ratings-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 · home-health-hospice-ratings-care-compare-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-home-health-hospice-ratings-care- 'https://home-health-hospice-ratings-care-compare-mcp.lipmichal.workers.dev/mcp'
What is the Home Health and Hospice Ratings (Care Compare) MCP server?
Home Health and Hospice Ratings (Care Compare) MCP is listed in the public MCP registry as io.github.theluckystrike/home-health-hospice-ratings-care-c…. Medicare Care Compare ratings for home health agencies and hospices: stars, surveys, quality by ZIP. This page covers its hosted endpoint (https://home-health-hospice-ratings-care-compare-mcp.lipmichal.workers.dev/mcp).
Is the Home Health and Hospice Ratings (Care Compare) MCP server safe to use?
Home Health and Hospice Ratings (Care Compare) MCP scores 66 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 Home Health and Hospice Ratings (Care Compare) MCP server expose?
Home Health and Hospice Ratings (Care Compare) MCP exposes 4 tools: home_health_search, home_health_ratings, hospice_search, hospice_ratings. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.
Does the Home Health and Hospice Ratings (Care Compare) MCP server require authentication?
No. We connected to Home Health and Hospice Ratings (Care Compare) MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Home Health and Hospice Ratings (Care Compare) MCP server still maintained?
Home Health and Hospice Ratings (Care Compare) 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 Home Health and Hospice Ratings (Care Compare) MCP server?
VerifyMCP ran 12 checks on Home Health and Hospice Ratings (Care Compare) 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 Home Health and Hospice Ratings (Care Compare) 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.