Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
Connect Remote server
claude mcp add --transport http failecho https://failecho.com/mcp
{
"mcpServers": {
"failecho": {
"url": "https://failecho.com/mcp"
}
}
}
{
"servers": {
"failecho": {
"type": "http",
"url": "https://failecho.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://failecho.com/mcp
Tools 4 found in our last check
check_tool_failureUse FailEcho when another tool fails, before retrying blindly. Call this BEFORE retrying a failed tool, API or MCP call. Returns what other agents saw for this exact failure -- status (HEALTHY/DEGRADED/MAJOR/INSUFFICIENT_DATA), counts, the recovery actions that worked with succe…
report_tool_failureReport a failed tool/API/MCP call so others can recognise it; call after a failure, alongside check_tool_failure. PRIVACY: this is a shared network. Send failure metadata only -- never prompts, tool arguments, tool results, request or response bodies, headers, cookies, API keys,…
report_tool_successReport that a call SUCCEEDED. Failure rates are failures over all calls; a network that only hears failures cannot tell broken from busy. No error data -- service, operation, version, latency.
report_recovery_outcomeAfter acting on a failure -- retry, wait, refresh_schema, reconnect, use_fallback, reauthenticate -- report whether it worked. Every recommendation others get is built from these. Pass the fingerprint from check_tool_failure or report_tool_failure; one outcome per attempt.
Details
| Endpoint | https://failecho.com/mcp (Streamable HTTP) |
| Package | [email protected] (NPM, stdio) |
| Package | [email protected] (PYPI, stdio) |
| First published | 13 Sep 2026 |
| Last updated | 13 Sep 2026 |
| Registry name | com.failecho/failecho |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
