MCP server list / ReliaStats
Reliability statistics — Weibull/lognormal fitting, MTBF/MTTR, availability, system composition.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 319.5 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 346 ms.
- Address
- https://reliastats.com/
mcp/ v1 - Listed in:
- official MCP registry
mcp_registry - Registry name
- com.reliastats/
public - Transport
- streamable HTTP
streamable-http - Host
reliastats.com
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- reliastats-v1
- Version:
- 1.0.0
- MCP features it lists:
- tools
- Tool names:
explain_reliability_basicsexplain_distributions_for_reliabilityexplain_advanced_reliability_patternsexplain_pi_vs_ci_for_validationinterpret_weibull_shapeweibull_summarycompute_availabilitysystem_reliabilityrecommend_distributionlist_paired_modelsdescribe_bottling_line- Instructions excerpt:
- ReliaStats is a free MCP server from ChiAha for reliability statistics theory + interpretation. Eleven tools across three families. Theory (4, doc-backed): explain_reliability_basics, explain_distributions_for_reliability, explain_advanced_reliability_patterns, explain_pi_vs_ci_for_validation. Pure-math interpretive (5, stateless deterministic): interpret_…
Reported Aug 17, 2026, 05:07 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 454 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 293 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 286 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 346 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.