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.

ReliaStats

REMOTE · RELIASTATS.COM · SCANNED AUG 3

Reliability statistics — Weibull/lognormal fitting, MTBF/MTTR, availability, system composition.

Available components

+5 this week 72 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 Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2208 tokens (~200/item across 11 items; 11 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; 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 · reliastats.com

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

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.

  • 3 Aug 26 +1

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

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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

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

  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 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 66

    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://reliastats.com/mcp/v1

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reliastats.com CN=YE2,O=Let's Encrypt,C=US 26 Jul 2026 24 Oct 2026 ECDSA 256 ECDSA-SHA384 5cd3d2270e6fb2d5c2bd9728f70195230f4
SANs: reliastats.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 reliastats.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
reliastats.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=()
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://reliastats.com/mcp/v1 Verified 200
http (plaintext) http://reliastats.com/mcp/v1 HTTPS enforced 301 https://reliastats.com/mcp/v1
MCP tools — 11 exposed · ~1,948 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
compute_availability ~154

Given MTBF and MTTR (same time unit), return steady-state availability A = MTBF / (MTBF + MTTR). One-line closed-form, but worth a dedicated tool so LLMs don't fumble the identity (the most common mistake is conflating MTBF with MTTF and silently inflating availability by the MTTR). Use whenever a user supplies an MTBF/MTTR pair and asks for availability. ANTI-FABRICATION: exact closed-form. Quote verbatim.

NameTypeReqDescription
mtbfnumberyesMean Time Between Failures (repairable system). Same time unit as MTTR.
mttrnumberyesMean Time To Repair. Same time unit as MTBF.

No output schema declared.

No examples provided.

describe_bottling_line ~275

Return the full worked-example doc for the bottling-line paired model — topology (5 machines: Filler/Capper/Labeler/Case Packer/Palletizer, 100 bottles/min, Weibull(30,1) TTF + Weibull(5,1) downtime at the Constraint-Level rollup), the two tracks (CT rollup vs LEDS-Level drill-down to 36 named failure modes), the 4 build sequences (BS1 → BS4), the file-shape mapping between ReliaSim outputs and ReliaStats modes, and a worked cross-MCP tool chain. Optional 'section' parameter narrows to one H2 section. ANTI-FABRICATION: content is sourced from docs/paired-model-bottling-line.md; every claim references the .aidos files or ChapterRegistry.fs in reliasim-site.

NameTypeReqDescription
sectionstringOptional H2 section name from docs/paired-model-bottling-line.md to narrow the response. Examples: 'Topology — the line itself', 'The two tracks — Constraint-Level vs LEDS-Level', 'The four build seq…

No output schema declared.

No examples provided.

explain_advanced_reliability_patterns ~126

Return a textbook-tier explainer of advanced reliability patterns: censored data (right/left/interval — the rule not the exception), Maximum Likelihood Estimation, Goodness-of-Fit tests (Anderson-Darling favored over KS for tail-sensitive reliability work), the Confidence-Interval vs Prediction-Interval distinction that backs the Interrupt Validation scatter, accelerated life testing (Arrhenius / inverse power law / Coffin-Manson), and Bayesian reliability. No inputs. ANTI-FABRICATION: text is sourced from docs/reliability-theory.md.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain_distributions_for_reliability ~161

Return a textbook-tier distribution zoology for reliability work: why Weibull is the default, the shape-parameter β table mapping β-ranges to physical failure modes (β<1 infant mortality, β=1 random, β>1 wearout), when to reach for Exponential / Lognormal / Normal / Gamma, and practitioner heuristics for picking a distribution. No inputs. Use when a user asks 'which distribution should I fit' / 'what does Weibull β mean' / 'when to use Lognormal'. ANTI-FABRICATION: text is sourced from docs/reliability-theory.md. The β-as-failure-mode interpretation is ChiAha's practitioner framing — quote verbatim; do not paraphrase.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain_pi_vs_ci_for_validation ~132

Return the specific explainer for the ReliaStats Interrupt Validation scatter chart's red y=x / blue 95% Prediction Interval / teal 99% Confidence Interval reference lines. Use when a user asks 'what do the bands mean' / 'why is my point outside the blue line' / 'how do I read the validation scatter'. The bands are FIXED plotting conventions — they are NOT recomputed from the loaded data; this is anti-fab by design. Text sourced from docs/reliability-theory.md (the 'Confidence intervals vs prediction intervals' sub-section of Advanced Reliability Patterns).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain_reliability_basics ~152

Return a textbook-tier explainer of reliability fundamentals: the four reliability functions R(t)/F(t)/f(t)/h(t), MTBF vs MTTF vs MTTR, the availability identity A = MTBF/(MTBF+MTTR), the bathtub curve, and series/parallel system reliability. No inputs. Use when a user asks 'what is reliability theory' / 'explain MTBF' / 'how does availability work' / 'what's a hazard rate'. ANTI-FABRICATION: text is sourced from docs/reliability-theory.md (the canonical ChiAha reliability primer). Quote sections verbatim; do not paraphrase reliability theory from training-data recall.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

interpret_weibull_shape ~243

Given a Weibull shape parameter β (and optionally the characteristic-life parameter η), return a plain-language interpretation: which bathtub-curve regime β implies (infant mortality / random / wearout), what action that suggests (process-of-care / steady-state monitoring / maintenance scheduling), and — if η provided — closed-form MTTF and B-life numbers from the Weibull formulas. Pure-math + lookup, no engine call, fully deterministic. Use when a user reports a fitted β and wants to know what to DO with it. ANTI-FABRICATION: MTTF and B-life are exact closed-form values from the two-parameter Weibull (η · Γ(1+1/β) and η · (-ln(1-p))^(1/β)). Quote them verbatim.

NameTypeReqDescription
betanumberyesWeibull shape parameter β (dimensionless). Typical reliability range 0.3 – 8.0.
etanumberOptional Weibull characteristic-life parameter η, in the same time units you care about (e.g. hours). When provided, the response includes MTTF + B-life numbers.

No output schema declared.

No examples provided.

list_paired_models ~157

Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recommend_distribution ~178

Given a free-text symptom description (e.g. 'manufacturing burn-in', 'bearing wearout under variable load', 'cosmic-ray bit flips'), return an ordered shortlist of distribution candidates with a one-line rationale per recommendation. Keyword-matched against a curated dictionary; ALWAYS treat output as a starting point for fitting work, not a fit. The actual fitting happens in the ReliaStats sandbox (protected/app.html). ANTI-FABRICATION: rationales are written ChiAha content; the algorithm is a deterministic substring match. Quote verbatim.

NameTypeReqDescription
symptomsstringyesFree-text description of the failure data or context — e.g. 'manufacturing burn-in', 'bearing wearout', 'cosmic-ray bit flips', 'multi-stage degradation'. Substring-matched against a keyword dictiona…

No output schema declared.

No examples provided.

system_reliability ~162

Given per-component reliabilities and a structure ('series' or 'parallel'), return the system reliability. Series = product (all must work). Parallel = 1 − product(1−Rᵢ) (at least one works). Useful for back-of-envelope RBD calcs before reaching for full RBD tooling. For mixed-structure systems (series with parallel sub-blocks), call this tool repeatedly on the sub-blocks. ANTI-FABRICATION: exact closed-form. Quote verbatim.

NameTypeReqDescription
componentsarrayyesPer-component reliabilities in [0, 1]. Order doesn't matter.
structurestringyesRBD structure: 'series' (all must work) or 'parallel' (at least one works).

No output schema declared.

No examples provided.

weibull_summary ~208

Given Weibull two-parameter (β, η), return all the closed-form summary statistics: MTTF (η·Γ(1+1/β)), B10 / B50 / B90 life, characteristic life (just η, surfaced explicitly), and — if evaluateAtT supplied — R(t), F(t), and hazard h(t) at that time. Pure-math, fully deterministic. Use when the user has a fit and wants the numbers downstream tools normally compute (don't recompute these from training-data recall — call this tool). ANTI-FABRICATION: every number is an exact closed-form value. Quote verbatim.

NameTypeReqDescription
betanumberyesWeibull shape parameter β (dimensionless).
etanumberyesWeibull characteristic life η, in your chosen time unit.
evaluateAtTnumberOptional time t (same unit as η) at which to also return reliability R(t), failure F(t), and hazard h(t).

No output schema declared.

No examples provided.