Failecho is answering right now. Last checked 10 min ago. 150 installs a week from pypi. It exposes 4 tools. Last commit 24 Sep 2026.
Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
What changed 18
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 September 2026. No other catalogue keeps this.
What the code does
We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
subprocess.run(["mkfs.ext4", "-q", "-F", "-O", "^has_journal", scratch],
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
self.dir = os.path.join(RUN_DIR, self.id)
subprocess.call(list(argv), stdout=subprocess.DEVNULL, stderr=subprocess.DEVNULL)
child = spawn(argv[0], argv.slice(1), { stdio: ["pipe", "pipe", "inherit"] });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found things in this code
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Failecho and you get told the day something new turns up.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
claude mcp add failecho --transport http https://failecho.com/mcphttps://failecho.com/mcp[mcp_servers.failecho]
url = "https://failecho.com/mcp"{
"mcpServers": {
"failecho": {
"url": "https://failecho.com/mcp"
}
}
}{
"servers": {
"failecho": {
"type": "http",
"url": "https://failecho.com/mcp"
}
}
}Available tools 4
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
report_recovery_outcome
report_tool_failure
report_tool_success
check_tool_failure
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://failecho.com/mcp | streamable-http | answering | 253 ms | 10 min ago |
Alternatives to Failecho
same job, measured the same wayCheck whether a website works for AI agents before visiting it, and the steps that worked.
Choose the safest next action after an API, MCP, or agent failure before retrying.
Shared failure knowledge for agents: check known tool failures, report failures and outcomes.
12 tools that let AI agents check trust scores and reviews before recommending any software tool.
Governs what AI agents do: tool calls, SQL, commands, files checked against policy before they run.
A .NET architecture checker that enforces one C# spec and renders the same rules for coding agents.
Check whether a real-world fact can be verified before an agent acts on it. Free, no auth.
Map how a company works, and run B2B order to cash with AI agents that ask before they act.
Failecho — questions
Answers built from our own checks of this server.