
QueueSim MCP server
Which MCP servers are QueueSim's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-21
- Registry namecom.queuesim/publicverified in the MCP registry
The registry name sits under queuesim.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-21
- Tools11
- Server calls itselfqueuesim-v1
- Server version1.0.1
- Protocol version2025-06-18
On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 130 ms.
- Its tools do every use case we checked: Test how many staff keep customer waits short; Model arrival rushes against different staffing levels.
Once connected
- For "Test how many staff keep customer waits short", the likely first call is recommend_staffing.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score98 of 100answers 100 · does the job 100 · definitions 97 · context 92 · connects 100
- What an agent can do with it2 of 2 use cases
- Answered100% of days15 of 15 daily checks
- Median first answer153 ms
- Space in an agent's context≈ 4,000 tokensthe definitions of all its tools (11), which an agent carries on every turn
- Tool definitionsA · 97 of 100
- Typed results8 of 11 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 2 of 11
What an agent can do with it
- can do · Test how many staff keep customer waits short
- not sure · Compare waits hour by hour across a shift schedule
- can do · Model arrival rushes against different staffing levels
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
simulate_mmcRun 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…
list_scenariosList 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_scenarioReturn 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.
simulate_scenarioRun 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…
simulate_scheduleRun 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…
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). Both runs have identical total capacity (c × μ) and…
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 inputs. Use this when the user asks a conceptual 'why' or 'how does this work'…
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 service, and server outages. Use this when the user…
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. Use this when the user asks 'how many servers do I need?' / 'what staffing…
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 utilization curve, what ρ means in plain language, what one…
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. Use this when the user is validating QueueSim's engine against textbook…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"public": {
"type": "http",
"url": "https://queuesim.com/mcp/v1"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http queuesim https://queuesim.com/mcp/v1claude.ai, ChatGPT and other clients: add https://queuesim.com/mcp/v1 as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.