mcp-failure-lab
A chaos-engineering and resilience-testing toolkit for Model Context Protocol servers.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 4 | github.com/anilloutombam/mcp-failure-lab |
| Last push | 2026-11-21 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 0.9.0 · active · updated 2026-09-15 | registry |
| Package | npm: mcp-failure-lab | registry |
Packages
npm: mcp-failure-lab
Exists · metadata read 2026-11-21
Latest version: 0.13.2. Last published: 2026-10-31.
Deprecated: no.
Weekly downloads: 89 · read 2026-11-21. downloads include bots and CI.
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
npx -y mcp-failure-labCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Quiet Failures Open weekly security base rates (CC BY 4.0), plus live DMARC, takeover and WHOIS checks.
- Span-level replay: fork from the failure Fork-replay one recorded span from a failed agent run and get an attribution verdict.
- LiquiLens Failure Radar Free bank-filing and counterparty research; cited evidence limits; public MCP needs no API…
- Agent Repair — MCP Tool Failure Diagnostics Free MCP tool error diagnosis, argument checks, and related agent-tool discovery.
- Predictive maintenance failure risk assessment — Atom Predictive maintenance failure risk assessment, delivered per API call on Conduit Atoms.
- Error-actionability translation for MCP tool failures Classifies MCP tool failures into enforced recovery verdicts from per-server dialect…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/io.github.anilloutombam/mcp-failure-lab)<a href="https://openforallofus.com/tools/io.github.anilloutombam/mcp-failure-lab"><img src="https://openforallofus.com/badge/io.github.anilloutombam/mcp-failure-lab.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.anilloutombam/mcp-failure-lab.