CareRanks Data
REMOTE · CARERANKS.COM · SCANNED SEP 26
CMS quality ratings, payer-negotiated prices, and clinician data for 41K+ US healthcare facilities.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 656 tokens (~131/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CareRanks Data MCP server?
CareRanks Data is a hosted endpoint at https://careranks.com/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 · careranks.com
claude mcp add --transport http com-careranks-careranks-data 'https://careranks.com/mcp'
{
"mcpServers": {
"com-careranks-careranks-data": {
"url": "https://careranks.com/mcp"
}
}
} {
"servers": {
"com-careranks-careranks-data": {
"type": "http",
"url": "https://careranks.com/mcp"
}
}
} [mcp_servers.com-careranks-careranks-data] url = "https://careranks.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-careranks-careranks-data": {
"type": "remote",
"url": "https://careranks.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-careranks-careranks-data --url 'https://careranks.com/mcp' --transport streamable-http
mcp_servers:
com-careranks-careranks-data:
url: "https://careranks.com/mcp" {
"McpServers": {
"com-careranks-careranks-data": {
"Transport": "http",
"Url": "https://careranks.com/mcp"
}
}
} assistant mcp add com-careranks-careranks-data -t streamable-http -u 'https://careranks.com/mcp'
{
"mcpServers": {
"com-careranks-careranks-data": {
"type": "http",
"url": "https://careranks.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 2 Sept 26 +1
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
- 11 Aug 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
- 4 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Aug 26 0
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 26 Sept 2026 · Probed https://careranks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=careranks.com | CN=WE1,O=Google Trust Services,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 296cc472ebf689f10eb776ac106bcdda |
| SANs: careranks.com | ||||||
| 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 careranks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| careranks.com. | absent | 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://careranks.com/mcp | Verified | 200 | |
| http (plaintext) | http://careranks.com/mcp | Inconclusive | 405 |
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_facility Get facility summary + capability URLs ~71
Look up one facility by {type, id}. Returns the index record plus canonical URLs and which detail tools work for it. Hospital ids are CMS CCNs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Facility id (hospitals: 6-char CCN; systems: slug). |
| type | string | yes | – |
No output schema declared.
No examples provided.
get_facility_profile Get full facility profile content ~88
Structured summary for any facility; for hospitals the full profile markdown (quality measures, ratings context) is returned AS THE TEXT CONTENT BLOCK, with metadata (truncation flag, full URL) in structuredContent. max_chars bounds the markdown body.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| max_chars | integer | – | Markdown budget (default 15000). |
| type | string | yes | – |
No output schema declared.
No examples provided.
get_hospital_clinicians Get hospital clinician roster ~97
Clinicians affiliated with a hospital (CMS data): name, specialty, Medicare procedure volumes, Open Payments totals. Available for ~4,570 hospitals (clinicians_tool_available flag). Filter matches name or specialty.
| Name | Type | Req | Description |
|---|---|---|---|
| ccn | string | yes | Hospital CCN (6 characters). |
| filter | string | – | Optional case-insensitive substring on name or specialty. |
| limit | integer | – | Max clinicians (default 20). |
No output schema declared.
No examples provided.
get_hospital_prices Get payer-negotiated hospital prices ~155
Payer-negotiated rates parsed from a hospital's federally required machine-readable file. Without `drg`: a per-DRG summary (payer count, min/median/max) across every DRG in the file. With `drg` (digits; zero-padded automatically): the individual payer-by-payer rates for that DRG. Available for ~2,060 hospitals (prices_tool_available flag).
| Name | Type | Req | Description |
|---|---|---|---|
| ccn | string | yes | Hospital CCN (6 characters). |
| drg | string | – | Optional MS-DRG code, e.g. "291" or "047". |
| limit | integer | – | Max DRG summary rows (default 100). Ignored when drg is given. |
No output schema declared.
No examples provided.
search_facilities Search US healthcare facilities ~120
Search 41K+ US facilities (hospitals, nursing homes, home-health agencies, dialysis centers, health systems) by name and/or city, optionally filtered by state and type. Returns ids usable with the other tools plus capability flags.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 10). |
| query | string | yes | Name or city text to match (case-insensitive substring). |
| state | string | – | Two-letter state/territory code filter, e.g. "CT". |
| type | string | – | Facility type filter. |
No output schema declared.
No examples provided.
What is the CareRanks Data MCP server?
CareRanks Data is an MCP server listed in the public MCP registry as com.careranks/careranks-data. CMS quality ratings, payer-negotiated prices, and clinician data for 41K+ US healthcare facilities. This page covers its hosted endpoint (https://careranks.com/mcp).
Is the CareRanks Data MCP server safe to use?
CareRanks Data scores 73 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 CareRanks Data MCP server expose?
CareRanks Data exposes 5 tools: search_facilities, get_facility, get_hospital_prices, get_hospital_clinicians, get_facility_profile. Their descriptions and schemas cost roughly 531 tokens of context every time the server is loaded.
Does the CareRanks Data MCP server require authentication?
No. We connected to CareRanks Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CareRanks Data MCP server still maintained?
CareRanks Data is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.