Skip to content

QSimHealth MCP server

com.qsimhealth/publicqsimhealth.comstreamable-httpv1.0.0Scanned

Healthcare staffing simulator — ED, walk-in clinic, and appointment office DES tools.

7 tools: 1 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 1 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the QSimHealth MCP server can do

The QSimHealth MCP server is published by qsimhealth.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (1 tool: simulate_ed_demo), but cannot delete data. 6 tools only read.

1 tool reads private data (recommend_md_count).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 1Claude Code: ask
  • simulate_ed_demoRun a 7-day MD-only demo simulation of an ED, urgent care, walk-in clinic, or appointment-office staffing scenario.1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "simulate_ed_demo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Simulate ED staffing (demo)
Only reads 6Show 6 read-only tools
  • describe_facilityReturn 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 faci…No findings

    Why it is in this group

    • The name "describe_facility" says "describe": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Describe a facility archetype
  • explain_appointment_officeExplain 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 visi…No findings

    Why it is in this group

    • The name "explain_appointment_office" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Explain appointment office dynamics
  • explain_ed_queueingReturn 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 rea…No findings

    Why it is in this group

    • The name "explain_ed_queueing" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Explain ED queueing dynamics
  • explain_walk_in_clinicExplain 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.No findings

    Why it is in this group

    • The name "explain_walk_in_clinic" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Explain walk-in clinic dynamics
  • list_facility_typesList the four healthcare facility archetypes QSimHealth speaks to: ED, urgent care, walk-in clinic, appointment office.No findings

    Why it is in this group

    • The name "list_facility_types" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List facility archetypes
  • recommend_md_countINVERSE of simulate_ed_demo — given an arrival rate and a target average wait, returns the smallest MD count meeting the target.Reads private dataNo findings

    Why it is in this group

    • The name "recommend_md_count" says "count": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "meeting": it reads calendars.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Recommend minimum MD count for wait target

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://qsimhealth.com/mcp/v1: tools/list returned 7 tools to an anonymous client, including simulate_ed_demo (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "simulate_ed_demo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http public https://qsimhealth.com/mcp/v1
claude mcp add --transport http public https://qsimhealth.com/mcp/v1

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__public__explain_ed_queueing",
      "mcp__public__explain_walk_in_clinic",
      "mcp__public__explain_appointment_office",
      "mcp__public__list_facility_types",
      "mcp__public__describe_facility",
      "mcp__public__recommend_md_count"
    ],
    "ask": [
      "mcp__public__simulate_ed_demo"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as public. Review it before you use it.

Capability tags behind 1 rule
  • mcp__public__recommend_md_count private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.qsimhealth/public/verify?hash=b15ab5e44bb3aeb6eaa7eb6d21034d30342ec7822b8620b5d3995d88fa456b28" | jq -e '.changed == false'

Pinned hash b15ab5e44bb3, from Nov 11, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.qsimhealth/public/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.qsimhealth/public
[![Anlyon Radar](https://radar.anlyon.com/badge/com.qsimhealth/public.svg)](https://radar.anlyon.com/servers/com.qsimhealth/public)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:01 UTC.

QSimHealth MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the QSimHealth MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the QSimHealth MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the QSimHealth MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the QSimHealth MCP server have?

7 tools: 1 write, 6 read. simulate_ed_demo, explain_ed_queueing, explain_walk_in_clinic, explain_appointment_office, list_facility_types, describe_facility and recommend_md_count.

Does the QSimHealth MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the QSimHealth MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the QSimHealth MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.