Skip to main content
Glama
claudiomedina17

CardioTriage MCP Server

by claudiomedina17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CARDIOTRIAGE_MCP_HOSTNoHost address for Streamable HTTP transport.127.0.0.1
CARDIOTRIAGE_MCP_PATHNoPath for Streamable HTTP transport endpoint./mcp
CARDIOTRIAGE_MCP_PORTNoPort for Streamable HTTP transport.8000
CARDIOTRIAGE_MCP_TRANSPORTNoTransport protocol for MCP server. Set to 'streamable-http' for HTTP transport.stdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "ai.promptopinion/fhir-context": {
    "scopes": [
      {
        "name": "patient/Patient.rs",
        "required": true
      },
      {
        "name": "patient/Observation.rs"
      },
      {
        "name": "patient/MedicationStatement.rs"
      },
      {
        "name": "patient/Condition.rs"
      }
    ]
  }
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_synthetic_casesA

List available synthetic demo cases. Use first when an agent needs to discover CardioTriage case IDs. NOT for clinical use.

get_fhir_case_bundleA

Return a synthetic FHIR-like bundle for case A, B, C, or D. Use after selecting a case ID. Synthetic data only; NOT for clinical use.

analyze_missing_critical_dataA

Flag missing or pending critical cardiovascular triage data for a synthetic case. Use before risk disposition. NOT for clinical use.

summarize_cardiovascular_risk_signalsA

Summarize deterministic cardiovascular risk signals for a synthetic case. Use for STEMI, HF/Chagas, or low-risk pattern triage. NOT for clinical use.

generate_structured_handoff_noteA

Generate a deterministic SBAR-style handoff note for a synthetic case in English, Spanish, or Portuguese. Use after risk and missing-data review. NOT for clinical use.

interpret_12_lead_ecgA

Run AI-ECG analysis on a 12-lead recording. Default case_id mode uses precomputed ECGFounder embeddings; advanced raw ECG mode routes to live inference when available. Returns uncalibrated demo scores. NOT for clinical use.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct aspect of the workflow: listing cases, retrieving data, analyzing ECG, summarizing risk, checking missing data, and generating a handoff note. No two tools have overlapping purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., list_synthetic_cases, interpret_12_lead_ecg), using snake_case throughout. No mixing of conventions or vague verbs.

Tool Count5/5

Six tools is well-scoped for a synthetic triage demo, covering discovery, data retrieval, multiple analysis types, and output generation. Neither too few nor too many for the purpose.

Completeness5/5

The tool set covers the complete triage workflow: case selection, data retrieval, ECG interpretation, risk signal extraction, missing data check, and handoff note generation. No obvious gaps for a synthetic demo.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources