Healthcare Context Intelligence Engine

v0.3.1

A powerful MCP server built with NitroStack

Connection Setup

Add via Cursor Settings UI (Settings > Features > MCP > Add New MCP Server):

{
  "mcpServers": {
    // your other mcp servers
    "healthcare-context-intelligence-engine": {
      "url": "https://synapsemed-a-healt-teamteam-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
    }
  }
}

Connect remote tools directly via Claude's Web UI:

Add custom connector BETA
Connect Claude to your data and tools. Learn more about connectors or get started with pre-built ones.
Advanced settings
Only use connectors from developers you trust. Anthropic does not control which tools developers make available and cannot verify that they will work as intended or that they won't change.

Configure custom tools directly via ChatGPT's Web UI:

New App
PNG only. Best results at 256 x 256 px or larger. Max file size: 10 KB
Custom MCP servers introduce risk. Learn more
OpenAI hasn't reviewed this MCP server. Attackers may attempt to steal your data or trick the model into taking unintended actions, including destroying data.

Add the following configuration block under mcpServers in your Antigravity configuration file (~/.gemini/config/mcp_config.json):

{
  "mcpServers": {
    // your other mcp servers
    "healthcare-context-intelligence-engine": {
      "serverUrl": "https://synapsemed-a-healt-teamteam-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
    }
  }
}

Add the following configuration block to your Codex configuration file (~/.codex/config.toml):

[mcp_servers.healthcare-context-intelligence-engine]
url = "https://synapsemed-a-healt-teamteam-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"

Connect directly using the Server-Sent Events endpoint:

https://synapsemed-a-healt-teamteam-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp
Available Tools
classify_intent

Classify emergency type and severity hint from raw text input (non-diagnostic)

parse_intent

Parse raw input into structured emergency orchestration intent

extract_goal

Extract prioritized actionable goals from classified intent

build_plan

Build a complete emergency execution plan from raw input. Runs discovery, retrieval, context, generation, and validation concurrently. Returns a plan object requiring human approval before execution-class actions.

get_patient_summary

Retrieve normalized patient summary for emergency orchestration (non-diagnostic)

get_allergies

List patient allergies by patient_id

get_medications

List active medications by patient_id

search_hospitals

Search and rank hospitals by query, location, and filters

nearest_hospital

Find nearest hospital matching required departments

available_departments

List departments available at a hospital

current_location

Resolve location text to lat/long coordinates

distance

Calculate distance in km between origin and destination

route

Calculate route and ETA between origin and destination

context_intelligence_score

Compute weighted context intelligence score for a retrieval item

hybrid_retrieve

Hybrid retrieve and score hospital candidates

rerank

Re-rank retrieval results by rerank_score descending

build_context_graph

Build context graph from intent, discovery, and ranked hospitals

infer_priority

Infer priority resource flags from intent and discovery context

build_plan_prompt

Build an LLM-ready prompt from intent and compressed context. Includes non-diagnostic constraints. Returns the prompt string and system prompt.

compress_context

Compress a full HCIE context (patient, hospitals, contacts, maps) into a token-efficient summary. Preserves: allergies, emergency contacts, symptoms (always). Boosts: location + hospital for dispatch intent.

validate_plan

Validate an ExecutionPlan for structural correctness: required fields, non-empty steps, valid action names, correct step ordering.

check_safety

Hard safety gate — scans plan text for diagnostic or prescriptive language. Returns safe=false and the offending terms if any diagnostic language is detected. This gate is enforced at code level and cannot be bypassed.

explain_plan

Generate a concise, user-facing, non-diagnostic explanation of an ExecutionPlan. Summarizes steps in plain English without clinical language.

confirm_plan

Human approval gate for an ExecutionPlan. Call with approved=true to unlock execution-class actions (call_ambulance, connect_physician). Call with approved=false to deny the plan. This gate is enforced at code level — execution-class tools will throw if called without approval.

call_ambulance

🚑 EXECUTION-CLASS — Dispatch an ambulance to the patient location. Requires confirm_plan(plan_id, approved=true) to have been called first. Will throw an error if the plan is not approved.

connect_physician

👨‍⚕️ EXECUTION-CLASS — Connect to an available physician for the case. Requires confirm_plan(plan_id, approved=true) to have been called first. Will throw an error if the plan is not approved.

notify_family

Send emergency notification to a family/emergency contact by contact_id.

navigate

Generate navigation instructions from current location to a hospital.

share_location

Share the case location with a recipient (hospital, contact, dispatcher).

share_patient_summary

Share a non-diagnostic patient context summary with the receiving hospital or physician.