Is the Reliasim Public MCP server down?

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "compare_chapters",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "chapter_a",
      "chapter_b"
    ],
    "properties": {
      "chapter_a": {
        "enum": [
          "bs1-ct",
          "bs2-ct",
          "bs3-ct",
          "bs4-ct",
          "bs1-leds",
          "bs2-leds",
          "bs3-leds",
          "bs4-leds",
          "cmp-buffer-reliability",
          "cmp-shared-palletizer"
        ],
        "type": "string",
        "default": "bs1-ct",
        "description": "First chapter id (left column of the comparison). Defaults to bs1-ct."
      },
      "chapter_b": {
        "enum": [
          "bs1-ct",
          "bs2-ct",
          "bs3-ct",
          "bs4-ct",
          "bs1-leds",
          "bs2-leds",
          "bs3-leds",
          "bs4-leds",
          "cmp-buffer-reliability",
          "cmp-shared-palletizer"
        ],
        "type": "string",
        "default": "bs1-leds",
        "description": "Second 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."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "explain_concept",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "concept"
    ],
    "properties": {
      "concept": {
        "enum": [
          "constraint",
          "buffer",
          "interrupt",
          "converter",
          "cascading_losses",
          "oee",
          "gain_loss",
          "buffer_tradeoff"
        ],
        "type": "string",
        "default": "constraint",
        "description": "Which 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'."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "find_bottleneck",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "chapter": {
        "enum": [
          "bs1-ct",
          "bs2-ct",
          "bs3-ct",
          "bs4-ct",
          "bs1-leds",
          "bs2-leds",
          "bs3-leds",
          "bs4-leds",
          "cmp-buffer-reliability",
          "cmp-shared-palletizer"
        ],
        "type": "string",
        "default": "bs1-ct",
        "description": "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 machine, 5 total) and `leds` = LEDS-Level (interrupts drilled down to named failure modes, 36 total). Defaults to bs1-ct when omitted."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}