FA

Failecho

com.failecho/failecho

Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.

Yes, your AI can use this right now.Answered a live MCP handshake in 162 ms with no sign-in needed and exposes 4 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://failecho.com/mcp

4 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
check_tool_failureread-only

Use 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 success rates, and one `recommendation` (or `skip` when nothing tried recently has worked; null when evidence is thin -- a rea

report_tool_failure

Report 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, tokens, emails or user content. Error text is normalized server-side and the raw string discarded. A stable reporter_id

report_tool_success

Report 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_outcome

After 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.

Alternatives in AI & Agents

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”