FinchNode Synthetic Health Records
REMOTE · API.FINCHNODE.COM · SCANNED SEP 25
Synthetic EHR: medications, labs, conditions, allergies, immunizations, FHIR R4. No API key.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1047 tokens (~80/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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'
{
"mcpServers": {
"com-finchnode-health-records-demo": {
"url": "https://api.finchnode.com/demo/mcp"
}
}
} {
"servers": {
"com-finchnode-health-records-demo": {
"type": "http",
"url": "https://api.finchnode.com/demo/mcp"
}
}
} [mcp_servers.com-finchnode-health-records-demo] url = "https://api.finchnode.com/demo/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-finchnode-health-records-demo": {
"type": "remote",
"url": "https://api.finchnode.com/demo/mcp",
"enabled": true
}
}
} openclaw mcp add com-finchnode-health-records-demo --url 'https://api.finchnode.com/demo/mcp' --transport streamable-http
mcp_servers:
com-finchnode-health-records-demo:
url: "https://api.finchnode.com/demo/mcp" {
"McpServers": {
"com-finchnode-health-records-demo": {
"Transport": "http",
"Url": "https://api.finchnode.com/demo/mcp"
}
}
} assistant mcp add com-finchnode-health-records-demo -t streamable-http -u 'https://api.finchnode.com/demo/mcp'
{
"mcpServers": {
"com-finchnode-health-records-demo": {
"type": "http",
"url": "https://api.finchnode.com/demo/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 74
First indexed and scored.
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 25 Sept 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 | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a96df831f223707f1368014b55d408d5 |
| 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. | present | 19718 | 13 | Verified |
| finchnode.com. | absent | 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 ~72
Use this to get only the allergies of FinchNode's fixed fictional sample EMR: 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 ~68
Use this to get only the conditions of FinchNode's fixed fictional sample EMR: 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) ~79
Use this to get only the basic details (demographics) of FinchNode's fixed fictional sample EMR: 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) ~81
Use this to get only the visits (encounters) of FinchNode's fixed fictional sample EMR: 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 ~34
Use this when a prototype or test needs the complete fictional FinchNode FHIR R4 Bundle and its resource references.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | – |
No examples provided.
get_demo_health_record Get platform-shaped synthetic health record ~93
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). Fixed fictional patient only; consent and sync are simulated, with no usable receipts or change cursor. Empty categories describe this fixture only.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_immunizations Get synthetic immunizations ~71
Use this to get only the immunizations of FinchNode's fixed fictional sample EMR: 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) ~76
Use this to get only the lab results (labs) of FinchNode's fixed fictional sample EMR: 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 ~73
Use this to get only the medications of FinchNode's fixed fictional sample EMR: Active and past prescriptions, normalized from FHIR R4 MedicationRequest, MedicationDispense. 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 ~52
Legacy categorized FHIR response. Kept compatible for existing prototypes. For normalized platform-shaped data, use get_demo_health_record. Fixed fictional patient only.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional subset of normalized record categories. |
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
No examples provided.
get_demo_vitals Get synthetic vital signs (vitals) ~81
Use this to get only the vital signs (vitals) of FinchNode's fixed fictional sample EMR: 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.
search_demo_fhir Search synthetic FHIR resources ~64
Use this to get all resources of one FHIR R4 type from FinchNode's fixed fictional sample EMR.
| Name | Type | Req | Description |
|---|---|---|---|
| patient_id | string | – | Optional fixed sample patient filter. |
| resource_type | string | yes | FHIR resource type present in the sample EMR. |
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | – |
No examples provided.
simulate_demo_connect Simulate FinchNode Connect ~62
Use this to prototype the FinchNode connection journey. Returns a non-persistent, immediately complete synthetic session.
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| session | object | yes | – |
No examples provided.
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 76 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 13 tools: get_demo_health_record, get_demo_record, get_demo_fhir_bundle, search_demo_fhir, simulate_demo_connect, and 8 more. Their descriptions and schemas cost roughly 906 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.