Skip to content
External endpointresponds

QueueSim

Run M/M/c queue simulations and four scenarios (call center, ER, coffee shop, single server).

Endpoint URL
https://queuesim.com/mcp/v1
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
199 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.queuesim/public

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
queuesim-v1
Version
1.0.1
Capability keys
tools
Tool names
simulate_mmc, list_scenarios, describe_scenario, simulate_scenario, simulate_schedule, compare_separate_vs_pooled, explain_queueing_theory, explain_advanced_patterns, recommend_staffing, interpret_result, compare_analytical_vs_simulated
Instructions excerpt

QueueSim is a free MCP server from ChiAha for discrete event queueing simulation. Nine tools: simulate_mmc for direct M/M/c queues, simulate_scenario for four preset shapes (single server, coffee shop, grocery checkout, call center) with optional overrides, recommend_staffing for the inverse problem (smallest c meeting a wait-time target), compare_analytical_vs_simulated to validate the DES engine against closed-form Erlang-C, interpret_result for queueing-theory-framed explanations, plus list/describe helpers and two textbook-level explainers (basic queueing theory and six complexity patterns beyond M/M/c). All tools are read-only pure compute. To compare two configurations (e.g. 'what does adding 1 server do?'), call simulate_mmc twice with the two configs and interpret the deltas — the standalone compare_scenarios tool was retired because a ~25% error rate from LLM clients passing partial nested inputs made it unreliable. ANTI-FABRICATION (IMPORTANT FOR ASSISTANT BEHAVIOR): every

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 134ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 296ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 205ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 199ms