Health · Remote MCP server
FinchNode Health Records
Read patient-authorized EHR records: medications, labs, conditions, allergies. Consent-bounded.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.finchnode/health-records- Version
- 1.0.0
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-09-21
- Updated
- 2026-09-21
- Publisher
- com.finchnode
- Namespace
- Namespace verified by the MCP Registry via the domain finchnode.com · how
- Website
- finchnode.com/ehr-integration-api
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.finchnode.com/api/mcp | Authorization (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)
- 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 FinchNode Health Records
FinchNode Health Records is a remote MCP server: there is nothing to install. Its endpoint is https://api.finchnode.com/api/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 an HTTP header for the connection: Authorization (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 |
|---|---|
| Fda Samd MCPFDA AI/ML Software as a Medical Device Action Plan + 510(k) + PMA + De Novo pathways for US MedT... | Local · stdio |
| Feegow ClinicFull clinic management on Feegow Clinic, patients, appointments, providers, specialties, insurance,. | Remote · HTTPLive check: ✓ handshake |
| fhirfly.ioHealthcare reference data for AI agents: providers, drugs, diagnoses, labs, codes, claims. | Local · stdio |
| FhirhydrantFHIR MCP server with Backend Services, response compaction, FHIRPath, and guarded writes. | Local · stdio |
| Find doctors and specialists in the Greater Toronto AreaGTA doctor, specialist, clinic, language, availability, and freshness data through REST and MCP. | Remote & Local · HTTP, stdioLive check: sign-in required |
| FineRxUS Rx prices by pharmacy near you + free discount card; foreign-brand equivalents; 12 languages. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Finn Tannlege MCPNorwegian dental clinic directory MCP: ~6,900 clinics with Helfo-agreement, specialty, duty, chain. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| FitbitRead Fitbit profile, activity, sleep, heart rate and device data. | Remote · HTTPLive check: ✓ handshake |