Is the Healthparse Gateway MCP server down?

mcp-registry/io.healthparse/gateway · v1.0.0

healthy
Last checked 2026-10-27 00:20 UTC · handshake 191ms

As of 2026-10-27 00:20 UTC, the Healthparse Gateway MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,941
outages (90d)
0
tools
42

Pay-per-call US healthcare data: hospital financials, prices, quality, exclusions, wages.

Point your MCP client at this streamable-http endpoint: https://api.healthparse.io/mcp

Agent-readiness: D (69/100)

D (69/100): 0 error(s), 3 warning(s) across 42 tool(s); ~10,298 tokens of tool definitions.
Scores higher than 4% of 15,774 MCP servers Glimind has audited.
Its tool list costs an agent ~10,298 tokens per session — more than 80% of servers.
67 → 69 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions37
Safety hints30
Token cost75
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

42 of 42 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: carecompare_dialysis_byCcn, carecompare_dialysis_search, carecompare_home-health_byCcn, carecompare_home-health_search, carecompare_hospice_byCcn and 37 more

42 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

147 parameter(s) across 32 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: carecompare_dialysis_search, carecompare_home-health_search, carecompare_hospice_search, carecompare_hospitals_search, carecompare_snf_search and 27 more

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: 30 corrected tool definitions

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

carecompare_dialysis_search 1 change 
{
  "name": "carecompare_dialysis_search",
  "description": "Search dialysis quality data by state, city, ZIP, or CMS star rating. Answers: which dialysis meet quality thresholds in a market? Source: CMS Care Compare, monthly refresh. [price: $0.02/call]",
  "inputSchema": {
    "type": "object",
    "properties": {
      "city": {
        "type": "string"
      },
      "limit": {
        "type": "integer",
        "default": 25,
        "maximum": 100
      },
      "state": {
        "type": "string"
      },
      "offset": {
        "type": "integer",
        "default": 0
      },
      "rating_max": {
        "type": "number"
      },
      "rating_min": {
        "type": "number"
      },
      "zip_prefix": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
carecompare_home-health_byCcn 1 change 
{
  "name": "carecompare_home-health_byCcn",
  "description": "CMS Care Compare quality record by CCN for a home health. Answers: what are the quality ratings and performance measures for this facility? Source: CMS Care Compare. [price: $0.01/call]",
  "inputSchema": {
    "type": "object",
    "required": [
      "ccn"
    ],
    "properties": {
      "ccn": {
        "type": "string",
        "description": "Path parameter: CMS Certification Number"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
carecompare_home-health_search 1 change 
{
  "name": "carecompare_home-health_search",
  "description": "Search home health quality data by state, city, ZIP, or CMS star rating. Answers: which home health meet quality thresholds in a market? Source: CMS Care Compare, monthly refresh. [price: $0.02/call]",
  "inputSchema": {
    "type": "object",
    "properties": {
      "city": {
        "type": "string"
      },
      "limit": {
        "type": "integer",
        "default": 25,
        "maximum": 100
      },
      "state": {
        "type": "string"
      },
      "offset": {
        "type": "integer",
        "default": 0
      },
      "rating_max": {
        "type": "number"
      },
      "rating_min": {
        "type": "number"
      },
      "zip_prefix": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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/io.healthparse/gateway"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.healthparse/gateway"}) 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%2Fio.healthparse%2Fgateway.svg)](https://glimind.com/server/mcp-registry%2Fio.healthparse%2Fgateway?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.healthparse%2Fgateway?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.healthparse%2Fgateway.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.healthparse%2Fgateway.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.healthparse%2Fgateway?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:599dd5665807d96b…, first seen 2026-10-17, included at leaf 11637 of 76,315. Version history · verify what your client received.

Tools (42)

Compare: most reliable retrieval servers · most reliable search servers · most reliable data servers · most reliable finance servers · most reliable database 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 Healthparse Gateway MCP server down right now?

As of 2026-10-27 00:20 UTC, the Healthparse Gateway MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Healthparse Gateway MCP server provide?

Healthparse Gateway MCP server advertises 42 tools, including carecompare_dialysis_byCcn, carecompare_dialysis_search, carecompare_home-health_byCcn, carecompare_home-health_search, carecompare_hospice_byCcn.

How do I install Healthparse Gateway MCP server?

Point your MCP client at this streamable-http endpoint: https://api.healthparse.io/mcp

Is the Healthparse Gateway MCP server safe to connect to an AI agent?

Glimind scanned all 42 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 Healthparse Gateway 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