Skip to content
FinchNode logo

FinchNode MCP server

Which servers in the official MCP registry are FinchNode's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to FinchNode

Whose server it is
  • Registry namecom.finchnode/health-records-demoverified in the MCP registry

The registry name sits under finchnode.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools14
  • Server calls itselffinchnode-public-demo
  • Server version2026-09-10
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 103 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer139 ms
  • Space in an agent's context≈ 2,600 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsA · 99 of 100
  • Typed results14 of 14 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 1 of 14

What an agent can do with it

  • not sure · Connect patient health records through hosted patient consent
  • cannot · Sync normalized patient records on a schedule
  • not sure · Search providers and request patient-authorized records

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-24
  • list_demo_scenarios

    Use this first to choose a fictional scenario: 12 record, behavior (consent, rate-limit, and source-failure errors), and Connect session cases, each with its subject, categories, what it exercises, and links. Pass an id as scenario to the…

  • get_demo_health_record

    Get any mix of demographics, medications, conditions, labs, vitals, allergies, immunizations, encounters in one call — prefer this over several single-category tools. Builds a record view using the authenticated API normalized data shape…

  • get_demo_record

    Legacy categorized FHIR response. Kept compatible for existing prototypes. For normalized platform-shaped data, use get_demo_health_record. Fictional patients only; pick one with scenario.

  • get_demo_fhir_bundle

    Use this when a prototype or test needs the complete fictional FinchNode FHIR R4 Bundle for one scenario and its resource references. Behaviors apply to record reads only, so every scenario returns its Bundle.

  • search_demo_fhir

    Use this to get all resources of one FHIR R4 type for one synthetic scenario's patient (baseline-adult unless patient_id names another).

  • simulate_demo_connect

    Use this to prototype the FinchNode connection journey. Returns a non-persistent synthetic session: complete for a record or behavior scenario, or the connect-cancelled or connect-failed outcome with no patient.

  • get_demo_demographics

    Use this to get only the basic details (demographics) of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Name, birth date, sex, contact…

  • get_demo_medications

    Use this to get only the medications of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Active and past prescriptions, normalized from FHIR R4…

  • get_demo_conditions

    Use this to get only the conditions of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Diagnoses and problem list, normalized from FHIR R4…

  • get_demo_labs

    Use this to get only the lab results (labs) of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Laboratory observations and reports, normalized…

  • get_demo_vitals

    Use this to get only the vital signs (vitals) of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Blood pressure, heart rate, weight, and similar…

  • get_demo_allergies

    Use this to get only the allergies of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Allergies and intolerances, normalized from FHIR R4…

  • get_demo_immunizations

    Use this to get only the immunizations of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Vaccination history, normalized from FHIR R4…

  • get_demo_encounters

    Use this to get only the visits (encounters) of baseline-adult, one of FinchNode's 12 synthetic scenarios from Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic): Encounters, appointments, and care teams…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "health-records-demo": {
      "type": "http",
      "url": "https://api.finchnode.com/demo/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http finchnode https://api.finchnode.com/demo/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.finchnode.com/demo/mcp as a custom connector in the settings.

Other servers listed as FinchNode's
  • com.finchnode/health-recordsanswers, requires sign-inverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.