ReliaSim MCP server
com.reliasim/publicreliasim.comstreamable-httpv1.0.0Scanned
Reliability and bottleneck simulation for manufacturing lines; run experiments, sweep buffers.
7 tools: 2 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ReliaSim MCP server can do
The ReliaSim MCP server is published by reliasim.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: run_gain_loss and run_buffer_tradeoff), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 2Claude Code: ask
run_buffer_tradeoffBuffer Tradeoff experiment — sweep a buffer's capacity from 50 → 10,000 units, measure throughput gain.1 finding
Why it is in this group
- The name "run_buffer_tradeoff" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_buffer_tradeoff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_buffer_tradeoff" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Show buffer size tradeoff
run_gain_lossGain/Loss experiment — disable each interrupt one at a time, measure production recovered.1 finding
Why it is in this group
- The name "run_gain_loss" says "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "run_gain_loss" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_gain_loss" says "run": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Show Gain and Loss results
Only reads 5Show 5 read-only tools
compare_chaptersSide-by-side comparison of two chapters — tracks, topology, OEE, throughput, headline bottleneck.No findings
Why it is in this group
- The name "compare_chapters" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Compare two line models
explain_conceptDefinitional primer for ReliaSim's framework concepts — Constraint, Buffer, Interrupt, Converter, cascading losses, OEE, Gain/Loss methodology, Buffer Tradeoff.No findings
Why it is in this group
- The name "explain_concept" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Explain a ReliaSim concept
find_bottleneckSingle Run bottleneck analysis for the selected chapter — which node has the worst availability, per-interrupt downtime split, throughput, OEE.No findings
Why it is in this group
- The name "find_bottleneck" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Find the bottleneck
get_chapter_factsStructural facts of the selected chapter — topology, rate limits, interrupt distributions, expected efficiency.No findings
Why it is in this group
- The name "get_chapter_facts" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get line model facts
get_chapter_narrativeLong-form narrative for the selected chapter — what the chapter adds to the complexity ladder and the key teaching point.No findings
Why it is in this group
- The name "get_chapter_narrative" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Get line model walkthrough
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://reliasim.com/mcp: tools/list returned 7 tools to an anonymous client, including run_gain_loss (write), run_buffer_tradeoff (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnrun_gain_loss
The server marks "run_gain_loss" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_gain_loss" says "run": a word for a change.
The server marks "run_buffer_tradeoff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "run_buffer_tradeoff" says "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools7 changed.~7 changedView diff
- Changed:compare_chaptersOnly readstitleannotations
- Changed:explain_conceptOnly readstitleannotations
- Changed:find_bottleneckOnly readstitledescriptionannotations
- Changed:get_chapter_factsOnly readstitledescriptionannotations
- Changed:get_chapter_narrativeOnly readstitleannotations
- Changed:run_buffer_tradeoffChanges thingstitleannotations
- Changed:run_gain_lossChanges thingstitledescriptionannotations
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http public https://reliasim.com/mcpclaude mcp add --transport http public https://reliasim.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__public__find_bottleneck",
"mcp__public__get_chapter_facts",
"mcp__public__get_chapter_narrative",
"mcp__public__explain_concept",
"mcp__public__compare_chapters"
],
"ask": [
"mcp__public__run_gain_loss",
"mcp__public__run_buffer_tradeoff"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as public. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.reliasim/public/verify?hash=2875dacb9614ef4d2a8781294f5213abf9ebe278282f0858c12e36e16a3e314f" | jq -e '.changed == false'Pinned hash 2875dacb9614, from Nov 11, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.reliasim/public/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.reliasim/public)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:01 UTC.
ReliaSim MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ReliaSim MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ReliaSim MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ReliaSim MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ReliaSim MCP server have?
- 7 tools: 2 write, 5 read. run_gain_loss, run_buffer_tradeoff, find_bottleneck, get_chapter_facts, get_chapter_narrative, explain_concept and compare_chapters.
Does the ReliaSim MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ReliaSim MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ReliaSim MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.