Skip to content
External endpointresponds

ReliaSim

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

Endpoint URL
https://reliasim.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
301 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.reliasim/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
reliasim
Version
0.1.0
Capability keys
tools
Tool names
find_bottleneck, get_chapter_facts, get_chapter_narrative, run_gain_loss, run_buffer_tradeoff, explain_concept, compare_chapters, run_showcase
Instructions excerpt

Public ReliaSim walkthrough — eight reference scenarios across two curriculum tracks (Constraint-Level and LEDS-Level). Two kinds of tool: (1) VERIFIED-REFERENCE tools (find_bottleneck, get_chapter_facts, get_chapter_narrative, run_gain_loss, run_buffer_tradeoff, compare_chapters, explain_concept) return canonical numbers transcribed from real dys-cli engine runs against authoritative .aidos models — including specific tradeoff figures like 'b3: CT +23.7% vs LEDS +64.2%'; this surface teaches the framework, it doesn't simulate your line data. (2) run_showcase (present only when the live engine is wired in) runs the real ReliaSim engine LIVE for parameters you choose and returns its verbatim run envelope — real output for that exact configuration, NOT a canonical reference number. ANTI-FABRICATION (IMPORTANT FOR ASSISTANT BEHAVIOR): quote every returned number VERBATIM; do not round, estimate, average, or compute derived figures from training-data recall. Keep the two contracts di

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

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 361ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 236ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 349ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 301ms