Health · Remote MCP server
Healthcare Provider Intelligence
Provider intelligence API joining NPPES, CMS Open Payments, and OIG LEIE with source provenance.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Joinware/healthcare-provider-intelligence- Version
- 0.1.2
- Status
- Active
- Category
- health
- Transport
- SSE (HTTP + Server-Sent Events)
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- Joinware (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Joinware) · how
- Repository
- github.com/Joinware/healthcare-provider-intelligence
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://healthcare-provider-intelligence-85cj.onrender.com/mcp/sse | X-API-Key (required, secret) |
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 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Healthcare Provider Intelligence
Healthcare Provider Intelligence is a remote MCP server reached over the older SSE transport, at https://healthcare-provider-intelligence-85cj.onrender.com/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: X-API-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 |
|---|---|
| health-osLocal-first personal health record: labs, meds, wearables, food log, deterministic safety checks. | Local · stdio |
| health4aiQuery your Apple Health data from your own Supabase/Postgres via local MCP. | Local · stdio |
| 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 |
| Healthclaw GuardrailsGuardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation. | Remote · HTTPLive check: sign-in required |
| Healthcovered MCPACA health insurance eligibility, subsidy checker, and enrollment dates for 2026. | Remote · HTTPLive check: ✓ handshake |
| 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 |