Is the Careranks Data MCP server down?

mcp-registry/com.careranks/careranks-data · v1.0.0

healthy
Last checked 2026-10-26 18:13 UTC · handshake 122ms

As of 2026-10-26 18:13 UTC, the Careranks Data MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 22 minutes.

uptime (30d checks)
99.9%
checks observed
4,886
outages (90d)
1
tools
5

CMS quality ratings, payer-negotiated prices, and clinician data for 41K+ US healthcare facilities.

Point your MCP client at this streamable-http endpoint: https://careranks.com/mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 2 warning(s) across 5 tool(s); ~917 tokens of tool definitions.
Scores higher than 13% of 15,768 MCP servers Glimind has audited.
Its tool list costs an agent ~917 tokens per session — lighter than 80% of servers.
76 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions62
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_facility, get_facility_profile, get_hospital_clinicians, get_hospital_prices, search_facilities

3 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_facility, get_facility_profile

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.careranks%2Fcareranks-data/fixes

get_facility 1 change
{
  "name": "get_facility",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "type",
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Facility id (hospitals: 6-char CCN; systems: slug)."
      },
      "type": {
        "enum": [
          "hospital",
          "nursing-home",
          "home-health",
          "dialysis",
          "system"
        ],
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get facility summary + capability URLs"
}
get_facility_profile 1 change
{
  "name": "get_facility_profile",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "type",
      "id"
    ],
    "properties": {
      "id": {
        "type": "string"
      },
      "type": {
        "enum": [
          "hospital",
          "nursing-home",
          "home-health",
          "dialysis",
          "system"
        ],
        "type": "string"
      },
      "max_chars": {
        "type": "integer",
        "maximum": 40000,
        "minimum": 500,
        "description": "Markdown budget (default 15000)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get full facility profile content"
}
get_hospital_clinicians 1 change
{
  "name": "get_hospital_clinicians",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "ccn"
    ],
    "properties": {
      "ccn": {
        "type": "string",
        "description": "Hospital CCN (6 characters)."
      },
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Max clinicians (default 20)."
      },
      "filter": {
        "type": "string",
        "description": "Optional case-insensitive substring on name or specialty."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get hospital clinician roster"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.careranks/careranks-data"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.careranks/careranks-data"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.careranks%2Fcareranks-data.svg)](https://glimind.com/server/mcp-registry%2Fcom.careranks%2Fcareranks-data?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.careranks%2Fcareranks-data?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.careranks%2Fcareranks-data.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.careranks%2Fcareranks-data.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.careranks%2Fcareranks-data?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9834a234bcba5358…, first seen 2026-10-17, included at leaf 5885 of 74,638. Version history · verify what your client received.

Tools (5)

Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Careranks Data MCP server down right now?

As of 2026-10-26 18:13 UTC, the Careranks Data MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 22 minutes.

How many tools does Careranks Data MCP server provide?

Careranks Data MCP server advertises 5 tools, including get_facility, get_facility_profile, get_hospital_clinicians, get_hospital_prices, search_facilities.

How do I install Careranks Data MCP server?

Point your MCP client at this streamable-http endpoint: https://careranks.com/mcp

Is the Careranks Data MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Careranks Data MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve