Medcalc MCP Server

medcalc PyPI v0.4.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for Medical Calculation

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 98/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 2 = 98. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 66

Each tool and what it can reach — statically extracted from the published source.

  • aa_gradientno sensitive capability
  • abw_calculatorno sensitive capability
  • anion_gap_delta_deltano sensitive capability
  • apache2_scoreno sensitive capability
  • ariscat_scoreno sensitive capability
  • ascvd_10yr_riskno sensitive capability
  • bmi_bsa_calculatorno sensitive capability
  • bmi_calculatorno sensitive capability
  • bp_childrenno sensitive capability
  • bsa_calculatorno sensitive capability
Show 56 more tools ↓
  • calculate_mmeno sensitive capability
  • caprini_scoreno sensitive capability
  • centor_score_modifiedno sensitive capability
  • chads2_vasc_scoreno sensitive capability
  • child_pugh_scoreno sensitive capability
  • ciwa_ar_scoreno sensitive capability
  • corrected_calciumno sensitive capability
  • corrected_sodiumno sensitive capability
  • corrected_sodium_hillierno sensitive capability
  • corrected_sodium_katzno sensitive capability
  • crcl_cockcroft_gaultno sensitive capability
  • curb65_scoreno sensitive capability
  • duke_activity_status_indexno sensitive capability
  • egfr_epino sensitive capability
  • egfr_epi_cr_cysno sensitive capability
  • fib4_indexno sensitive capability
  • fractional_excretion_of_sodiumno sensitive capability
  • framingham_risk_scoreno sensitive capability
  • free_water_deficitno sensitive capability
  • gad7_scoreno sensitive capability
  • glasgow_coma_scaleno sensitive capability
  • grace_acs_scoreno sensitive capability
  • gupta_perioperative_micano sensitive capability
  • has_bled_scoreno sensitive capability
  • heart_scoreno sensitive capability
  • homa_irno sensitive capability
  • ibw_abw_calculatorno sensitive capability
  • ibw_calculatorno sensitive capability
  • infusion_rateno sensitive capability
  • ldl_calculatedno sensitive capability
  • maintenance_fluidsno sensitive capability
  • map_calculatorno sensitive capability
  • mdrd_gfrno sensitive capability
  • meld_3no sensitive capability
  • news2_scoreno sensitive capability
  • nihss_scoreno sensitive capability
  • pecarn_pediatric_head_injuryno sensitive capability
  • perc_ruleno sensitive capability
  • phq9_scoreno sensitive capability
  • pregnancy_calculatorno sensitive capability
  • prevent_cvd_riskno sensitive capability
  • psi_port_scoreno sensitive capability
  • qtc_calculatorno sensitive capability
  • revised_cardiac_risk_indexno sensitive capability
  • sepsis_criteriano sensitive capability
  • serum_anion_gapno sensitive capability
  • serum_osmolarityno sensitive capability
  • sofa_scoreno sensitive capability
  • steroid_conversionno sensitive capability
  • stop_bang_scoreno sensitive capability
  • timi_nstemino sensitive capability
  • timi_stemino sensitive capability
  • ventilator_tidal_volumeno sensitive capability
  • wells_dvt_criteriano sensitive capability
  • wells_pe_criteriano sensitive capability
  • winters_formulano sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.4.0 latest A 98/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/medcalc/badge.svg)](https://mcptrustchecker.com/registry/medcalc)
HTML
<a href="https://mcptrustchecker.com/registry/medcalc"><img src="https://mcptrustchecker.com/registry/medcalc/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/medcalc/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan medcalc --online --registry pypi

Use the free API → How scoring works

More in Developer Tools