_ registry / mcp streamable-http · checked 1h ago

finchnode-public-demo

https://api.finchnode.com

Registry code: 44fed82396d40fb0

api record

All FinchNode demo tools return fictional records from 12 named synthetic scenarios drawn from two synthetic sources, Northstar Health System (Synthetic) and Quillhaven Medical Group (Synthetic). Call list_demo_scenarios to choose a scenario: tools that accept scenario default to baseline-adult, and the per-category tools always serve it. Behavior scenarios return the same scripted errors and partial results as the REST demo. 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…

endpoint
https://api.finchnode.com/demo/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is finchnode-public-demo live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is finchnode-public-demo free to use?
Yes — the hub reached it with no key and no payment.
What tools does finchnode-public-demo have?
14 tools: get_demo_health_record, get_demo_vitals, list_demo_scenarios, get_demo_record, get_demo_fhir_bundle, search_demo_fhir, simulate_demo_connect, get_demo_medications, ….
Is finchnode-public-demo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
593ms

last good check

priced tools
0

of 14 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 14 tools
3 open 11 never probed 3 of 14 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_demo_allergies open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_conditions open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_demographics open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_health_record unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "scenario": {
      "enum": [
        "baseline-adult",
        "polypharmacy-senior",
        "pediatric-asthma",
        "multi-source-overlap",
        "sparse-record",
        "messy-coding",
        "rate-limited",
        "consent-revoked",
        "consent-partial",
        "source-unavailable"
      ],
      "type": "string",
      "description": "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 error or partial result as the REST demo."
    },
    "categories": {
      "type": "array",
      "items": {
        "enum": [
          "demographics",
          "medications",
          "conditions",
          "labs",
          "vitals",
          "allergies",
          "immunizations",
          "encounters",
          "documents",
          "claims"
        ],
        "type": "string"
      },
      "minItems": 1
    }
  }
}
    arguments 41 lines
  • get_demo_vitals unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • list_demo_scenarios unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_record unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "scenario": {
      "enum": [
        "baseline-adult",
        "polypharmacy-senior",
        "pediatric-asthma",
        "multi-source-overlap",
        "sparse-record",
        "messy-coding",
        "rate-limited",
        "consent-revoked",
        "consent-partial",
        "source-unavailable"
      ],
      "type": "string",
      "description": "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 error or partial result as the REST demo."
    },
    "categories": {
      "type": "array",
      "items": {
        "enum": [
          "demographics",
          "medications",
          "conditions",
          "labs",
          "vitals",
          "allergies",
          "immunizations",
          "encounters"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Optional subset of normalized record categories."
    }
  }
}
    arguments 40 lines
  • get_demo_fhir_bundle unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "scenario": {
      "enum": [
        "baseline-adult",
        "polypharmacy-senior",
        "pediatric-asthma",
        "multi-source-overlap",
        "sparse-record",
        "messy-coding",
        "rate-limited",
        "consent-revoked",
        "consent-partial",
        "source-unavailable"
      ],
      "type": "string",
      "description": "Optional scenario id from list_demo_scenarios. Omitted means baseline-adult."
    }
  }
}
    arguments 22 lines
  • search_demo_fhir unknown never probed

    Use this to get all resources of one FHIR R4 type for one synthetic scenario's patient (baseline-adult unless patient_id names another).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "resource_type"
  ],
  "properties": {
    "patient_id": {
      "enum": [
        "patient-demo-001",
        "patient-demo-polypharmacy",
        "patient-demo-pediatric-asthma",
        "patient-demo-multi-source",
        "patient-demo-sparse",
        "patient-demo-messy-coding",
        "patient-demo-rate-limited",
        "patient-demo-consent-revoked",
        "patient-demo-consent-partial",
        "patient-demo-source-unavailable"
      ],
      "type": "string",
      "description": "Optional scenario subject from list_demo_scenarios. Omitted searches the baseline-adult Bundle only."
    },
    "resource_type": {
      "enum": [
        "AllergyIntolerance",
        "Appointment",
        "CareTeam",
        "Condition",
        "Coverage",
        "DiagnosticReport",
        "DocumentReference",
        "Encounter",
        "ExplanationOfBenefit",
        "Immunization",
        "MedicationAdministration",
        "MedicationDispense",
        "MedicationRequest",
        "Observation",
        "Organization",
        "Patient",
        "Practitioner",
        "Provenance"
      ],
      "type": "string",
      "description": "FHIR R4 resource type present in the synthetic scenario Bundles."
    }
  }
}
    arguments 49 lines
  • simulate_demo_connect unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "scenario": {
      "enum": [
        "baseline-adult",
        "polypharmacy-senior",
        "pediatric-asthma",
        "multi-source-overlap",
        "sparse-record",
        "messy-coding",
        "rate-limited",
        "consent-revoked",
        "consent-partial",
        "source-unavailable",
        "connect-cancelled",
        "connect-failed"
      ],
      "type": "string",
      "description": "Optional scenario id from list_demo_scenarios. Omitted means baseline-adult; connect-cancelled and connect-failed end without a patient."
    },
    "categories": {
      "type": "array",
      "items": {
        "enum": [
          "demographics",
          "medications",
          "conditions",
          "labs",
          "vitals",
          "allergies",
          "immunizations",
          "encounters"
        ],
        "type": "string"
      },
      "minItems": 1,
      "description": "Requested fictional record categories."
    },
    "external_user_id": {
      "type": "string",
      "pattern": "^[A-Za-z0-9._:-]+$",
      "maxLength": 100,
      "description": "Optional non-sensitive prototype identifier. Never send a real patient identifier."
    }
  }
}
    arguments 48 lines
  • get_demo_medications unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_labs unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_immunizations unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • get_demo_encounters unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 44fed82396d40fb0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/44fed82396d40fb0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/44fed82396d40fb0/badge.svg)](https://brick.blue/agent/44fed82396d40fb0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.