# FinchNode Synthetic Health Records (remote · api.finchnode.com)

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

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.finchnode.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-finchnode-health-records-demo/demo-mcp.md), [page](https://verifymcp.io/servers/com-finchnode-health-records-demo/demo-mcp)

## Channel facts

- Endpoint: `https://api.finchnode.com/demo/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1047 tokens (~80/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-finchnode-health-records-demo": {
      "type": "remote",
      "url": "https://api.finchnode.com/demo/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-finchnode-health-records-demo --url 'https://api.finchnode.com/demo/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-finchnode-health-records-demo:
    url: "https://api.finchnode.com/demo/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-finchnode-health-records-demo": {
      "Transport": "http",
      "Url": "https://api.finchnode.com/demo/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-finchnode-health-records-demo -t streamable-http -u 'https://api.finchnode.com/demo/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 75, +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.

### 2026-09-22 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 74)

First indexed and scored.

## MCP tools (13)

### `get_demo_health_record` (~93 tokens)

Get platform-shaped synthetic 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). Fixed fictional patient only; consent and sync are simulated, with no usable receipts or change cursor. Empty categories describe this fixture only.

Input parameters:

- `categories` (array)

Output parameters:

- `record` (object)

### `get_demo_record` (~52 tokens)

Get synthetic health record

Legacy categorized FHIR response. Kept compatible for existing prototypes. For normalized platform-shaped data, use get_demo_health_record. Fixed fictional patient only.

Input parameters:

- `categories` (array): Optional subset of normalized record categories.

Output parameters:

- `record` (object)

### `get_demo_fhir_bundle` (~34 tokens)

Get synthetic FHIR Bundle

Use this when a prototype or test needs the complete fictional FinchNode FHIR R4 Bundle and its resource references.

Output parameters:

- `bundle` (object)

### `search_demo_fhir` (~64 tokens)

Search synthetic FHIR resources

Use this to get all resources of one FHIR R4 type from FinchNode's fixed fictional sample EMR.

Input parameters:

- `patient_id` (string): Optional fixed sample patient filter.
- `resource_type` (string, required): FHIR resource type present in the sample EMR.

Output parameters:

- `bundle` (object)

### `simulate_demo_connect` (~62 tokens)

Simulate FinchNode Connect

Use this to prototype the FinchNode connection journey. Returns a non-persistent, immediately complete synthetic session.

Input parameters:

- `categories` (array): Requested fictional record categories.
- `external_user_id` (string): Optional non-sensitive prototype identifier. Never send a real patient identifier.

Output parameters:

- `session` (object)

### `get_demo_demographics` (~79 tokens)

Get synthetic basic details (demographics)

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.

Output parameters:

- `record` (object)

### `get_demo_medications` (~73 tokens)

Get synthetic medications

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.

Output parameters:

- `record` (object)

### `get_demo_conditions` (~68 tokens)

Get synthetic conditions

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.

Output parameters:

- `record` (object)

### `get_demo_labs` (~76 tokens)

Get synthetic lab results (labs)

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.

Output parameters:

- `record` (object)

### `get_demo_vitals` (~81 tokens)

Get synthetic vital signs (vitals)

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.

Output parameters:

- `record` (object)

### `get_demo_allergies` (~72 tokens)

Get synthetic allergies

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.

Output parameters:

- `record` (object)

### `get_demo_immunizations` (~71 tokens)

Get synthetic immunizations

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.

Output parameters:

- `record` (object)

### `get_demo_encounters` (~81 tokens)

Get synthetic visits (encounters)

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.

Output parameters:

- `record` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-finchnode-health-records-demo/demo-mcp#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 75
- 2026-09-23: 75
- 2026-09-22: 74
- 2026-09-21: 74

## Common questions

### 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.

## Links

- Remote endpoint: https://api.finchnode.com/demo/mcp
- Website: https://finchnode.com/developers/demo-api
- Changelog RSS feed: https://verifymcp.io/servers/com-finchnode-health-records-demo/demo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-finchnode-health-records-demo/demo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-finchnode-health-records-demo/demo-mcp