ReliaStats

com.reliastats/public · v1.0.0 · developer-tools

ReliaStats is healthy: it completed an MCP handshake in 2350 ms and exposes 11 tools. It scores 58/100.

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

Endpoint: https://reliastats.com/mcp/v1 (streamable-http)

Repository · JSON · Add to my inventory

Score 58/100

health17 / 25
authEase15 / 15
toolQuality15 / 15
maintenance3 / 15
adoption0 / 10
usage0 / 10
security8 / 10

Scoring v0.3, computed 2026-10-15T08:45:15.664Z.

Health history

Checked (UTC)StatusLatencyError
2026-10-14T21:30:44.973ZHealthy2350

Tools (11)

explain_reliability_basicsReturn 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 theo
explain_distributions_for_reliabilityReturn 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 heuristic
explain_advanced_reliability_patternsReturn 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-Inte
explain_pi_vs_ci_for_validationReturn 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
interpret_weibull_shapeGiven 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),
weibull_summaryGiven 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 h
compute_availabilityGiven 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 u
system_reliabilityGiven 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 (ser
recommend_distributionGiven 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
list_paired_modelsReturn 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
describe_bottling_lineReturn 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 failu