Skip to content
MCP server

FailEcho

By failechoAll Failecho servers

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

Listed on

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

3
Directories
1 via MCP Toplist
4
Tools
From an anonymous probe
C
ToolBench grade
Arcade’s grade, not ours
2
GitHub stars
From MCP Toplist

Tools

ToolDescriptionBehaviour
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 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.Read-only
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.Changes data
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, 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.Changes data
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.Changes data

Directory listings

DirectoryListingTierFirst seen
Official MCP Registrycom.failecho/failecho-2 Oct 2026
SmitheryFailEcho-2 Oct 2026
GlamaListed there according to MCP Toplist’s dataset; not collected by InvokeRank.