Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

ReliaSim

REMOTE · RELIASIM.COM · SCANNED AUG 3

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

Available components

+4 this week 62 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2151 tokens (~268/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · reliasim.com

# add to Claude Code
claude mcp add --transport http com-reliasim-public https://reliasim.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-reliasim-public]
url = "https://reliasim.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-reliasim-public": {
      "type": "remote",
      "url": "https://reliasim.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-reliasim-public --url https://reliasim.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-reliasim-public:
    url: "https://reliasim.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-reliasim-public": {
      "type": "http",
      "url": "https://reliasim.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://reliasim.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reliasim.com CN=YE2,O=Let's Encrypt,C=US 27 Jul 2026 25 Oct 2026 ECDSA 256 ECDSA-SHA384 64f8ae7c7b83fc6098c3cc0ae1fb613752b
SANs: reliasim.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of reliasim.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
reliasim.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=(self)
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://reliasim.com/mcp Verified 200
http (plaintext) http://reliasim.com/mcp HTTPS enforced 301 https://reliasim.com/mcp
MCP tools — 8 exposed · ~1,850 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
compare_chapters ~190

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.

NameTypeReqDescription
chapter_astringyesFirst chapter id (left column of the comparison). Defaults to bs1-ct.
chapter_bstringyesSecond chapter id (right column of the comparison). Defaults to bs1-leds — same plant data as bs1-ct, but with interrupts drilled down to named failure modes; the canonical first-look comparison.

No output schema declared.

No examples provided.

explain_concept ~149

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.

NameTypeReqDescription
conceptstringyesWhich concept to explain. Returns a definitional primer — theory, not interpretation of a specific simulation run. Use for 'what is a Constraint?' / 'what are cascading losses?' / 'explain Gain-Loss'.

No output schema declared.

No examples provided.

find_bottleneck ~198

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.

NameTypeReqDescription
chapterstringWhich curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per mach…

No output schema declared.

No examples provided.

get_chapter_facts ~167

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.

NameTypeReqDescription
chapterstringWhich curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per mach…

No output schema declared.

No examples provided.

get_chapter_narrative ~157

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.

NameTypeReqDescription
chapterstringWhich curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per mach…

No output schema declared.

No examples provided.

run_buffer_tradeoff ~408

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.

NameTypeReqDescription
bufferstringBuffer id to sweep. The Buffer-Options Constraint-Level model has `b3` (Buffer 1, between Capper↔Labeler), `b4` (Buffer 2, between Labeler↔Case Packer), `b5` (Buffer 3, between Case Packer↔Palletizer…
chapterstringChapter id. Only `bs4-ct` and `bs4-leds` have buffer tradeoffs defined.

No output schema declared.

No examples provided.

run_gain_loss ~250

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.

NameTypeReqDescription
chapterstringWhich curriculum chapter the tool should answer about. Format: `bs<1-5>-<ct|leds>`. Both tracks run on the same real plant data — `ct` = Constraint-Level (interrupts rolled up to one Weibull per mach…

No output schema declared.

No examples provided.

run_showcase ~331

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.

NameTypeReqDescription
demo_idstringyesWhich bottling-line demo to run live. Same eight ids as the curated tools (bs1-ct … bs4-leds).
knobsobjectOptional parameters as a map of name:number. All eight demos accept `duration_days` (run length, 7–90 days). The two Buffer-Options demos also accept buffer capacities: bs4-ct → `buffer_capacity_b3`…

No output schema declared.

No examples provided.