Skip to content

QueueSim MCP server

com.queuesim/publicqueuesim.comstreamable-httpv1.3.0Scanned

Queueing simulation: M/M/c, staffing, Erlang C checks, and multi-step models built from nodes.

14 tools: 10 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 10 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 7 findings

Tools listed without sign-in. Remote posture

With Anlyon

10 tools here change things. Govern them.

  • 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 QueueSim MCP server can do

The QueueSim MCP server is published by queuesim.com, a domain the MCP Registry verified. It has 14 tools. It can create or change data (10 tools: simulate_mmc, simulate_scenario, simulate_schedule, compare_separate_vs_pooled and 6 more), but cannot delete data. 4 tools only read.

1 tool reads private data (describe_scenario).

The fixed checks matched 7 findings (annotation-conflict and tool-shadowing). Each one comes with the text it matched.

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

Last scanned Nov 10, 2026, version 1.3.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.

14 tools

Changes things 10Claude Code: ask
  • check_queue_modelCheck a QueueSim Cloud model (a multi-step queueing system built from nodes and staff groups) without running it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check a QueueSim Cloud model (a multi-step queueing system built from nodes and staff groups) without running it. Returns every problem found (missing links, a line that would grow without limit, plan limits) tied to the node it is about, and a link that opens the model in QueueSim Cloud. Free plan: up to 8 nodes, 3 staff groups, 30 days, 1 run.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check a QueueSim Cloud model
  • compare_analytical_vs_simulatedRun the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas.1 finding

    Why it is in this group

    • The name "compare_analytical_vs_simulated" says "compare": a word for reading.
    • 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 "compare_analytical_vs_simulated" 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 name "compare_analytical_vs_simulated" says "compare": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Run the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas. Use this when the user is validating QueueSim's engine against textbook values, learning queueing theory by watching simulation converge on the formula, or auditing a result that 'feels off' — agreement within ~5% is the canonical sanity check for an M/M/c run. Pure-Exponential M/M/c only; the closed-form Erlang-C is undefined for other service distributions. Large deltas usually mean the simulation run was too short for steady-state — raise simulationDays. ANTI-FABRICATION: both sides come from real computation — closed-form is deterministic, simulation is stochastic but engine-backed. Quote both verbatim. Do not synthesize an 'average of the two' or recompute the formula from training-data recall.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Compare closed-form Erlang-C vs DES simulation
  • compare_separate_vs_pooledRun the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each).1 finding

    Why it is in this group

    • The name "compare_separate_vs_pooled" says "compare": a word for reading.
    • 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 "compare_separate_vs_pooled" 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 name "compare_separate_vs_pooled" says "compare": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical total arrivals (λ), so the offered load ρ is the same; the only structural difference is whether arrivals share a queue or split into c isolated streams. The pooled configuration ALWAYS produces shorter waits — that's the whole teaching point. Use this when the user asks 'should we pool our resources?' / 'should we cross-train?' / 'why do banks have one line instead of c?' / 'what's the cost of siloing my call center into specialist queues?'. Returns both runs side by side with the pooled-vs-separate wait delta. ANTI-FABRICATION: numbers come from two real DES runs. Quote them VERBATIM.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Compare pooled (M/M/c) vs separate (c × M/M/1) queueing
  • interpret_resultGiven an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the util…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Given an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the utilization curve, what ρ means in plain language, what one more or fewer server would qualitatively do, and which complexity factors (priority, abandonment, skills routing) might be hiding in real data the M/M/c model can't see. Use this to TEACH while answering — when the user wants context around a number, not just the number itself. Pure text computation, no simulation, no RNG — deterministic output.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Interpret M/M/c result
  • queue_model_guideHow to build a QueueSim Cloud model: the node types (arrivals, service, delay, split, settype, bytype, exit), staff groups, distributions, plan limits and a worked example.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How to build a QueueSim Cloud model: the node types (arrivals, service, delay, split, settype, bytype, exit), staff groups, distributions, plan limits and a worked example. Call this before check_queue_model or run_queue_model when the user's system has more than one step (several stations in a row, shared staff, routing by percent or customer type, priority customers, people who give up or are turned away). Text only, no simulation.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: QueueSim Cloud model guide
  • recommend_staffingINVERSE of simulate_mmc — given an arrival rate, service rate, and a target average wait time, returns the SMALLEST number of servers needed to meet the target.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    INVERSE of simulate_mmc — given an arrival rate, service rate, and a target average wait time, returns the SMALLEST number of servers needed to meet the target. Use this when the user asks 'how many servers do I need?' / 'what staffing keeps wait under N minutes?'. The tool runs a binary search over candidate server counts (up to maxServers, default 50), invoking the simulator for each candidate. Saves Claude from iterating simulate_mmc 3-5 times by hand. If even maxServers servers can't meet the target, the recommendation is null and the response includes the achieved wait so Claude can explain that the target is infeasible at the given load. ANTI-FABRICATION: `recommendedServers` and `achievedAvgWaitMinutes` come from real DES runs. Quote them VERBATIM. Do not propose a different number you think 'feels right'; this tool already binary-searches for the minimum that meets the target. If the user asks 'what if c=N?' for a specific N, call simulate_mmc with that c.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Recommend minimum staffing for a wait-time target
  • run_queue_modelRun a QueueSim Cloud model (a multi-step queueing system built from nodes and staff groups) on the QueueSim Cloud discrete event engine.1 finding

    Why it is in this group

    • The name "run_queue_model" says "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 "run_queue_model" 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 name "run_queue_model" says "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a QueueSim Cloud model (a multi-step queueing system built from nodes and staff groups) on the QueueSim Cloud discrete event engine. Returns, per service node: customers joined, served, gave up and turned away, mean and percentile waits in minutes and service levels; per staff group: utilization and busy staff; per exit: count and time in system. Also returns a link that opens the model in QueueSim Cloud to see it drawn and animated. Free plan: up to 8 nodes, 3 staff groups, 30 days, 1 run. Use simulate_mmc or simulate_schedule instead for a single line.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run a QueueSim Cloud model
  • simulate_mmcRun a generic M/M/c queue simulation.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_mmc" 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 generic M/M/c queue simulation. Provide an arrival rate (λ, arrivals/hour), a service rate per server (μ, customers/hour each server can finish), and a server count (c). Optional: distribution shapes, service coefficient of variation, run length. Returns per-hour metrics and an overall summary (avg wait, queue length, offered load, throughput). This is the primary tool for 'how many servers do I need?' / 'what's my average wait?' style questions. ALSO preferred over simulate_scenario for what-if questions about scheduled scenarios (Coffee Shop) when the user wants flat uniform numbers — pull the peak params from describe_scenario and run them here. That usually matches user intent better than collapsing a schedule. ANTI-FABRICATION: the returned numbers come from a real discrete-event simulation run. Quote them VERBATIM in your reply. Do not round, estimate, or compute derived figures from training-data recall. If the user asks a follow-up about the same configuration, re-call this tool rather than recalling numbers from earlier in the conversation.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run M/M/c queue simulation
  • simulate_scenarioRun one of the four preset scenarios (single, coffee, grocery, callcenter) with optional overrides.2 findings

    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 description contains "overrides, re-call this tool", wording about other tools or servers.

      Matched text

      description: "...sks a follow-up about the same scenario+overrides, re-call this tool rather than recalling numbers from earl..."

      What this check looks for
    • Warn

      The server marks "simulate_scenario" 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 one of the four preset scenarios (single, coffee, grocery, callcenter) with optional overrides. Overrides apply UNIFORMLY across open hours — e.g. setting servers=5 on 'coffee' replaces the 4/6/4 staffing pattern with a flat 5 during open hours (closed hours stay at zero). Use this for (a) faithful reproduction of a scenario's defaults, or (b) uniform scaling (everywhere it was open, use these new numbers). Do NOT use this when the user wants to keep a scheduled scenario's shape but tweak just one part — there's no per-hour override here, and collapsing a 4/6/4 pattern to 5 often isn't what the user meant. For flat what-if analysis on scheduled scenarios, prefer simulate_mmc using peak params from describe_scenario. ANTI-FABRICATION: returned numbers come from a real discrete-event simulation run. Quote them VERBATIM in your reply. Do not round, estimate, or compute derived figures from training-data recall. If the user asks a follow-up about the same scenario+overrides, re-call this tool rather than recalling numbers from earlier in the conversation.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run preset scenario
  • simulate_scheduleRun a queueing simulation against an arbitrary 24-hour staffing schedule.1 finding

    Why it is in this group

    • The name "simulate_schedule" says "schedule": 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_schedule" 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 name "simulate_schedule" says "schedule": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a queueing simulation against an arbitrary 24-hour staffing schedule. Take this when the user describes a custom day shape that doesn't match a preset (e.g., 'my coffee shop is open 6am–10pm with 4 baristas off-peak, 7 at the 8am rush, 5 at the 4pm rush'). Inputs: `arrivalRates` (24-element array of customers/hr per hour-of-day) and `staffing` (24-element array of servers/hr); optional uniform `serviceTimeMinutes`. Use 0 in both arrays for closed hours (terminating system). Returns the same per-hour metrics + summary shape as simulate_mmc / simulate_scenario. Stronger fit than simulate_scenario when the user's shape doesn't match the four presets; stronger fit than simulate_mmc when they need per-hour variation. ANTI-FABRICATION: numbers come from a real DES run. Quote them VERBATIM. Do not round, estimate, or derive from training-data recall.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Run a custom 24-hour schedule simulation
