Health · Remote MCP server
Healthclaw Guardrails
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.aks129/healthclaw-guardrails- Version
- 1.6.0
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-07-04
- Updated
- 2026-07-04
- Publisher
- aks129 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/aks129) · how
- Website
- healthclaw.io
- Repository
- github.com/aks129/HealthClawGuardrails
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp-server-production-5112.up.railway.app/mcp | X-Tenant-Id, X-Step-Up-Token (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)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Healthclaw Guardrails
Healthclaw Guardrails is a remote MCP server: there is nothing to install. Its endpoint is https://mcp-server-production-5112.up.railway.app/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.
The registry entry declares HTTP headers for the connection: X-Tenant-Id and X-Step-Up-Token (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set them 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
Site checks
The website's own root, healthclaw.io, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More health servers
| Server | Runs |
|---|---|
| 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 |
| Healthcare Provider IntelligenceProvider intelligence API joining NPPES, CMS Open Payments, and OIG LEIE with source provenance. | Remote · SSELive 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 |
| healthpoint-rsRead-only MCP server for licensed Healthpoint HL7 FHIR API access. | Local · stdio |