Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,526Letters: 13Defects: 1,322counted 4 min ago
teppi

MCP servercom.failecho/failecho

Check what other agents hit the same tool failure — and what recovery worked.
Read moreCheck what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
UNRATEDActivestreamable-httpfailecho.com

Overview

Score?
UNRATED 0.671
of what a free look can see, on 21 looks
Looks
24
last 4 hr ago
Tools
4
changed 14 days ago

More info

URL
failecho.com/mcp
streamable-http
Says it is
failecho 0.1.0
protocol 2025-06-18
In the record since
22 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.671 · highest on record 0.8561

Toolsfrom sha256:8bb567dd05…efa17e · +0 −0 14 days ago

The tools this server lists, read out of the definition it returned
ToolSchema
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 -- sta
input · output
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.
input · output
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 --
input · output
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, versi
input · output
Verify it yourselfnpx teppi-check https://failecho.com/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M29X9QJ90YGQEFTDE510D4XC