Hospital price-transparency machine-readable file index
REMOTE · REFERENCESOURCE.ORG
Where is a US hospital's CMS price-transparency file? The URL, quoted from its own cms-hpt.txt.
Available components
Last scanned (23 hours ago)
Scores higher than 56% 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 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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 985 tokens (~328/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 Management17
- Stability observed for 5 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 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.
- 20 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.
- 18 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.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 69
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://referencesource.org/mcp/hospitals
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=referencesource.org | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 284c538e5c38c80d0eb8e23b1bba01ab |
| SANs: referencesource.org | ||||||
| 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 referencesource.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| referencesource.org. | 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://referencesource.org/mcp/hospitals | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp/hospitals | HTTPS enforced | 301 | https://referencesource.org/mcp/hospitals |
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 →
list_hospitals_on_domain List every hospital a health system's cms-hpt.txt declares ~207
Which hospitals does this health system publish prices for? Give a domain ("mercy.net", "www.adventhealth.com", or a URL on it) and get every location its root cms-hpt.txt names, each with its machine-readable file URL, its public page and the line it was read from. This is how the files are actually published — one cms-hpt.txt can declare eighty-six hospitals — so it is the right call when you know the system but not the exact location name. With no domain it lists the 73 domains this register covers, with a count for each.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | The health system's domain. Scheme, "www." and any path are ignored, so "https://www.mercy.net/billing" and "mercy.net" are the same system. Omit it to list the domains covered. |
| limit | integer | – | How many locations to return, 1–20. Default 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| domains_covered | array | – | Returned instead of hospitals when no domain was given. |
| hospitals | array | – | – |
| locations_matched | integer | – | – |
| locations_returned | integer | – | – |
| note | string | – | – |
| register | object | yes | – |
No examples provided.
resolve_hospital_mrf Find a hospital's price-transparency machine-readable file ~243
Where is this hospital's CMS standard-charges machine-readable file? Give a hospital name or part of one ("Prisma Health Richland", "Pennsylvania Hospital", "Abbott Northwestern") and get the file URL, the hospital's public price-transparency page, the health-system domain whose cms-hpt.txt declared it, and the verbatim line it was read from. Punctuation and case are ignored when matching. Hospital names are not unique — 64 names in this register belong to more than one hospital — so this returns a list and the domain tells them apart. Use list_hospitals_on_domain when you know the system rather than the hospital.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional health-system domain to narrow by, e.g. "mercy.net" or "https://www.mercy.net". Use it when a name matched more than one hospital. |
| limit | integer | – | How many to return, 1–20. Default 20. |
| name | string | yes | Hospital name or part of one. Case- and punctuation-insensitive; exact matches are returned first, then names starting with it, then names containing it. |
| Name | Type | Req | Description |
|---|---|---|---|
| hospitals | array | yes | – |
| hospitals_matched | integer | yes | – |
| hospitals_returned | integer | – | – |
| name | string | yes | – |
| note | string | – | – |
| register | object | – | – |
No examples provided.
verify_quote Check a claimed hospital file URL against the register ~238
Is this right? Check a claim about a hospital's price-transparency file — the machine-readable file URL, the public page, the domain — against the register instead of trusting it. Says whether the claim matches a stored value, appears only in the verbatim source quote, or differs (and then what the register says instead), and returns the source and quote so it can be traced upstream. Use it on a URL a model produced from memory: these URLs are long, they rot, and a plausible wrong one is indistinguishable from a right one until it is checked.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_value | string | yes | The value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29". |
| domain | string | – | Optional health-system domain, needed when the name belongs to more than one hospital (64 names in this register do). |
| field | string | – | Which field the claim is about, if you know it. Without it, every stored field of the record is checked. |
| hospital | string | yes | The hospital name the claim is about, as resolve_hospital_mrf returns it. |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | – |
| claimed_value | string | yes | – |
| in_source_quote | boolean | – | – |
| match | object | – | – |
| quote_source | string | – | – |
| record | object | – | – |
| stored_values | object | – | – |
| verdict | string | yes | matches_record: the claim equals a stored value (match.match_type says how exactly). matches_quote: it appears in the verbatim source quote but is not a stored value. differs: the record was found an… |
No examples provided.
How do I install the Hospital price-transparency machine-readable file index MCP server?
Hospital price-transparency machine-readable file index is a hosted endpoint at https://referencesource.org/mcp/hospitals, 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 · referencesource.org
claude mcp add --transport http org-referencesource-hospital-price-transparency- 'https://referencesource.org/mcp/hospitals'
What is the Hospital price-transparency machine-readable file index MCP server?
Hospital price-transparency machine-readable file index is an MCP server listed in the public MCP registry as org.referencesource/hospital-price-transparency-files. Where is a US hospital's CMS price-transparency file? The URL, quoted from its own cms-hpt.txt. This page covers its hosted endpoint (https://referencesource.org/mcp/hospitals).
Is the Hospital price-transparency machine-readable file index MCP server safe to use?
Hospital price-transparency machine-readable file index scores 71 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 price-transparency machine-readable file index MCP server expose?
Hospital price-transparency machine-readable file index exposes 3 tools: resolve_hospital_mrf, list_hospitals_on_domain, verify_quote. Their descriptions and schemas cost roughly 688 tokens of context every time the server is loaded.
Does the Hospital price-transparency machine-readable file index MCP server require authentication?
No. We connected to Hospital price-transparency machine-readable file index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hospital price-transparency machine-readable file index MCP server still maintained?
Hospital price-transparency machine-readable file index 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 price-transparency machine-readable file index MCP server?
VerifyMCP ran 13 checks on Hospital price-transparency machine-readable file index, 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.