FinchNode Synthetic Health Records MCP Server

by finchnode Your server? Claim it

answering

FinchNode Synthetic Health Records is answering right now. Last checked 12 min ago. It exposes 14 tools.

Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.

Uptime history 47 days of history · worst day 96%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

347 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 21

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 September 2026. No other catalogue keeps this.

3 Oct a tool description was rewritten get_demo_medications

3 Oct a tool changed the parameters it asks for search_demo_fhir

26 Sep 13 tool descriptions were rewritten get_demo_allergies, get_demo_conditions, get_demo_demographics and 10 more

26 Sep 5 tools changed the parameters they ask for get_demo_fhir_bundle, get_demo_health_record, get_demo_record and 2 more

26 Sep a tool appeared list_demo_scenarios

Nothing serious here today

Today is the operative word: we check FinchNode Synthetic Health Records every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://api.finchnode.com/demo/mcp

~/.codex/config.toml

[mcp_servers.health-records-demo]
url = "https://api.finchnode.com/demo/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

demo

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 AllergyIntolerance. No account or API key. To get allergies together with other categories, call get_demo_health_record once instead of calling several of these tools.

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 Condition. No account or API key. To get conditions together with other categories, call get_demo_health_record once instead of calling several of these tools.

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 information, normalized from FHIR R4 Patient. No account or API key. To get basic details together with other categories, call get_demo_health_record once instead of calling several of these tools.

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, normalized from FHIR R4 Encounter, Appointment, CareTeam. No account or API key. To get visits together with other categories, call get_demo_health_record once instead of calling several of these tools.

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.

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 (schemaVersion 2). Fictional patients only; pick one with scenario. Consent and sync are simulated, with no usable change cursor. Empty categories describe the fixture only.

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 Immunization. No account or API key. To get immunizations together with other categories, call get_demo_health_record once instead of calling several of these tools.

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 from FHIR R4 Observation, DiagnosticReport. No account or API key. To get lab results together with other categories, call get_demo_health_record once instead of calling several of these tools.

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 MedicationRequest, MedicationDispense, MedicationAdministration. No account or API key. To get medications together with other categories, call get_demo_health_record once instead of calling several of these tools.

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_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 measures, normalized from FHIR R4 Observation. No account or API key. To get vital signs together with other categories, call get_demo_health_record once instead of calling several of these tools.

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 other demo tools. No clinical data. The controls and exercises fields describe the authenticated FinchNode sandbox; this accountless demo cannot perform them.

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

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.

Endpoints

URL	Transport	State	Latency	Checked
https://api.finchnode.com/demo/mcp	streamable-http	answering	324 ms	12 min ago

Alternatives to FinchNode Synthetic Health Records

same job, measured the same way

FinchNode Health Records

by finchnode

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

answering

Health Gorilla MCP by usefulapi

by usefulapi

Query Health Gorilla FHIR patients, conditions, medications and lab results.

16 tools answering

Elation Health MCP by usefulapi

by usefulapi

Read Elation Health patients, appointments, problems, allergies, medications, notes and vitals.

14 tools answering

Akute Health MCP by usefulapi

by usefulapi

Read Akute Health patients, appointments, tasks, notes, medications, allergies and observations.

15 tools answering

Mednode

by mednode

Your MedNode health vault in your AI assistant — records, summaries, labs, appointments.

answering

Anpheros FHIR

by anpheros

HL7 FHIR R4 health-data API for AI agents: free sandbox, 30 synthetic patients, AI-ready context.

answering

K01 Synthetic Health Data

by k01

Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.

answering

MCP Imslp

by smeet666

Read IMSLP, the Petrucci Music Library: works, scores, editions, copyright. No API key.

152 installs/wk local only

FinchNode Synthetic Health Records — questions

Answers built from our own checks of this server.

What can FinchNode Synthetic Health Records do?

It exposes 14 tools, read directly from the server on our last check. Among them: get_demo_allergies, get_demo_conditions, get_demo_demographics, get_demo_encounters, get_demo_fhir_bundle, get_demo_health_record and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is FinchNode Synthetic Health Records working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 347 ms. The bar chart above shows every period we have measured.

How do I connect FinchNode Synthetic Health Records?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does FinchNode Synthetic Health Records need an API key?

No. FinchNode Synthetic Health Records completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is FinchNode Synthetic Health Records?

It answers our handshake in 347 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.