SNF Register: nursing home owners, CMS ratings and HUD 232 loans
REMOTE · HUDSKILLEDNURSING.LOAN
US nursing home owners, CMS ratings and matched HUD 232 loans, plus a 232 refinance sizer.
Available components
Last scanned (16 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1910 tokens (~318/item across 6 items; 6 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 Management10
- Stability observed for 3 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 4 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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 68
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 5 Nov 2026 · Probed https://hudskillednursing.loan/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hudskillednursing.loan | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 575431cbac14decd0e2956f0d7762c12 |
| SANs: hudskillednursing.loan | ||||||
| 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 hudskillednursing.loan. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| loan. | DS published | 61084 | 8 | Verified |
| hudskillednursing.loan. | 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://hudskillednursing.loan/mcp | Verified | 200 | |
| http (plaintext) | http://hudskillednursing.loan/mcp | HTTPS enforced | 301 | https://hudskillednursing.loan/mcp |
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 →
get_nursing_home Nursing home record: ratings, owners and HUD loan ~141
One nursing home's SNF Register record by CCN: CMS beds, occupancy, star ratings, staffing hours and turnover, fines, ownership type and chain; the owners and operators it reported to CMS, private equity or REIT flags, changes of ownership; and its matched FHA-insured HUD 232 loans with note rate, balance, maturity and servicer.
| Name | Type | Req | Description |
|---|---|---|---|
| ccn | string | yes | Six-character CMS certification number (CCN), e.g. "015109". search_nursing_homes returns it. |
| max_owners | integer | – | Owners and operators to list, 1 to 60 (largest records run to 100+). |
No output schema declared.
No examples provided.
get_state_nursing_homes Nursing homes in a state: supply, quality, owners, HUD 232 ~122
A state's (or the US) nursing home roll-up: CMS-certified facilities and beds, median occupancy, star-rating spread, median nurse hours and turnover, for-profit, nonprofit and government counts, chain share, PE and REIT flags, recent ownership changes, Special Focus count, and HUD 232 loan activity. Omit state for the US.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | US state, DC, PR or GU: two-letter code (e.g. TX) or full name (e.g. "Texas"). Omit for the US. |
No output schema declared.
No examples provided.
list_hud_232_nursing_home_loans HUD Section 232 loans on nursing homes ~361
FHA-insured HUD Section 232 loans matched to CMS-certified nursing homes: facility, CCN, HUD project name, program, endorsement date and amount, status, note rate, balance, monthly P&I, maturity and servicer. Filter by state, CCN, name or city, servicer, status, rate range or maturity year; sort by balance, rate, maturity or endorsement.
| Name | Type | Req | Description |
|---|---|---|---|
| ccn | string | – | Six-character CMS certification number (CCN), e.g. "015109". search_nursing_homes returns it. |
| limit | integer | – | Loans to return, 1 to 50. |
| matures_by | integer | – | Only active loans maturing in or before this year. |
| max_rate | number | – | Only loans with a note rate at or below this percent. |
| min_rate | number | – | Only loans with a note rate at or above this percent, e.g. 5. |
| name | string | – | Part of the facility name, HUD project name or city, e.g. "Civic Center". |
| offset | integer | – | Skip this many loans (paging). |
| servicer | string | – | Part of the servicer or holder name, e.g. "Berkadia" (active loans). |
| sort | string | – | balance (largest first), rate (highest first), maturity (soonest first), endorsed (newest first). |
| state | string | – | US state, DC, PR or GU: two-letter code (e.g. TX) or full name (e.g. "Texas"). Omit to search every state. |
| status | string | – | Loan status in HUD's insured-mortgage files. Default active. |
No output schema declared.
No examples provided.
rank_states_nursing_homes Rank states by nursing home supply, quality, ownership or HUD 232 ~130
Ranks the states, DC, PR and GU on one nursing home measure: facilities, beds, median occupancy, nurse or RN hours, staff turnover, for-profit or chain share, PE or REIT owner flags, recent ownership changes, Special Focus count, or HUD 232 activity (active loans, balance, endorsements). Returns value, rank and state page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | States to return, 1 to 53. |
| metric | string | yes | What to rank by. |
| order | string | – | desc = largest first (default), asc = smallest first. |
No output schema declared.
No examples provided.
search_nursing_homes Find CMS-certified nursing homes ~260
Searches the 14,000+ CMS-certified nursing homes by name, city or state and returns each match's CCN, name, city, state, certified beds, CMS overall star rating, whether an FHA-insured HUD 232 loan is matched (active, past or none) and its SNF Register page. Use the CCN with get_nursing_home.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City, e.g. "Birmingham". |
| hud_loan | string | – | Only facilities with an active matched FHA loan, a past one only, or none. Default any. |
| limit | integer | – | Results to return, 1 to 50. |
| min_stars | integer | – | Only facilities with at least this CMS overall star rating. |
| offset | integer | – | Skip this many results (paging). |
| query | string | – | Part of the facility name as CMS lists it, e.g. "Civic Center" or "Good Samaritan". |
| sort | string | – | name (A to Z, default) or beds (largest first). |
| state | string | – | US state, DC, PR or GU: two-letter code (e.g. TX) or full name (e.g. "Texas"). |
No output schema declared.
No examples provided.
size_hud_232_refinance Size a HUD 232 nursing home refinance (223(f) or 223(a)(7)) ~527
Runs the SNF Register sizer: HUD Section 232 loan tests (debt service at 1.45x or 1.11x with MIP, 80%/85% loan to value, cost to refinance, original principal for 223(a)(7)) on your NOI, value, rate and payoff; returns the maximum insurable loan, the binding test, payment, MIP, DSCR and cash to close. Pass a CCN to fill in its active FHA loan.
| Name | Type | Req | Description |
|---|---|---|---|
| appraised_value | number | – | Appraised value, $. Required for 223f. |
| beds | integer | – | Beds (sets the 223f inspection fee). Default the CCN's certified beds, else 120. |
| borrower | string | – | Nonprofit with an operating track record gets 85% LTV instead of 80%. |
| ccn | string | – | Six-character CMS certification number (CCN), e.g. "015109". search_nursing_homes returns it. |
| current_monthly_pi | number | – | 223a7 only: current monthly principal and interest, to show the payment change. Defaults from ccn. |
| financing_fee_pct | number | – | Lender financing fee, % of loan (capped at 3.5% for 223f, 2% for 223a7). Default 2. |
| ground_rent | number | – | Annual ground rent, $. |
| noi | number | yes | Underwritten net operating income, $ a year. |
| original_principal | number | – | 223a7 only: original principal of the FHA loan (caps the new loan). Defaults from ccn. |
| other_costs | number | – | Other closing costs, $ (third-party reports, legal, title, prepayment premium). |
| payoff | number | – | Existing debt to pay off, $. Defaults to the active FHA balance when ccn is given. |
| program | string | – | 223f = 232/223(f) refinance of non-HUD debt; 223a7 = streamlined refinance of an existing FHA loan. Default 223a7 when ccn has an active FHA loan, else 223f. |
| rate_pct | number | yes | Interest rate, percent (your quote or assumption; HUD does not set it). |
| repairs | number | – | Repairs to finance, $. |
| term_years | integer | – | Term in years. Default 35, or the active loan's remaining term for 223a7 with ccn. |
No output schema declared.
No examples provided.
How do I install the SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server?
SNF Register: nursing home owners, CMS ratings and HUD 232… is a hosted endpoint at https://hudskillednursing.loan/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 · hudskillednursing.loan
claude mcp add --transport http loan-hudskillednursing-hudskillednursing-loan 'https://hudskillednursing.loan/mcp'
What is the SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server?
SNF Register: nursing home owners, CMS ratings and HUD 232… is an MCP server listed in the public MCP registry as loan.hudskillednursing/hudskillednursing-loan. US nursing home owners, CMS ratings and matched HUD 232 loans, plus a 232 refinance sizer. This page covers its hosted endpoint (https://hudskillednursing.loan/mcp).
Is the SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server safe to use?
SNF Register: nursing home owners, CMS ratings and HUD 232… scores 69 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 SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server expose?
SNF Register: nursing home owners, CMS ratings and HUD 232… exposes 6 tools: search_nursing_homes, get_nursing_home, get_state_nursing_homes, list_hud_232_nursing_home_loans, rank_states_nursing_homes, size_hud_232_refinance. Their descriptions and schemas cost roughly 1,541 tokens of context every time the server is loaded.
Does the SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server require authentication?
No. We connected to SNF Register: nursing home owners, CMS ratings and HUD 232… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server still maintained?
SNF Register: nursing home owners, CMS ratings and HUD 232… is still listed as active in the MCP registry. We last reached this channel on 5 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 SNF Register: nursing home owners, CMS ratings and HUD 232… MCP server?
VerifyMCP ran 13 checks on SNF Register: nursing home owners, CMS ratings and HUD 232…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.