failecho

com.failecho/failechoVersion 0.2.0

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

Status

Responds272 msNov 14, 2026, 13:56 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:56 UTC
Latency: 272 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://failecho.com/mcpResponds272 msNov 14, 2026, 13:56 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: failecho
Remote MCP server URL: https://failecho.com/mcp

Cursor

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

VS Code

code --add-mcp '{"name":"failecho","type":"http","url":"https://failecho.com/mcp"}'

Streamable HTTP

npm: failecho-mcp 0.1.1

Package only

npm (npx)

claude mcp add failecho -- npx -y failecho-mcp@0.1.1

Streamable HTTP

pypi: failecho-mcp 0.1.1

Package only

PyPI (uvx)

claude mcp add failecho -- uvx failecho-mcp==0.1.1

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

4 tools

Tools of failecho
	Description		Read-only	Idempotent	Open world
`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 `recommendation` (or `skip` when nothing tried recently has worked; null when evidence is thin -- a real answer). Works on your own history before anyone else joins. Free, anonymous, stores nothing, never rate limited.	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 real answer). Works on your own history before anyone else joins. Free, anonymous, stores nothing, never rate limited.	No	Yes	Yes	No
`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.	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.	No	No	No	No
`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 (hashed, never stored raw) makes you one reporter instead of anonymous noise. Writes are rate limited per client.	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 (hashed, never stored raw) makes you one reporter instead of anonymous noise. Writes are rate limited per client.	No	No	No	No
`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 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.	No	No	No	No

Details

Registry status: Active
Published: Sep 13, 2026
Updated: Sep 13, 2026
Website: https://failecho.com/⁠ (opens in a new tab)
Repository: https://github.com/FailEcho/failecho⁠ (opens in a new tab)
Categories: Uncategorized
GDPR: Not declared

Are you the operator? Claim this listing