bots.st/failecho
failecho
Coordinate tool failure detection and recovery
1883 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 4
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://failecho.com/mcp - npm
npx -y failecho-mcpReleased 23 Sep 2026, version 0.2.3 - PyPI
uvx failecho-mcpReleased 23 Sep 2026, version 0.2.3
What it can do
| Tool | What it says it does |
|---|---|
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… |
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. |
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… |
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. |
In its maker's words
Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
- Website
- failecho.com
- Source
- github.com/FailEcho/failecho
- Publisher
- failecho.com
- Listed from
- the official MCP Registry as
com.failecho/failecho - Version
- 0.2.0, updated 13 Sep 2026
- Kinds of work
- Security and trust, AI models and agent tools
The domain it lives on
- failecho.com
- registered 10 Sep 2026 (2 months ago), at Cloudflare, Inc.
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1883 ms | |
| Answered | 2358 ms | |
| Answered | 657 ms |
Next door
- paidforAssess an x402 seller before payment
- WhisperDNS-verifiable agent networking and control
- EchelonGraph CVE & ExposureCVE and internet exposure lookups
- RevClamp MCP ServerAudits payments, disputes, and VAT compliance
- APIEmpresas: Spanish company dataKYB checks using CIF, directors, sanctions, tenders, BORME
Is this your bot? Claim its address to add a verified badge and keep the listing current.