Heart Score Calculator MCP for AI. Instantly triage chest pain patients with clinical precision.

Q: How does Heart Score Calculator MCP determine if the patient needs immediate admission?

The system uses classifyriskandtriage first to assign 'High Risk' status. Then, calling recommendclinicalconduct('High Risk') generates mandatory directives for immediate inpatient admission and urgent investigation.

Q: What is the difference between classifyriskandtriage and recommendclinicalconduct?

classifyriskandtriage only provides a risk label (Low/Moderate/High) and a Triage Level. You must then use recommendclinicalconduct to get the actual, detailed medical actions required.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

How this MCP server connects to your AI agent

Heart Score Calculator determines acute myocardial infarction (AMI) risk by synthesizing five key clinical metrics: History, ECG findings, Age, Risk Factors, and Troponin levels.

This MCP provides immediate, guideline-backed scoring and triage recommendations for chest pain patients.

What AI agents can do with Heart Score Calculator Automation

Calculate heart score

Combines history, ECG, age, risk factor, and troponin data to provide a total HEART score for AMI assessment.

Classify risk and triage

Takes the calculated heart score and assigns an official 'Low', 'Moderate', or 'High' risk status along with a triage level.

Recommend clinical conduct

Generates specific, evidence-based medical recommendations for tests, management, and follow-up based on the final risk classification.

Calculate total HEART score

Aggregates five separate clinical metrics (History, ECG, Age, Risk Factor, Troponin) into a single numerical risk score.

Assign risk category and triage level

Takes the final calculated HEART score and determines if the patient is Low, Moderate, or High risk, assigning an immediate triage priority.

Generate clinical management pathways

Creates evidence-based next steps, including mandatory diagnostic tests and follow-up protocols, based on the assigned risk level.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

What AI agents can do with Heart Score Calculator: 3 Tools Available

These tools allow your AI client to calculate the total HEART score, determine the resulting clinical risk tier, and generate mandatory next steps for AMI patients.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using Heart Score Calculator on Vinkius

Calculate Heart Score

Combines history, ECG, age, risk factor, and troponin data to provide a total HEART score for AMI assessment.

Classify Risk And Triage

Takes the calculated heart score and assigns an official 'Low', 'Moderate', or...

Recommend Clinical Conduct

Generates specific, evidence-based medical recommendations for tests, management...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The Heart Score Calculator integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "heart-score-calculator": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the Heart Score Calculator tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"heart-score-calculator": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with Heart Score Calculator, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Heart Score Calculator. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 3 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

The struggle to standardize acute cardiac assessments, Solved with Vinkius AI Gateway

Right now, assessing chest pain involves gathering data from history sheets, interpreting physical ECGs, reviewing age brackets, and checking multiple blood levels. This process often requires clinicians to manually cross-reference several hospital protocols—checking the AHA guidelines here, verifying local EMS procedures there. It’s a highly variable system prone to human omission or conflicting departmental rules.

With this MCP, your AI client takes all those disparate data points and runs them through one unified model. You get an immediate, guideline-backed total score that dictates everything from triage level to required next steps, drastically reducing the time spent consulting protocols.

Heart Score Calculator: Clear Triage Directives

The biggest manual step that disappears is the complex mapping of a numeric score into specific care mandates. You no longer have to manually determine if an '8' means immediate cath lab activation or stable observation; the `recommend_clinical_conduct` tool handles that translation instantly.

What changes now is speed and certainty. Instead of debating which guideline applies, you get a single, authoritative command for action.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

heart-score

ami

ecg

troponin

triage

What your AI can actually do with this

When a patient presents with chest pain, doctors need more than just gut feelings; they need an objective risk score. This MCP takes the complex clinical data—history, ECG readings, comorbidities, and troponin levels—and structures it into a single, actionable assessment. Instead of spending time cross-referencing multiple hospital protocols or manually calculating scores across different sheets, your AI client handles the heavy lifting.

It first calculates a total HEART score from all five inputs. Next, it instantly maps that number to a specific risk category and defined triage priority. Finally, it generates mandatory diagnostic pathways, telling care teams exactly which tests to order and how the patient needs to be managed immediately. You'll connect this MCP via Vinkius, giving your agents instant access to standardized clinical decision support.

Built · Hosted · Managed by Vinkius Heart Score Calculator - AMI Triage MCP

Server ID 019ecb73-fd88-70c6-be6a-8c88fe6ca041

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is: your AI client converts scattered clinical data points into an immediate, clear action plan.

Feed the necessary patient data (History score, ECG findings, Age group, Risk Factor status, Troponin severity) into the system.

The MCP uses calculate_heart_score to combine these metrics and produce a total risk number from 0 to 10.

It then runs this total score through classify_risk_and_triage to assign a definitive risk level, followed by calling recommend_clinical_conduct for specific care directives.

What Changes When You Connect

Eliminate manual score calculation. The calculate_heart_score tool aggregates all five necessary components, giving you a single number instead of juggling multiple data inputs.

Ensure consistent patient care. The system doesn't just give advice; it uses classify_risk_and_triage to map the score directly to mandatory Low, Moderate, or High risk tiers, standardizing triage across shifts.

Get actionable next steps immediately. Instead of generic guidelines, recommend_clinical_conduct outputs a specific list of required tests and management directives for your care team.

Focus on diagnosis, not documentation. By automating the complex synthesis process, clinicians can dedicate their attention to patient care rather than cross-referencing multiple clinical pathways.

Reduce assessment variability. The MCP enforces adherence to AHA/ESC guidelines, ensuring every patient receives an objective score and protocol regardless of who is assessing them.

