Leaderboard/ReliaSim
MCP ServerScored via MCP protocol probing: initialize handshake, tools/list conformance, and ping + tool invocation performance.

ReliaSim

Reliability and bottleneck simulation for manufacturing lines; run experiments, sweep buffers.

97/100
Operational Score
Score Breakdown
Availability30/30
Conformance30/30
Performance37/40
Key Metrics
Uptime 30d
100.0%
P95 Latency
108.5ms
Conformance
Pass
Trend
Stable
What's Being Tested
Availability
HTTP health check to the service endpoint
Responded with HTTP 200 in 105ms
Conformance
MCP initialize handshake + tools/list
Valid MCP server info returned, tools/list responded
Performance
MCP ping + zero-arg tool invocation benchmarking
P95 latency: 108ms, task completion: 100%
Skills
find_bottleneck

Single Run bottleneck analysis for the selected chapter — which node has the worst availability, per-interrupt downtime split, throughput, OEE. All eight chapters return verified dys-cli sales-prototype numbers. ANTI-FABRICATION: numbers in the response are canonical reference values from real dys-cli engine runs. Quote them VERBATIM. Do not round, estimate, or recall from training data. For follow-ups about the same chapter, re-call this tool.

get_chapter_facts

Structural facts of the selected chapter — topology, rate limits, interrupt distributions, expected efficiency. Use when the user asks about the line's configuration. ANTI-FABRICATION: rates and distributions are verified .aidos-file values. Quote VERBATIM; do not estimate or substitute training-data recall.

get_chapter_narrative

Long-form narrative for the selected chapter — what the chapter adds to the complexity ladder and the key teaching point. Use when the user asks 'walk me through this' or wants the conceptual primer. Pure prose, no numerical claims; safe to summarize.

run_gain_loss

Gain/Loss experiment — disable each interrupt one at a time, measure production recovered. Reveals the ACTUAL impact of each failure mode (Gain ≠ Loss: removing one lets others fire more often). Available on `bs1-leds`, `bs3-leds`, `bs4-ct`, `bs4-leds`. Use when the user asks 'what if we fixed X?' / 'which interrupt matters most if we actually fixed it?' / 'show me the Pareto'. ANTI-FABRICATION: per-interrupt recovered-production numbers come from real dys-cli runs. Quote VERBATIM; the Gain ≠ Loss interaction is exactly the kind of figure LLMs are prone to fabricate — don't.

run_buffer_tradeoff

Buffer Tradeoff experiment — sweep a buffer's capacity from 50 → 10,000 units, measure throughput gain. Shows the diminishing-returns elbow for buffer sizing. Only defined on `bs4-ct` and `bs4-leds`; each chapter has THREE inline buffers with different placements (pass `buffer` id to pick one). Compare CT vs LEDS on the same slot to see why interrupt-detail level changes buffer ROI math (e.g. b3: CT +23.7% vs LEDS +64.2%). Use when the user asks 'how big should the buffer be?' / 'do buffers help on this line?' / 'which buffer position gives the most gain?' / 'what's the diminishing-returns point?'. ANTI-FABRICATION (CRITICAL): the specific tradeoff numbers (e.g. CT +23.7% vs LEDS +64.2%) are sweep-derived reference values. Quote VERBATIM in your reply; do NOT recall similar percentages from training data — every buffer position has different math.

explain_concept

Definitional primer for ReliaSim's framework concepts — Constraint, Buffer, Interrupt, Converter, cascading losses, OEE, Gain/Loss methodology, Buffer Tradeoff. Returns bundled theory content, NOT interpretation of any specific simulation run. Use for 'what is X?' / 'how does X work?' / 'explain the framework' questions. For line-specific claims (throughput, availability, what-if), call the sim tools instead.

compare_chapters

Side-by-side comparison of two chapters — tracks, topology, OEE, throughput, headline bottleneck. Output is sim-derived (no interpretation drift). Use for 'how does X compare to Y?' / 'what's the difference between Constraint-Level and LEDS-Level on the same model?' / 'what changes when we add buffers?' questions. ANTI-FABRICATION: per-chapter OEE/throughput numbers are real reference values; the side-by-side delta is computed from them, not estimated. Quote VERBATIM.

run_showcase

LIVE experiment — run a bottling-line demo against the real ReliaSim engine with parameters you choose, and get its verbatim run envelope (metadata, execution stats, metrics, details). This is the only tool that COMPUTES fresh output: dial `duration_days` (or buffer capacities on the bs4 demos) and see the real numbers for that exact configuration. IMPORTANT: a run_showcase result is NOT a verified reference number — it is live output for the parameters you passed. Label it as an experiment result, not a canonical figure, and don't blend it with the curated reference numbers. For the canonical, verified OEE/throughput/bottleneck values use find_bottleneck / run_gain_loss / run_buffer_tradeoff instead. Quote any figures verbatim; do not round, average, or derive.

Tools
8 tools verified via live probe
verified 2h ago
Server: reliasimVersion: 0.1.0Protocol: 2024-11-05
Recent Probe Results
TimestampStatusLatencyConformance
Jun 10, 2026success105.9msPass
Jun 9, 2026success93msPass
Jun 5, 2026success108.5msPass
Jun 5, 2026success63.9msPass
Jun 4, 2026success86.2msPass
Jun 3, 2026success98.9msPass
May 30, 2026success55msPass
May 29, 2026success63.3msPass
May 29, 2026success88.6msPass
Source Registries
mcp-registry
First Seen
May 27, 2026
Last Seen
Jun 9, 2026
Last Probed
Jun 10, 2026