MCP server that wraps the Dagster GraphQL API — manage runs, assets, schedules, sensors, and backfills from any MCP client
Nothing to run from here
QSimHealth is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Healthcare staffing simulator — ED, walk-in clinic, and appointment office DES tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http qsimhealth-mcp https://qsimhealth.com/mcp/v1
# 2 — ask your agent for something these tools do
# explain_ed_queueing, explain_walk_in_clinic, explain_appointment_office and 4 more
QSimHealth costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
QSAll 1 server
qsimhealth1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http qsimhealth-mcp https://qsimhealth.com/mcp/v1Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Facility archetype key from list_facility_types. |
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 — **for MIXED PROVIDER STAFFING (MD + PA + NP + Locum), acuity-tiered case mix, hourly arrival pat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| arrivalRate | number | yes | Mean patient arrivals per hour (λ). Range 0-500. For real-facility hourly arrival patterns from your data, sign up at https://qsimhealth.com or contact qsimhealth@chiaha.com. |
| mds | integer | yes | MDs (or single-provider type) on duty per hour. Range 1-20. The public demo is MD-only — for MIXED PROVIDER staffing (MD + PA + NP + Locum), acuity-tiered case mix, and hourly schedules, sign up at ht |
| mdTreatmentMinutes | number | no | Mean treatment time per MD encounter, in minutes. Range 1-180. |
| simulationDays | integer | no | Days to simulate. Range 1-7. |
| treatmentDistribution | string | no | Shape of treatment-time distribution. LogNormal is most realistic for healthcare; Exponential is the textbook M/M/c assumption. |
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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| arrivalRate | number | yes | Mean patient arrivals per hour (λ). Range 0-500. |
| targetAvgWaitMinutes | number | yes | Maximum acceptable average wait, in minutes. Search returns the smallest MD count meeting this. |
| mdTreatmentMinutes | number | no | Mean MD treatment time, in minutes. Range 1-180. |
| maxMds | integer | no | Search ceiling for MD count. Range 1-20. For mixed-provider (MD + PA + NP + Locum) optimization, sign up at https://qsimhealth.com. |
| simulationDays | integer | no | Days to simulate per candidate. Range 1-7; 3 is the default for faster search. |
| treatmentDistribution | string | no | Shape of treatment-time distribution. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install QSimHealth or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish QSimHealth can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.