ReliaStats
by reliastats.com in Other
Reliability statistics — Weibull/lognormal fitting, MTBF/MTTR, availability, system composition.
https://reliastats.com/mcp/v1
Last 30 days
- Uptime
- 100%
- Response time
- 294 ms typical, 328 ms slowest 5%
- Last check
- 1 h ago
- Next check
- in 5 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"reliastats": {
"type": "http",
"url": "https://reliastats.com/mcp/v1"
}
}
}11 tools
- explain_reliability_basics
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
- explain_distributions_for_reliability
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 pr
- explain_advanced_reliability_patterns
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-Interva
- explain_pi_vs_ci_for_validation
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 th
- interpret_weibull_shape
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 / maint
- weibull_summary
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.
- compute_availability
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 MTT
- system_reliability
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-st
- recommend_distribution
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;
- list_paired_models
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. Ret
- describe_bottling_line
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-do
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 1 h ago | Passed | 200 | 294 ms |
| 10 h ago | Passed | 200 | 265 ms |
| 19 h ago | Passed | 200 | 328 ms |
| 28 h ago | Passed | 200 | 3.9 s |