B

reliastats.com

https://reliastats.com/mcp/v1
85/100 · MCP Trust Grade · checked 4h ago · MCP 2025-06-18
Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 11 tools · Developer 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 availabili

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

explain_advanced_reliability_patterns

Return a textbook-tier explainer of advanced reliability patterns: censored data (right/left/interval — the rule not the exception), Maximum Likelihoo

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 Int

interpret_weibull_shape

Given a Weibull shape parameter β (and optionally the characteristic-life parameter η), return a plain-language interpretation: which bathtub-curve re

weibull_summary

Given Weibull two-parameter (β, η), return all the closed-form summary statistics: MTTF (η·Γ(1+1/β)), B10 / B50 / B90 life, characteristic life (just

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 L

system_reliability

Given per-component reliabilities and a structure ('series' or 'parallel'), return the system reliability. Series = product (all must work). Parallel

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

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

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 bottle

Spec conformance20%100
Security (OWASP MCP)30%100
Reliability / performance20%84
Tool hygiene15%53
Transparency / provenance15%70

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.
Grade another server

We re-grade reliastats.com on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — reliastats.com grade B
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade B · wmcp.sh
[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/reliastats.com/badge.svg)](https://wmcp.sh/mcp/grade/reliastats.com)
<a href="https://wmcp.sh/mcp/grade/reliastats.com"><img src="https://wmcp.sh/mcp/grade/reliastats.com/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.