ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Clinical Reasoning Prover with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Forces AI to validate clinical treatment plans against US guidelines (AHA, ACC) using real differential exclusion, explicit pharmacokinetics, and objective tria

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 1 capability

The complete Clinical Reasoning Prover capability set.

These are the exact actions your AI can choose when you ask it to work with Clinical Reasoning Prover.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through Clinical Reasoning Prover.

  1. 01

    Validate clinical reasoning

    This is NOT a diagnostic capability. it is a reasoning integrity check. You must: (1) detail PATIENT PRESENTATION. chief complaint with timeline, vital signs (BP, HR, RR, SpO2, Temp), HPI (onset, location, duration, character, aggravating/alleviating, radiation, timing, severity), relevant PMH, medications, allergies, social history. Structured, not narrative, (2) construct DIFFERENTIAL DIAGNOSIS. systematically. Use VINDICATE mnemonic (Vascular, Infectious, Neoplastic, Degenerative, Iatrogenic, Congenital, Autoimmune, Traumatic, Endocrine/metabolic) to ensure completeness. Rule out life-threatening "cannot miss" diagnoses FIRST. For chest pain: ACS, aortic dissection, PE, tension pneumothorax, esophageal rupture. before considering GERD, (3) cite EVIDENCE LEVEL. name the specific guideline (AHA 2023 STEMI Guidelines, ACC/AHA Chest Pain Evaluation, USPSTF Grade A Recommendation). Cite evidence class (I, IIa, IIb, III) and level (A, B-R, B-NR, C-LD, C-EO). "Standard of care" without a citation is not evidence-based, (4) analyze PHARMACOKINETICS. for every proposed medication: ADME (absorption route, distribution volume, metabolism pathway including CYP450 isoenzymes, elimination half-life and route). Adjust for renal function (CrCl/eGFR), hepatic function (Child-Pugh), age, weight. Check CYP450 inhibitor/inducer interactions with current medications, (5) assess TRIAGE SEVERITY. use validated, objective scales: ESI (1-5), GCS (3-15), qSOFA (0-3), HEART score, CHADS₂-VASc, Wells criteria. Justify the score with specific findings, (6) check CONTRAINDICATIONS. FDA black box warnings, absolute/relative contraindications, drug-drug interactions, allergies (including cross-reactivity classes), pregnancy category (Category X agents explicitly excluded), (7) propose TREATMENT PLAN. exact medication name (generic), dose, route, frequency, duration. Include monitoring parameters (labs, vitals, clinical signs) and follow-up timeline. "Give antibiotics" is rejected. "Ceftriaxone 1g IV q24h × 5 days, monitor Cr and WBC q48h" is required. If rejected, your clinical analysis has a structural deficiency. fix it before advising. Structured reflection capability for US clinical reasoning (AHA/ACC/FDA/USPSTF guidelines). Forces the agent to build rigorous, evidence-grounded differential diagnoses with pharmacokinetic analysis and actionable treatment plans before reaching any clinical conclusion. Catches Anchoring Bias (locking onto the first diagnosis without ruling out life-threatening differentials), Evidence Vacuum (citing "standard of care" without naming the AHA/ACC guideline or evidence level), Pharmacokinetic Blindness (prescribing without ADME analysis, CYP450 interactions, or renal/hepatic adjustments), Triage Confusion (no objective severity scoring. ESI, GCS, qSOFA. just "seems serious"), and Contraindication Omission (missing FDA black box warnings, cross-reactivities, pregnancy categories). Call once per clinical case analysis

Observed, not estimated

845ms average. Fast in production.

Clinical Reasoning Prover is checked daily against the live service.

Daily averagePeak 979ms
Aug 20Today
Fastest day
695ms
Slowest day
979ms
14-day trend
Slowing+9%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Clinical Reasoning Prover, so you can see the experience inside your AI.

It does not authenticate your account with Clinical Reasoning Prover. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Clinical Reasoning Prover Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_fskQynMT78EFGvL9AdlF1JoET4jVcG1rcrTlLgq9/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Clinical Reasoning Prover capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "clinical-reasoning-prover-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_fskQynMT78EFGvL9AdlF1JoET4jVcG1rcrTlLgq9/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Clinical Reasoning Prover owners ask.

  • 01

    Can this MCP query patient records or EMR?

    No. This is a strictly stateless reasoning gatekeeper. It does not access patient data, query external databases, or connect to EMRs. It validates the structural logic of the AI's clinical reasoning based on the inputs provided.

  • 02

    Why did the Prover reject my clinical plan with EVIDENCE_LEVEL_UNGROUNDED?

    Because the reasoning relied on vague appeals like 'standard of care' or 'clinical consensus'. To pass the Prover, you must cite specific US guidelines (e.g., AHA/ACC, USPSTF, IDSA) or established evidence levels (e.g., Class I, Level A) to justify the intervention.

  • 03

    What objective scales are required for the Triage Severity pivot?

    The Prover requires recognized objective scoring systems such as the Emergency Severity Index (ESI), Glasgow Coma Scale (GCS), qSOFA, or CHADS2-VASc. Subjective descriptors like 'very sick' or 'unstable' will trigger a TRIAGE_SEVERITY_BLIND rejection.