# 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.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp)

## Channel facts

- Endpoint: `https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-nursing-home-ratings-medicare-car 'https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-nursing-home-ratings-medicare-car": {
      "url": "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-nursing-home-ratings-medicare-car": {
      "type": "http",
      "url": "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-nursing-home-ratings-medicare-car]
url = "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-nursing-home-ratings-medicare-car": {
      "type": "remote",
      "url": "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-nursing-home-ratings-medicare-car --url 'https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-nursing-home-ratings-medicare-car:
    url: "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-nursing-home-ratings-medicare-car": {
      "Transport": "http",
      "Url": "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-nursing-home-ratings-medicare-car -t streamable-http -u 'https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-nursing-home-ratings-medicare-car": {
      "type": "http",
      "url": "https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +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.

### 2026-11-19 (score 66, +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.

### 2026-11-18 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 65)

First indexed and scored.

## MCP tools (3)

### `nursing_home_search` (~333 tokens)

Find and rank nursing homes

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.

Input parameters:

- `city` (string): City or town (use with state).
- `county` (string): County or parish (needs state).
- `exclude_abuse_icon` (boolean): Leave out facilities CMS flags with the abuse icon.
- `exclude_special_focus` (boolean): Leave out Special Focus Facilities and candidates.
- `latitude` (number): Latitude to search around (with longitude).
- `limit` (integer): How many facilities to return, 1 to 50. Default 15.
- `longitude` (number): Longitude to search around (with latitude).
- `min_overall_rating` (integer): Only facilities with at least this many overall stars.
- `name` (string): Part of the facility name.
- `radius_miles` (number): Radius around the ZIP or point, 1 to 50 miles. Default 10.
- `sort` (string): Sort order. Default overall (ties by inspections, staffing, then distance).
- `state` (string): State as a two-letter code (VT) or name (Vermont).
- `zip` (string): 5-digit ZIP code to search around.

### `nursing_home_ratings` (~243 tokens)

Nursing home ratings and inspection record

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.

Input parameters:

- `ccn` (string): CMS Certification Number (6 characters, e.g. 475014), from nursing_home_search. Most exact.
- `city` (string): City, to narrow a name match.
- `deficiencies` (integer): How many of the most recent cited deficiencies to list, 0 to 50. Default 10.
- `name` (string): Facility name or part of it, if no ccn.
- `state` (string): State as a two-letter code (VT) or name (Vermont).

### `nursing_home_compare` (~95 tokens)

Compare nursing homes

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.

Input parameters:

- `facilities` (array, required): 2 to 5 facilities, each as {ccn} or {name, state}.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65

## 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.

## Links

- Remote endpoint: https://nursing-home-ratings-medicare-care-compare-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/nursing-home-ratings-medicare-care-compare-mcp
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-nursing-home-ratings-medicare-care-compare-mcp/nursing-home-ratings-medicare-care-compare-mcp
