Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
Facts
- MCP registry
com.failecho/failecho· 0.2.0- Endpoint
https://failecho.com/mcp- Packages
npmfailecho-mcp stdiopypifailecho-mcp stdio- Website
- failecho.com
- npm / week
- 392
- GitHub stars
- 2
- Registry entry
- updated 13 Sep 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under failecho.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 4 · about 1,657 tokens of context · checked 23 hours ago
| Tool | What it does | Hint |
|---|---|---|
check_tool_failureCheck what the network knows about a 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… | read-only |
report_tool_failureReport a failed tool call to the network | 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… | writes |
report_tool_successReport a successful tool call to the network | 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. | writes |
report_recovery_outcomeReport whether a recovery action worked | 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… | writes |
What https://failecho.com/mcp answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 0 warnings · 0 notes
Nothing to flag: every tool reads cleanly to an agent.
The checks from /check and anchor check, run each day on the list above: about 1,657 tokens of definitions. Not part of the score yet. Check your own server.