FinchNode Synthetic Health Records
REMOTE · API.FINCHNODE.COM
Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.
Available components
Last scanned (18 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1620 tokens (~115/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.finchnode.com/demo/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.finchnode.com | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 509240396a6b2589139e2a1b415b41e1 |
| SANs: api.finchnode.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.finchnode.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| finchnode.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; base-uri 'none'; frame-ancestors 'self'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.finchnode.com/demo/mcp | Verified | 200 | |
| http (plaintext) | http://api.finchnode.com/demo/mcp | HTTPS enforced | 301 | https://api.finchnode.com/demo/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_demo_allergies Get synthetic allergies ~93
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_conditions Get synthetic conditions ~89
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_demographics Get synthetic basic details (demographics) ~100
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_encounters Get synthetic visits (encounters) ~102
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_fhir_bundle Get synthetic FHIR Bundle ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | – | Optional scenario id from list_demo_scenarios. Omitted means baseline-adult. |
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | – |
No examples provided.
get_demo_health_record Get platform-shaped synthetic health record ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| scenario | string | – | Optional scenario id from list_demo_scenarios. Omitted means baseline-adult. Behavior scenarios (rate-limited, consent-revoked, consent-partial, source-unavailable) answer with the same scripted erro… |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_immunizations Get synthetic immunizations ~92
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_labs Get synthetic lab results (labs) ~97
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_medications Get synthetic medications ~97
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_record Get synthetic health record ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional subset of normalized record categories. |
| scenario | string | – | Optional scenario id from list_demo_scenarios. Omitted means baseline-adult. Behavior scenarios (rate-limited, consent-revoked, consent-partial, source-unavailable) answer with the same scripted erro… |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_vitals Get synthetic vital signs (vitals) ~102
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
list_demo_scenarios List synthetic demo scenarios ~92
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| scenarios | array | yes | – |
No examples provided.
search_demo_fhir Search synthetic FHIR resources ~87
Use this to get all resources of one FHIR R4 type for one synthetic scenario's patient (baseline-adult unless patient_id names another).
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | string | – | Optional scenario subject from list_demo_scenarios. Omitted searches the baseline-adult Bundle only. |
| resource_type | string | yes | FHIR R4 resource type present in the synthetic scenario Bundles. |
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | – |
No examples provided.
simulate_demo_connect Simulate FinchNode Connect ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Requested fictional record categories. |
| external_user_id | string | – | Optional non-sensitive prototype identifier. Never send a real patient identifier. |
| scenario | string | – | Optional scenario id from list_demo_scenarios. Omitted means baseline-adult; connect-cancelled and connect-failed end without a patient. |
| Name | Type | Req | Description |
|---|---|---|---|
| session | object | yes | – |
No examples provided.
How do I install the FinchNode Synthetic Health Records MCP server?
FinchNode Synthetic Health Records is a hosted endpoint at https://api.finchnode.com/demo/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.finchnode.com
claude mcp add --transport http com-finchnode-health-records-demo 'https://api.finchnode.com/demo/mcp'
What is the FinchNode Synthetic Health Records MCP server?
FinchNode Synthetic Health Records is an MCP server listed in the public MCP registry as com.finchnode/health-records-demo. Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key. This page covers its hosted endpoint (https://api.finchnode.com/demo/mcp).
Is the FinchNode Synthetic Health Records MCP server safe to use?
FinchNode Synthetic Health Records scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FinchNode Synthetic Health Records MCP server expose?
FinchNode Synthetic Health Records exposes 14 tools: list_demo_scenarios, get_demo_health_record, get_demo_record, get_demo_fhir_bundle, search_demo_fhir, and 9 more. Their descriptions and schemas cost roughly 1,411 tokens of context every time the server is loaded.
Does the FinchNode Synthetic Health Records MCP server require authentication?
No. We connected to FinchNode Synthetic Health Records without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FinchNode Synthetic Health Records MCP server still maintained?
FinchNode Synthetic Health Records is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FinchNode Synthetic Health Records MCP server?
VerifyMCP ran 13 checks on FinchNode Synthetic Health Records, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.