All servers · Email & messaging

com.failecho/failecho

com.failecho/failecho · v0.2.0

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http failecho https://failecho.com/mcp

{
  "mcpServers": {
    "failecho": {
      "url": "https://failecho.com/mcp"
    }
  }
}

Tools as reported by the server

• check_tool_failure
  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 `re
• 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 us
• 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.

Repository · Website · JSON · Text for agents · Registry updated 2026-09-13