FinchNode Health Records

com.finchnodePublished by finchnode.comOfficial publisherv1.0.0Updated Oct 25, 2026

Read patient-authorized EHR records: medications, labs, conditions, allergies. Consent-bounded.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP server that lets an assistant read patient-authorized electronic health record data — medications, labs, conditions and allergies — within consent.

What you can do
Read patient-authorized EHR records, including medications, labs, conditions and allergies, through a hosted FinchNode endpoint. Access is described as consent-bounded, so results are limited to records the patient has authorized. Sandbox and production connections are separated by the type of API key used.
When to use it
Useful when an assistant needs to pull structured clinical record data for a patient who has authorized access, for example to summarize medications, review lab results or check conditions and allergies. Not intended for general health advice or for records without patient consent.
Requirements
A remote streamable HTTP endpoint at api.finchnode.com, reachable over the network. A FinchNode API key is required, sent as a bearer token in the Authorization header; keys are created in the FinchNode console, with test keys for sandbox connections and live keys for production connections.
Before you install
The Authorization header carries a FinchNode API key, which is a credential; keep it out of logs and shared transcripts. Live keys reach production patient records, so prefer test keys while evaluating. The server exposes sensitive health data, and access depends on patient consent being in place.

Installation

In SourceWeft

  1. Open FinchNode Health Records in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.finchnode%2Fhealth-records/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "finchnode-health-records": {
      "type": "http",
      "url": "https://api.finchnode.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Finchnode integrations