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

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

## Components

- remote · `referencesource.org`: 71/100 (this document), [markdown](https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals.md), [page](https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals)

## Channel facts

- Endpoint: `https://referencesource.org/mcp/hospitals`
- 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**: 74/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 is enforced; there's no plaintext access path.
  - 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**: 62/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http org-referencesource-hospital-price-transparency- 'https://referencesource.org/mcp/hospitals'
```

### Cursor

```json
{
  "mcpServers": {
    "org-referencesource-hospital-price-transparency-": {
      "url": "https://referencesource.org/mcp/hospitals"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-referencesource-hospital-price-transparency-": {
      "type": "http",
      "url": "https://referencesource.org/mcp/hospitals"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-referencesource-hospital-price-transparency-]
url = "https://referencesource.org/mcp/hospitals"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-referencesource-hospital-price-transparency-": {
      "type": "remote",
      "url": "https://referencesource.org/mcp/hospitals",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-referencesource-hospital-price-transparency- --url 'https://referencesource.org/mcp/hospitals' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-referencesource-hospital-price-transparency-:
    url: "https://referencesource.org/mcp/hospitals"
```

### Netclaw

```json
{
  "McpServers": {
    "org-referencesource-hospital-price-transparency-": {
      "Transport": "http",
      "Url": "https://referencesource.org/mcp/hospitals"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-referencesource-hospital-price-transparency- -t streamable-http -u 'https://referencesource.org/mcp/hospitals'
```

### Other

```json
{
  "mcpServers": {
    "org-referencesource-hospital-price-transparency-": {
      "type": "http",
      "url": "https://referencesource.org/mcp/hospitals"
    }
  }
}
```

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-20 (score 71, +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-18 (score 70, +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-17 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 69)

First indexed and scored.

## MCP tools (3)

### `resolve_hospital_mrf` (~243 tokens)

Find a hospital's price-transparency machine-readable file

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.

Input parameters:

- `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, required): Hospital name or part of one. Case- and punctuation-insensitive; exact matches are returned first, then names starting with it, then names containing it.

Output parameters:

- `hospitals` (array)
- `hospitals_matched` (integer)
- `hospitals_returned` (integer)
- `name` (string)
- `note` (string)
- `register` (object)

### `list_hospitals_on_domain` (~207 tokens)

List every hospital a health system's cms-hpt.txt declares

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.

Input parameters:

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

Output parameters:

- `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)

### `verify_quote` (~238 tokens)

Check a claimed hospital file URL against the register

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.

Input parameters:

- `claimed_value` (string, required): 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, required): The hospital name the claim is about, as resolve_hospital_mrf returns it.

Output parameters:

- `attestation` (string)
- `claimed_value` (string)
- `in_source_quote` (boolean)
- `match` (object)
- `quote_source` (string)
- `record` (object)
- `stored_values` (object)
- `verdict` (string): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69

## Common questions

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

## Links

- Remote endpoint: https://referencesource.org/mcp/hospitals
- Website: https://referencesource.org/hospital-price-transparency-mrf-index
- Changelog RSS feed: https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals.json
- HTML version of this page: https://verifymcp.io/servers/org-referencesource-hospital-price-transparency-files/mcp-hospitals
