Health · Remote MCP server
Healthcovered MCP
ACA health insurance eligibility, subsidy checker, and enrollment dates for 2026.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.hillsidecoastal-glitch/healthcovered-mcp- Version
- 1.0.0
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-03-31
- Updated
- 2026-03-31
- Publisher
- hillsidecoastal-glitch (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/hillsidecoastal-glitch) · how
- Repository
- github.com/hillsidecoastal-glitch/healthcovered-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://healthcovered-mcp.onrender.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- HealthCovered ACA Assistant 1.26.0 · protocol 2025-06-18
- Tools discovered
- 3:
check_aca_eligibility,get_enrollment_dates,get_healthcovered_contact - Checked on
- 2026-10-05
How to connect Healthcovered MCP
Healthcovered MCP is a remote MCP server: there is nothing to install. Its endpoint is https://healthcovered-mcp.onrender.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| Healthcare DataUS healthcare data for AI agents: CMS, FDA adverse events, CDC, NPPES NPI. Keyless, real samples. | Remote · HTTPLive check: ✓ handshake |
| Healthcare Fda Intelligence MCPScrape the FAA Aircraft Registry by N-number - aircraft make, model, year, owner name, address, airw. | Remote · HTTPLive check: ✗ no handshake |
| Healthcare Provider IntelligenceProvider intelligence API joining NPPES, CMS Open Payments, and OIG LEIE with source provenance. | Remote · SSELive check: sign-in required |
| Healthclaw GuardrailsGuardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation. | Remote · HTTPLive check: sign-in required |
| HealthguardHealthGuard - 12-tool health/medical AI safety MCP: PII redaction, HIPAA, GDPR Art.9. | Remote · HTTPLive check: ✓ handshake |
| Healthparse Healthcare Data GatewayPay-per-call US healthcare data: hospital financials, prices, quality, exclusions, wages. | Remote · HTTPLive check: ✓ handshake |
| healthpoint-rsRead-only MCP server for licensed Healthpoint HL7 FHIR API access. | Local · stdio |
| HebrewCore by baba HebrewHebrew translation that keeps prices, names and dates exact, RTL display, nikud, clinical Hebrew. | Remote · HTTPLive check: ✓ handshake |