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

ReliaSim

REMOTE · RELIASIM.COM

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

Available components

0 this week 82 Trust /100

Last scanned (16 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Testing and QA

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2506 tokens (~358/item across 7 items; 7 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +6
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_bottleneck” rewrote its description, which is the text the model reads security
    • Tool “get_chapter_facts” rewrote its description, which is the text the model reads security
    • Tool “run_gain_loss” rewrote its description, which is the text the model reads security
    • Schema quality: 247 → 351 ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • Tool “compare_chapters” changed its title: Compare two line models cosmetic
    • Tool “explain_concept” changed its title: Explain a ReliaSim concept cosmetic
    • Tool “find_bottleneck” changed its title: Find the bottleneck cosmetic
    • Tool “get_chapter_facts” changed its title: Get line model facts cosmetic
    • Tool “get_chapter_narrative” changed its title: Get line model walkthrough cosmetic
    • Tool “run_buffer_tradeoff” changed its title: Show buffer size tradeoff cosmetic
    • Tool “run_gain_loss” changed its title: Show Gain and Loss results cosmetic
  • 22 Oct 26 0
    • Stability: fail → pass ▲ security
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 21 Nov 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 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 6a14fad4efac154bdddbac566c8a004c9dd
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of reliasim.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
reliasim.com. No DS 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)

Background: How OAuth 2.1 works in the 2026 MCP spec →

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 · 7 exposed · ~1,518 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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 ~195

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 saved results. ANTI-FABRICATION: numbers in the response are canonical reference values from real ReliaSim 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
chapterstring–Which 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 values from the model file. Quote VERBATIM; do not estimate or substitute training-data recall.

NameTypeReqDescription
chapterstring–Which 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
chapterstring–Which 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
bufferstring–Buffer 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…
chapterstring–Chapter id. Only `bs4-ct` and `bs4-leds` have buffer tradeoffs defined.

No output schema declared.

No examples provided.

run_gain_loss ~252

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 ReliaSim engine runs. Quote VERBATIM; the Gain ≠ Loss interaction is exactly the kind of figure LLMs are prone to fabricate — don't.

NameTypeReqDescription
chapterstring–Which 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.

Install

How do I install the ReliaSim MCP server?

ReliaSim is a hosted endpoint at https://reliasim.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · reliasim.com

# add to Claude Code
claude mcp add --transport http com-reliasim-public 'https://reliasim.com/mcp'
Common questions

What is the ReliaSim MCP server?

ReliaSim is an MCP server listed in the public MCP registry as com.reliasim/public. Reliability and bottleneck simulation for manufacturing lines; run experiments, sweep buffers. This page covers its hosted endpoint (https://reliasim.com/mcp).

Is the ReliaSim MCP server safe to use?

ReliaSim scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ReliaSim MCP server expose?

ReliaSim exposes 7 tools: find_bottleneck, get_chapter_facts, get_chapter_narrative, run_gain_loss, run_buffer_tradeoff, and 2 more. Their descriptions and schemas cost roughly 1,518 tokens of context every time the server is loaded.

Does the ReliaSim MCP server require authentication?

No. We connected to ReliaSim without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ReliaSim MCP server still maintained?

ReliaSim is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ReliaSim MCP server?

VerifyMCP ran 13 checks on ReliaSim, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.