Only reads 4Show 4 read-only tools
  • describe_scenarioReturn full details for one preset scenario: title, description, teaching note, peak parameters, and per-hour arrival + staffing arrays.Reads private dataNo findings

    Why it is in this group

    • The name "describe_scenario" says "describe": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    Return full details for one preset scenario: title, description, teaching note, peak parameters, and per-hour arrival + staffing arrays. Use this before simulate_scenario to understand the default shape and what overrides make sense.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Describe preset scenario
  • explain_advanced_patternsReturn a textbook-level description of six queueing complexity patterns beyond basic M/M/c: abandonment/reneging, priority tiers, overflow routing, skills-based routing, compound s…No findings

    Why it is in this group

    • The name "explain_advanced_patterns" says "explain": a word for reading.
    Description, as the server wrote it
    Return a textbook-level description of six queueing complexity patterns beyond basic M/M/c: abandonment/reneging, priority tiers, overflow routing, skills-based routing, compound service, and server outages. Use this when the user describes real-world complexity (customers hanging up, VIP queues, specialist escalation, agent breaks, transfers) that plain M/M/c doesn't model. The tool frames each pattern conceptually and points users at ChiAha for custom modeling.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Advanced patterns primer
  • explain_queueing_theoryReturn a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C.No findings

    Why it is in this group

    • The name "explain_queueing_theory" says "explain": a word for reading.
    Description, as the server wrote it
    Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' question rather than asking for a number.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Queueing theory primer
  • list_scenariosList the four pre-built QueueSim scenarios.No findings

    Why it is in this group

    • The name "list_scenarios" says "list": a word for reading.
    Description, as the server wrote it
    List the four pre-built QueueSim scenarios. Returns key, title, and one-line description for each (Single Server, Coffee Shop, Grocery Checkout, Call Center). Call this when the user's problem matches one of the preset shapes — use describe_scenario for more detail and simulate_scenario to run one.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List preset scenarios

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 Nov 13, 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
10
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 10 tools that change things (10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://queuesim.com/mcp/v1: tools/list returned 14 tools to an anonymous client, including simulate_mmc (write), simulate_scenario (write), simulate_schedule (write), compare_separate_vs_pooled (write), recommend_staffing (write) and 5 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 7 to 10

Findings

Matches of fixed checks, with the text they matched.

7 warn
  • The server marks "simulate_mmc" 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
  • The description contains "overrides, re-call this tool", wording about other tools or servers.

    Matched text

    description: "...sks a follow-up about the same scenario+overrides, re-call this tool rather than recalling numbers from earl..."

    What this check looks for
  • The server marks "simulate_scenario" 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
  • The server marks "simulate_schedule" 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 name "simulate_schedule" says "schedule": a word for a change.

    What this check looks for
  • The server marks "compare_separate_vs_pooled" 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 name "compare_separate_vs_pooled" says "compare": a word for reading.

    What this check looks for
  • The server marks "compare_analytical_vs_simulated" 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 name "compare_analytical_vs_simulated" says "compare": a word for reading.

    What this check looks for
Show 1 more finding
  • The server marks "run_queue_model" 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 name "run_queue_model" says "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. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 10.View diff
    • Tools that change things, listed without credentials: 7 to 10
  2. Tools3 added.+3 addedView diff
  3. Tools1 changed.~1 changedView diff

Install

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

claude mcp add --transport http public https://queuesim.com/mcp/v1
claude mcp add --transport http public https://queuesim.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__list_scenarios",
      "mcp__public__describe_scenario",
      "mcp__public__explain_queueing_theory",
      "mcp__public__explain_advanced_patterns"
    ],
    "ask": [
      "mcp__public__simulate_mmc",
      "mcp__public__simulate_scenario",
      "mcp__public__simulate_schedule",
      "mcp__public__compare_separate_vs_pooled",
      "mcp__public__recommend_staffing",
      "mcp__public__interpret_result",
      "mcp__public__compare_analytical_vs_simulated",
      "mcp__public__queue_model_guide",
      "mcp__public__check_queue_model",
      "mcp__public__run_queue_model"
    ],
    "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__describe_scenario 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.queuesim/public/verify?hash=9ab9f3874748375b67139c696801fd22ff572741da1d881c7d7df9334ca6ddd6" | jq -e '.changed == false'

Pinned hash 9ab9f3874748, from Nov 10, 2026, 03:18 UTC.

Watch

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

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

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

Badge

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

Source: MCP Registry · repository. Synced Nov 10, 2026, 03:17 UTC.

QueueSim MCP server: questions and answers

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

Is the QueueSim MCP server safe?

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

Can the QueueSim MCP server delete data?

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

Can the QueueSim 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 QueueSim MCP server have?

14 tools: 10 write, 4 read. simulate_mmc, simulate_scenario, simulate_schedule, compare_separate_vs_pooled, recommend_staffing, interpret_result, compare_analytical_vs_simulated, queue_model_guide and 6 more.

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

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

Does the QueueSim MCP server send data to outside services?

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

Has the QueueSim MCP server changed its tools?

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