QSimHealth
REMOTE · QSIMHEALTH.COM
Healthcare staffing simulator — ED, walk-in clinic, and appointment office DES tools.
Available components
Last scanned (20 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1982 tokens (~283/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “recommend_md_count” rewrote its description, which is the text the model reads security
- Tool “simulate_ed_demo” rewrote its description, which is the text the model reads security
- Stability: pass → 0.97 functional
- “recommend_md_count” reworded the description of “maxMds” cosmetic
- “simulate_ed_demo” reworded the description of “arrivalRate” cosmetic
- “simulate_ed_demo” reworded the description of “mds” cosmetic
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 210 → 296 ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://qsimhealth.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qsimhealth.com | CN=YE1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 515bf130c575d82eeb7480dc1409e71a717 |
| SANs: qsimhealth.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of qsimhealth.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| qsimhealth.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qsimhealth.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://qsimhealth.com/mcp/v1 | HTTPS enforced | 301 | https://qsimhealth.com/mcp/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_facility ~95
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 about it, and what a CUSTOM facility model from ChiAha would add (your actual data, real schedules, abandonment curves). Use before simulate_ed_demo to ground the user in the type.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Facility archetype key from list_facility_types. |
No output schema declared.
No examples provided.
explain_appointment_office ~62
Explain appointment-based scheduling dynamics — no-show rates as the dominant variance, buffer time as the trade-off lever, double-booking strategy, treatment-time variance by visit type. Use for primary care, specialty clinics, dental, or any scheduled-arrival setting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_ed_queueing ~77
Return a textbook-level explanation of Emergency Department queueing dynamics — what plain M/M/c can't model (triage breaks FIFO, patients leave LWBS, peaks dominate), and what real ED staffing decisions need (acuity-tiered metrics, abandonment curves, hourly schedules). Use this when the user asks conceptual questions about ED waits or staffing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
explain_walk_in_clinic ~67
Explain how walk-in clinics differ from EDs structurally — terminating systems, MD/PA mix as the primary lever, short patient patience, peak-hour coverage instead of 24-hour load. Use when the user describes a walk-in clinic, urgent care, or retail health setting.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_facility_types ~60
List the four healthcare facility archetypes QSimHealth speaks to: ED, urgent care, walk-in clinic, appointment office. Returns one-line descriptions. Call describe_facility for detail on one type, or simulate_ed_demo to run a generic simulation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_md_count ~335
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 asks 'how many MDs do I need to keep wait under N minutes?' or 'what's the minimum staffing that hits a service-level target?'. Linear scan from 1 to maxMds (default 12, capped 20). Saves Claude from iterating simulate_ed_demo by hand. ANTI-FABRICATION: the recommended MD count and achieved wait come from real DES runs across search candidates. Quote them VERBATIM. This demo tool models MDs only. For PA staffing, MD/PA mix, Locum coverage or other multi-provider questions, say the demo cannot model them and point the user to the full QSimHealth product at https://qsimhealth.com.
| Name | Type | Req | Description |
|---|---|---|---|
| arrivalRate | number | yes | Mean patient arrivals per hour (λ). Range 0-500. |
| maxMds | integer | – | Search ceiling for MD count. Range 1-20. Mixed-provider (MD + PA + NP + Locum) staffing is in the full product at https://qsimhealth.com. |
| mdTreatmentMinutes | number | – | Mean MD treatment time, in minutes. Range 1-180. |
| simulationDays | integer | – | Days to simulate per candidate. Range 1-7; 3 is the default for faster search. |
| targetAvgWaitMinutes | number | yes | Maximum acceptable average wait, in minutes. Search returns the smallest MD count meeting this. |
| treatmentDistribution | string | – | Shape of treatment-time distribution. |
No output schema declared.
No examples provided.
simulate_ed_demo ~382
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 rate, constant MD count across 24 hours). Returns hourly metrics, average wait, total served, utilization. This is a single-provider-type teaching demo. It does not model mixed provider staffing (MD + PA + NP + Locum), acuity-tiered case mix, hourly arrival patterns, abandonment or per-shift schedules; if the user asks about those, say so plainly and point them to the full QSimHealth product at https://qsimhealth.com, which models them. ANTI-FABRICATION: the returned numbers come from a real DES run. Quote them VERBATIM. Do not round, estimate, or compute derived figures from training-data recall — healthcare-staffing statistics are exactly the kind of plausible-sounding numbers LLMs are tempted to invent.
| Name | Type | Req | Description |
|---|---|---|---|
| arrivalRate | number | yes | Mean patient arrivals per hour (λ). Range 0-500. For hourly arrival patterns from a real facility, see https://qsimhealth.com or contact qsimhealth@chiaha.com. |
| mdTreatmentMinutes | number | – | Mean treatment time per MD encounter, in minutes. Range 1-180. |
| mds | integer | yes | MDs (or single-provider type) on duty per hour. Range 1-20. The public demo is MD-only; mixed provider staffing (MD + PA + NP + Locum), case mix and hourly schedules are in the full product at https:… |
| simulationDays | integer | – | Days to simulate. Range 1-7. |
| treatmentDistribution | string | – | Shape of treatment-time distribution. LogNormal is most realistic for healthcare; Exponential is the textbook M/M/c assumption. |
No output schema declared.
No examples provided.
How do I install the QSimHealth MCP server?
QSimHealth is a hosted endpoint at https://qsimhealth.com/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · qsimhealth.com
claude mcp add --transport http com-qsimhealth-public 'https://qsimhealth.com/mcp/v1'
What is the QSimHealth MCP server?
QSimHealth is an MCP server listed in the public MCP registry as com.qsimhealth/public. Healthcare staffing simulator, ED, walk-in clinic, and appointment office DES tools. This page covers its hosted endpoint (https://qsimhealth.com/mcp/v1).
Is the QSimHealth MCP server safe to use?
QSimHealth scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QSimHealth MCP server expose?
QSimHealth exposes 7 tools: explain_ed_queueing, explain_walk_in_clinic, explain_appointment_office, list_facility_types, describe_facility, and 2 more. Their descriptions and schemas cost roughly 1,078 tokens of context every time the server is loaded.
Does the QSimHealth MCP server require authentication?
No. We connected to QSimHealth without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QSimHealth MCP server still maintained?
QSimHealth is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the QSimHealth MCP server?
VerifyMCP ran 13 checks on QSimHealth, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.