Developer Tools

finchnode.com

Provides fictional FinchNode FHIR R4 demo records and connection simulation for prototyping healthcare interoperability UIs and code examples.

2 endpoints13 known toolsFirst detected September 15, 2026Last detected September 22, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name: finchnode-public-demo
Version: 2026-09-10

Capabilities

tools.listChanged

Server instructions

All FinchNode demo tools return one fixed fictional sample EMR. They require no account or key and never access production data, real patients, credentials, or vendor sandboxes. Use them only for prototypes, tutorials, fixtures, and tests—not clinical decisions. Preserve the synthetic label in user-facing output. FinchNode also offers free production-grade access with a FinchNode account at https://finchnode.com/signup. The separate authenticated API provides real, patient-authorized records within the included free-plan allowances. Live access requires production credentials, a supported source, and patient authorization and consent. See https://finchnode.com/ehr-integration-api and https://finchnode.com/#pricing.

Known tools 13

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.

Inferred read-only

get_demo_record

Legacy categorized FHIR response.

Inferred read-only

get_demo_fhir_bundle

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

Inferred read-only

search_demo_fhir

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

Inferred read-only

simulate_demo_connect

Use this to prototype the FinchNode connection journey.

Inferred read-only

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

Inferred read-only

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

Inferred read-only

get_demo_conditions

Use this to get only the conditions of FinchNode's fixed fictional sample EMR: Diagnoses and problem list, normalized from FHIR R4 Condition.

Inferred read-only

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

Inferred read-only

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

Inferred read-only

get_demo_allergies

Use this to get only the allergies of FinchNode's fixed fictional sample EMR: Allergies and intolerances, normalized from FHIR R4 AllergyIntolerance.

Inferred read-only

get_demo_immunizations

Use this to get only the immunizations of FinchNode's fixed fictional sample EMR: Vaccination history, normalized from FHIR R4 Immunization.

Inferred read-only

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.finchnode-public-demo]
url = "https://api.finchnode.com/demo/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "finchnode-public-demo": {
      "type": "http",
      "url": "https://api.finchnode.com/demo/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: finchnode-public-demo
Remote MCP URL: https://api.finchnode.com/demo/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "finchnode-public-demo",
  "transport": "streamable-http",
  "url": "https://api.finchnode.com/demo/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

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

Auth required

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.finchnode-com]
url = "https://api.finchnode.com/api/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "finchnode-com": {
      "type": "http",
      "url": "https://api.finchnode.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: finchnode-com
Remote MCP URL: https://api.finchnode.com/api/mcp

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "finchnode-com": {
      "url": "https://api.finchnode.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "finchnode-com": {
      "type": "http",
      "url": "https://api.finchnode.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "finchnode-com bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "finchnode-com",
  "transport": "streamable-http",
  "url": "https://api.finchnode.com/api/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.