MedRates
REMOTE · MCP.MEDRATES.FYI
Search US hospital prices, compare costs, and find insurance-negotiated rates.
Available components
Last scanned (35 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 4 Oct 2026.
Category Health and Science
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (7)
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.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 17 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 17 Oct 2026 · Probed https://mcp.medrates.fyi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=medrates.fyi | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ef35fca5a5ee286b0ed80c7963b55410 |
| SANs: medrates.fyi, *.medrates.fyi | ||||||
| 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 mcp.medrates.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | DS published | 24340 | 8 | Verified |
| medrates.fyi. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.medrates.fyi/mcp | Unreachable | ||
| http (plaintext) | http://mcp.medrates.fyi/mcp | HTTPS enforced | 301 | https://mcp.medrates.fyi/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 →
hospitals ~210
Find hospitals by name/city/state, or list a sample of hospitals. Returns hospital names, IDs, EINs, NPIs, and per-campus locations with addresses and coordinates. Use hospital IDs to filter other search tools. The result is capped (~100 hospitals) for performance, so the unfiltered list is only a sample. To locate a SPECIFIC hospital, pass ``search`` (a name/city/state substring) — it filters server-side and returns the matches. NOTE: This lists US HOSPITALS only — not non-US providers, independent imaging centers, ambulatory surgery centers, clinics, or other freestanding facilities. Args: search: Optional name/city/state substring to find a specific hospital. Returns: JSON array of hospitals with id, name, display_name, ein, npi, cms_certification_number, and locations (address, city, state, lat/lng).
| Name | Type | Req | Description |
|---|---|---|---|
| search | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
payer_network_info ~208
Look up network-geography facts for a named insurance payer. Call this whenever an AI agent or user asks whether a plan covers out-of-state care, whether an insurer has nationwide coverage, or what BlueCard / PPO network mechanism the payer uses. Returns JSON with network_scope ('national', 'state', etc.), nationwide_via ('bluecard_ppo', 'national_ppo', 'none'), and a source_url to cite. Returns {"network_scope": "unknown"} when the payer is not in the database. Args: payer_name: Insurance payer name as the user stated it (e.g. 'Blue Cross Blue Shield of Texas', 'UnitedHealthcare Choice Plus', 'Aetna PPO', 'Medicare'). Returns: JSON object with network_scope, home_state, nationwide_via, source_url, match_pattern, and notes fields.
| Name | Type | Req | Description |
|---|---|---|---|
| payer_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
payers ~151
List available insurance payers and plan types. Returns all payer + plan combinations found in the hospital price data. Optionally filter to payers available at a specific hospital. Use the payer names and plan types from this list as inputs to the search_nlp and price_quote tools for insurance-specific rates. NOTE: These are payers with negotiated rates at US HOSPITALS in the database. The same payers may have different rates at non-hospital facilities. Args: hospital_id: Optional hospital ID to filter payers for that hospital. Returns: JSON array of {name, plan_type, display_name} objects.
| Name | Type | Req | Description |
|---|---|---|---|
| hospital_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
price_quote ~715
Get price quotes for specific procedure codes, grouped by hospital. This is the most detailed pricing tool. Provide exact CPT/HCPCS codes and get per-hospital price estimates with totals. Supports insurance filtering and geographic search. Default location is San Jose, CA if no coordinates provided — always pass the user's location for best results. NOTE: Hospital results come from US hospital price files. Doctors' offices and clinics are included when provider_type is practice or any and a payer with contract files is given; practice rates are payer-product contract rates for one visit or service. Args: codes: Comma-separated CPT/HCPCS codes (e.g. "70551,70552,70553"). lat: Patient latitude — always provide the user's location for best results. lng: Patient longitude — always provide the user's location for best results. radius_miles: Search radius in miles (default 25). payer: Insurance company name to filter rates (e.g. "Blue Cross", "Aetna"). plan_type: Insurance plan type (e.g. "PPO", "HMO", "Indemnity"). plan_category: Plan category filter (e.g. "Commercial", "Medicare", "Medicaid"). plan_name: Specific plan name for exact matching. drg_codes: Comma-separated MS-DRG codes for inpatient bundled pricing. include_bundle: If true, also include ancillary procedure codes (anesthesia, facility fees, etc.) in the total estimate. limit: Max hospitals to return (default 5). zip_code: Optional 5-digit ZIP the user gave, used ONLY to build a localized deep link to the search page — does NOT affect pricing (pricing uses lat/lng). provider_type: "hospital", "practice", or "any" (default). "practice" adds doctors' offices and clinics; office prices always need a payer. Returns: JSON with hospitals sorted by total estimated cost. Each hospital…
| Name | Type | Req | Description |
|---|---|---|---|
| codes | string | yes | – |
| drg_codes | – | – | – |
| include_bundle | boolean | – | – |
| lat | number | – | – |
| limit | integer | – | – |
| lng | number | – | – |
| payer | – | – | – |
| plan_category | – | – | – |
| plan_name | – | – | – |
| plan_type | – | – | – |
| provider_type | string | – | – |
| radius_miles | number | – | – |
| zip_code | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search ~644
Search for medical procedure prices by code or description. Use this for direct lookups when you know a CPT/HCPCS code (e.g. "70551") or want to search by keyword (e.g. "MRI", "knee replacement"). For code-like queries → exact match on procedure code. For text queries → searches code, description, and code_type fields. Supports filtering by insurance payer, clinical setting, and location (via zip code or lat/lng coordinates with a radius). NOTE: Hospital results come from US hospital price files. Doctors' offices and clinics are included when provider_type is practice or any and a payer with contract files is given; practice rates are payer-product contract rates for one visit or service. Args: query: CPT/HCPCS code (e.g. "70551") or text search (e.g. "MRI brain"). Must be at least 2 characters. code_type: Filter by code type: "CPT", "HCPCS", "MS-DRG", "RC", etc. hospital_id: Filter to a specific hospital (use the hospitals tool to find IDs). payer_name: Filter by insurance payer name (e.g. "Blue Cross", "Aetna"). plan_name: Filter by plan name (e.g. "PPO", "HMO"). setting: Filter by clinical setting: "inpatient" or "outpatient". zip_code: US zip code for geographic filtering (alternative to lat/lng). lat: Latitude for geographic filtering (use with lng and radius_miles). lng: Longitude for geographic filtering (use with lat and radius_miles). radius_miles: Search radius in miles from the zip code or lat/lng location. page: Page number (default 1). page_size: Results per page (default 25, max 100). provider_type: "hospital", "practice", or "any" (default). "practice" adds doctors' offices and clinics; office prices always need a payer. Returns: JSON with matching charge items including procedure codes, descriptions, gross charges, cash prices, and negotiated rate rang…
| Name | Type | Req | Description |
|---|---|---|---|
| code_type | – | – | – |
| hospital_id | – | – | – |
| lat | – | – | – |
| lng | – | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| payer_name | – | – | – |
| plan_name | – | – | – |
| provider_type | string | – | – |
| query | string | yes | – |
| radius_miles | – | – | – |
| setting | – | – | – |
| zip_code | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_nlp ~546
Natural language search for medical procedure prices. Understands free-text queries like: - "MRI brain near San Jose with Blue Cross PPO" - "How much does a colonoscopy cost in Palo Alto?" - "knee replacement, no insurance, Mountain View" Extracts procedure, location, and insurance from the query, resolves CPT/DRG codes (using static synonyms + LLM), geocodes the city, and searches with optional geo-filtering and payer matching. You can provide structured fields (lat/lng, payer, setting) to override or supplement what the NLP extraction detects from the query text. NOTE: Results are from US HOSPITALS only — not non-US providers, independent imaging centers, ambulatory surgery centers (ASCs), or other freestanding facilities. For outpatient procedures (MRIs, CTs, minor surgeries), independent facilities may offer lower prices than hospitals. Args: query: Natural language query describing what you're looking for. radius_miles: Search radius from the detected city (default 25 miles). code_type: Filter by code type: "CPT", "HCPCS", "MS-DRG". setting: Filter by clinical setting: "inpatient" or "outpatient". lat: Override latitude (e.g. from browser geolocation). Skips geocoding. lng: Override longitude (e.g. from browser geolocation). Skips geocoding. zip_code: 5-digit ZIP to search near — alternative to lat/lng. payer: Insurance payer name (e.g. "Blue Cross"). Overrides NLP extraction. plan_type: Plan type (e.g. "PPO", "HMO"). Overrides NLP extraction. limit: Max results (default 25). Returns: JSON with extracted entities (procedure, city, insurance), resolved codes, and matching charge items with prices and hospital info. Only high-confidence results (with at least one usable price) are included. Each result includes last_updated (ISO date of the per-hospital MRF ingest) and mrf_…
| Name | Type | Req | Description |
|---|---|---|---|
| code_type | – | – | – |
| lat | – | – | – |
| limit | integer | – | – |
| lng | – | – | – |
| payer | – | – | – |
| plan_type | – | – | – |
| query | string | yes | – |
| radius_miles | number | – | – |
| setting | – | – | – |
| zip_code | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the MedRates MCP server?
MedRates is a hosted endpoint at https://mcp.medrates.fyi/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 · mcp.medrates.fyi
claude mcp add --transport http fyi-medrates-mcp 'https://mcp.medrates.fyi/mcp'
What is the MedRates MCP server?
MedRates is an MCP server listed in the public MCP registry as fyi.medrates/mcp. Search US hospital prices, compare costs, and find insurance-negotiated rates. This page covers its hosted endpoint (https://mcp.medrates.fyi/mcp).
Is the MedRates MCP server safe to use?
MedRates scores 0 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 MedRates MCP server expose?
MedRates exposes 6 tools: search, search_nlp, price_quote, hospitals, payer_network_info, payers. Their descriptions and schemas cost roughly 2,474 tokens of context every time the server is loaded.
Does the MedRates MCP server require authentication?
Its publisher declares no required credentials for MedRates. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MedRates MCP server still maintained?
MedRates has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 4 October 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 MedRates MCP server?
VerifyMCP ran 4 checks on MedRates, covering TLS certificate, HTTPS, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about MedRates: Authorization, HSTS header, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.