See it in action

01 01

Triage a suspected AMI in the ER

An incoming patient has chest pain. Instead of starting from scratch, your agent first runs calculate_heart_score using all available data. It gets a total score and immediately passes it to classify_risk_and_triage, which assigns 'High Risk' with Triage Level 3. This triggers the final step: calling recommend_clinical_conduct('High Risk') to mandate immediate admission protocols.

02 02

Follow up on a stable, low-score patient

A young patient is admitted with minimal symptoms and a calculated HEART score of 2. The agent uses classify_risk_and_triage to confirm 'Low Risk'. Then, it calls recommend_clinical_conduct('Low Risk'), which guides the care team toward safe outpatient follow-up rather than unnecessary imaging.

03 03

Reviewing complex comorbidities

Assessing an 85-year-old male with multiple risk factors. The agent calculates the score, confirming 'Moderate Risk'. It then uses recommend_clinical_conduct to get a specific ER guideline that adjusts for age and gender, ensuring the care plan is highly customized.

04 04

Validating initial assessment findings

A physician manually calculates a score but wants confirmation. The agent runs calculate_heart_score to validate the inputs. It then uses classify_risk_and_triage to confirm the risk tier before running recommend_clinical_conduct('Moderate Risk') for final sign-off.

The honest tradeoffs

Treating it like a simple calculator

Anti-pattern

Just entering age and troponin levels into the tool, assuming it will give full guidance. This only provides partial data, ignoring history or ECG findings.

The Fix

Always run the calculation by providing all five metrics (History, ECG, Age, Risk Factor, Troponin) first using calculate_heart_score. Never skip a component; completeness is key.

Stopping after scoring

Anti-pattern

Getting only the 'High Risk' score but not knowing what to do next. A score means nothing without an action plan.

The Fix

After getting the score and risk classification from classify_risk_and_triage, you MUST call recommend_clinical_conduct with that risk status. This generates the necessary, actionable directives.

Using it for non-cardiac pain

Anti-pattern

Trying to assess abdominal pain using this tool. The scoring mechanism is specific only to AMI and chest pain presentations.

The Fix

This MCP is strictly for acute myocardial infarction assessment of chest pain patients. Use different tools designed for GI or musculoskeletal pain evaluation.

When It Fits, When It Doesn't

Use this MCP if your primary need is standardizing the immediate triage and management plan for a patient presenting with symptoms suggestive of AMI, requiring adherence to established clinical pathways. You must be able to provide scores across all five components (H, E, A, R, T). Don't use it if you are only trying to calculate one isolated component, like just Age or just Troponin; those tools aren't available here. Similarly, don't rely on this MCP for definitive diagnosis—it is a decision support tool. If you need comprehensive diagnostic imaging scheduling across multiple departments, look for a separate EMR integration rather than relying solely on the recommend_clinical_conduct output.

Questions you might have

How does Heart Score Calculator MCP determine if the patient needs immediate admission? +

The system uses classify_risk_and_triage first to assign 'High Risk' status. Then, calling recommend_clinical_conduct('High Risk') generates mandatory directives for immediate inpatient admission and urgent investigation.

Does Heart Score Calculator MCP work if I only have ECG data? +

The tool can calculate a score even with missing information, as many inputs are optional. However, the resulting recommendation will be less definitive without full history and troponin details.

What is the difference between `classify_risk_and_triage` and `recommend_clinical_conduct`? +

classify_risk_and_triage only provides a risk label (Low/Moderate/High) and a Triage Level. You must then use recommend_clinical_conduct to get the actual, detailed medical actions required.

Can Heart Score Calculator MCP run an assessment for someone over 80? +

Yes. The scoring tools are designed to take age groups into account when calculating risk and generating clinical recommendations, ensuring the care plan is tailored to the patient's demographic.

What type of data does calculate_heart_score need? +

It requires five components: History score, ECG findings score, Age factor score, Risk Factor status, and Troponin severity. Missing inputs simply default the component score to zero.

How this MCP server connects to your AI agent

Heart Score Calculator determines acute myocardial infarction (AMI) risk by synthesizing five key clinical metrics: History, ECG findings, Age, Risk Factors, and Troponin levels.This MCP provides immediate, guideline-backed scoring and triage recommendations for chest pain patients.

What AI agents can do with Heart Score Calculator Automation

Calculate heart score

Classify risk and triage

Recommend clinical conduct

What AI agents can do with Heart Score Calculator: 3 Tools Available

Calculate Heart Score

Combines history, ECG, age, risk factor, and troponin data to provide a total HEART score for AMI assessment.

Classify Risk And Triage

Takes the calculated heart score and assigns an official 'Low', 'Moderate', or...

Recommend Clinical Conduct

Generates specific, evidence-based medical recommendations for tests, management...

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The struggle to standardize acute cardiac assessments, Solved with Vinkius AI Gateway

Heart Score Calculator: Clear Triage Directives

heart-score

ami

ecg

troponin

triage

What your AI can actually do with this

Here's how it actually works

Who is this actually for?

What Changes When You Connect

Triage a suspected AMI in the ER

Follow up on a stable, low-score patient

Reviewing complex comorbidities

Validating initial assessment findings

The honest tradeoffs

Treating it like a simple calculator

Stopping after scoring

Using it for non-cardiac pain

When It Fits, When It Doesn't

Questions you might have

Heart Score Calculator determines acute myocardial infarction (AMI) risk by synthesizing five key clinical metrics: History, ECG findings, Age, Risk Factors, and Troponin levels.

This MCP provides immediate, guideline-backed scoring and triage recommendations for chest pain patients.