ReliaStats MCP server
com.reliastats/publicreliastats.comstreamable-httpv1.2.0Scanned
Reliability math: Weibull life, availability from MTBF/MTTR, system reliability, which fit to use.
11 tools: 5 change things and 6 only read.
- Reads private data · 1
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
5 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 ReliaStats MCP server can do
The ReliaStats MCP server is published by reliastats.com, a domain the MCP Registry verified. It has 11 tools. It can create or change data (5 tools: interpret_weibull_shape, weibull_summary, compute_availability, system_reliability and 1 more), but cannot delete data. 6 tools only read.
1 tool reads private data (describe_bottling_line).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.2.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.
11 tools
Changes things 5Claude Code: ask
compute_availabilityGiven MTBF and MTTR (same time unit), return steady-state availability A = MTBF / (MTBF + MTTR).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Compute availability A = MTBF/(MTBF+MTTR)
interpret_weibull_shapeGiven a Weibull shape parameter β (and optionally the characteristic-life parameter η), return a plain-language interpretation: which bathtub-curve regime β implies (infant mortali…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Interpret a Weibull β
recommend_distributionGiven a free-text symptom description (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Recommend a starting distribution
system_reliabilityGiven per-component reliabilities and a structure ('series' or 'parallel'), return the system reliability.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: System reliability — series or parallel
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 —…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Closed-form Weibull summary
Only reads 6Show 6 read-only tools
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 + Wei…Reads private dataNo findings
Why it is in this group
- The name "describe_bottling_line" says "describe": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "doc": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Describe the bottling-line paired model
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 …No findings
Why it is in this group
- The name "explain_advanced_reliability_patterns" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Advanced reliability patterns primer
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 mor…No findings
Why it is in this group
- The name "explain_distributions_for_reliability" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Reliability distributions primer
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.No findings
Why it is in this group
- The name "explain_pi_vs_ci_for_validation" says "explain": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Validation scatter PI/CI explainer
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+MTT…No findings
Why it is in this group
- The name "explain_reliability_basics" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: Reliability fundamentals primer
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 (dist…No findings
Why it is in this group
- The name "list_paired_models" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
- title: List paired models (cross-MCP catalog)
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 untrusted-input or outbound.
- Reads private data1
- 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
- 5
- Protocol version
- 2025-06-18
- 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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://reliastats.com/mcp/v1: tools/list returned 11 tools to an anonymous client, including interpret_weibull_shape (write), weibull_summary (write), compute_availability (write), system_reliability (write), recommend_distribution (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http public https://reliastats.com/mcp/v1claude mcp add --transport http public https://reliastats.com/mcp/v1Run 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__explain_reliability_basics",
"mcp__public__explain_distributions_for_reliability",
"mcp__public__explain_advanced_reliability_patterns",
"mcp__public__explain_pi_vs_ci_for_validation",
"mcp__public__list_paired_models",
"mcp__public__describe_bottling_line"
],
"ask": [
"mcp__public__interpret_weibull_shape",
"mcp__public__weibull_summary",
"mcp__public__compute_availability",
"mcp__public__system_reliability",
"mcp__public__recommend_distribution"
],
"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.
Capability tags behind 1 rule
- mcp__public__describe_bottling_line private-data
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.reliastats/public/verify?hash=f8b0cb89a2293a25e3d5de0b8fc0553de43b438af75de7707be1b3458fa5e8b3" | jq -e '.changed == false'Pinned hash f8b0cb89a229, from Nov 10, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.reliastats/public/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.reliastats/public)Source: MCP Registry · repository. Synced Nov 10, 2026, 03:17 UTC.
ReliaStats MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ReliaStats MCP server safe?
- No scan can promise that. What its definitions show: 11 tools, 5 of which can change, send or delete something, and 0 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 ReliaStats MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ReliaStats 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 ReliaStats MCP server have?
- 11 tools: 5 write, 6 read. interpret_weibull_shape, weibull_summary, compute_availability, system_reliability, recommend_distribution, explain_reliability_basics, explain_distributions_for_reliability, explain_advanced_reliability_patterns and 3 more.
Does the ReliaStats MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ReliaStats MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ReliaStats MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.