qsimhealth.com

Item: qsimhealth.com
Rating: 86
Author: wmcp.sh

https://qsimhealth.com/mcp/v1

86/100 · MCP Trust Grade · checked 6h ago · MCP 2025-06-18

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 7 tools · Productivity

explain_ed_queueing

Return a textbook-level explanation of Emergency Department queueing dynamics — what plain M/M/c can't model (triage breaks FIFO, patients leave LWBS,

explain_walk_in_clinic

Explain how walk-in clinics differ from EDs structurally — terminating systems, MD/PA mix as the primary lever, short patient patience, peak-hour cove

explain_appointment_office

Explain appointment-based scheduling dynamics — no-show rates as the dominant variance, buffer time as the trade-off lever, double-booking strategy, t

list_facility_types

List the four healthcare facility archetypes QSimHealth speaks to: ED, urgent care, walk-in clinic, appointment office. Returns one-line descriptions.

describe_facility

Return detailed info on one facility type: typical arrival pattern, MD/PA mix, common pain points, what a sim with simulate_ed_demo would teach you ab

simulate_ed_demo

Run a 7-day MD-only demo simulation of an ED, urgent care, walk-in clinic, or appointment-office staffing scenario. Inputs are flat (constant arrival

recommend_md_count

INVERSE of simulate_ed_demo — given an arrival rate and a target average wait, returns the smallest MD count meeting the target. Use when the user ask

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 7 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

7 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%92

single-probe latency 307ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%46

43% of tools have typed inputSchema
0/7 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade qsimhealth.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — qsimhealth.com grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/qsimhealth.com

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/qsimhealth.com/badge.svg)](https://wmcp.sh/mcp/grade/qsimhealth.com)

HTML

<a href="https://wmcp.sh/mcp/grade/qsimhealth.com"><img src="https://wmcp.sh/mcp/grade/qsimhealth.com/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.