FinchNode Synthetic Health Records
com.finchnode/health-records-demo · 1.0.0
Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://api.finchnode.com/demo/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 14 tools.
- Protocol
- 2025-06-18
- Calls itself
- finchnode-public-demo 2026-09-10
- Handshake time
- 294 ms
- HTTP status
- 200
The tools it lists (14, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
list_demo_scenariosUse 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.
get_demo_health_recordGet 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_recordLegacy 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_bundleUse 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_fhirUse 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_connectUse 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.finchnode/health-records-demo, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 16 days ago. The registry entry · finchnode.com