Clinresolve Server

v2.0.0

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
    "clinresolve-server": {
      "url": "https://clinserver-6a5b14af-genx-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
    "clinresolve-server": {
      "serverUrl": "https://clinserver-6a5b14af-genx-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"
    }
  }
}

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

[mcp_servers.clinresolve-server]
url = "https://clinserver-6a5b14af-genx-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp"

Connect directly using the Server-Sent Events endpoint:

https://clinserver-6a5b14af-genx-amrita-university-amritapuri-campus.app.nitrocloud.ai/mcp
Available Tools
select-patient

Load a patient profile by patient ID, including demographics, conditions, allergies, active medications, and recent labs.

collect-evidence

Collect and reconcile evidence for a drug from RxNorm, OpenFDA, DailyMed, RxNav Drug Interactions, PubMed, ClinicalTrials.gov, hospital guidelines, and clinical literature — ranked by Trust Engine scoring with temporal reasoning applied. Conflicts are detected and annotated with the preferred source and rationale.

list-patients

List all patients in the system with their demographics, active medications, and conditions. Use this to browse available patients before selecting one for a medication check.

generate-decision

Run the full Evidence Reconciliation pipeline for a given drug and patient. Collects evidence from RxNorm, OpenFDA, DailyMed, RxNav, PubMed, ClinicalTrials.gov, HospitalGuidelines, and ClinicalEvidence; detects conflicts; applies Trust Engine ranking and Temporal Reasoning; applies patient context and hospital policies; computes reliability metrics; and produces a deterministic APPROVE / CAUTION / AVOID recommendation. The recommendation is NOT generated by an LLM — use the explain-decision prompt afterwards to get a narrative.

get-audit-history

Retrieve the complete audit history of all clinical decisions generated in this session, merged with seeded historical records from the fixture data. Returns decisions sorted newest-first, with full reasoning trails and reliability metrics.

search-pubmed

Search PubMed (NCBI) for research articles relevant to a drug or clinical query. Returns article titles, authors, journals, and publication dates. Results are cached for 6 hours.

lookup-dailymed

Retrieve the FDA-approved Structured Product Label (SPL) from DailyMed for a drug. Extracts indications, contraindications, warnings, drug interactions, and adverse reactions. Results are cached for 12 hours.

lookup-clinical-trials

Search ClinicalTrials.gov for clinical studies relevant to a drug. Returns study title, phase, status (COMPLETED/RECRUITING/TERMINATED), and brief summary. Completed Phase 3/4 trials are marked supportive; terminated/suspended trials are marked caution.

calculate-decision-reliability

Re-compute structured reliability metrics for a drug+patient combination on demand. Returns 5 metrics: evidenceCompleteness, sourceAgreement, policyCompliance, patientContextCoverage, evidenceFreshness — all in range 0-1.

compare-evidence-sources

Collect evidence for a drug and return a head-to-head comparison of all sources, showing their trust scores, stances, and authority rankings side by side. Use this to understand which sources agree/disagree and why.

recommend-alternative

Deterministically suggest a safer alternative medication for a patient when the requested drug has a CAUTION or AVOID verdict. Looks up the alternatives table from evidence fixtures and runs a quick viability check against the patient's allergy profile.

simulate-patient-change

Re-run the full decision pipeline with a hypothetically modified patient context. Useful for answering "what if" questions: what if the patient didn't have CKD? What if amiodarone was removed from their medication list? What if their eGFR was 90 instead of 35? Supports changes to: conditions (add/remove), medications (remove), labs (override eGFR/INR/creatinine).

find-similar-cases

Search the audit history for past clinical decisions involving the same drug or patients with similar conditions. Useful for longitudinal care continuity and precedent review.

get-api-status

Returns the real-time health status of all external evidence API providers: RxNorm, OpenFDA, DailyMed, PubMed, ClinicalTrials.gov, and RxNav Drug Interactions. Includes average latency, success/error counts, cache hit rate, and whether mock fallback is active.

generate-evidence-graph

Build and return a structured Evidence Graph for a drug + patient combination. The graph contains nodes (Drug, Patient, Condition, LabResult, DrugInteraction, FdaWarning, ClinicalGuideline, ClinicalTrial, ResearchPaper, HospitalPolicy) and typed edges (contraindicated_with, supported_by, conflicts_with, recommends, overrides, requires, associated_with). Each node carries metadata: source, authority, freshness, confidence, evidenceLevel.

explain-conflict

Given a drug and patient, identify all evidence conflicts detected during reconciliation and explain which source was preferred and why (based on Trust Engine scoring). Use this to understand WHY the system sided with one piece of evidence over another.