failecho

Name: failecho
Author: com.failecho

MCP serverMCP

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

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability622/622 checks ok

30 days agotoday

Endpoints

Registry facts

when	check	result	http	latency	detail
31 min ago	mcp initialize	ok	200	111 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
1 h ago	mcp initialize	ok	200	96 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
2 h ago	mcp initialize	ok	200	105 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
3 h ago	mcp initialize	ok	200	99 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
4 h ago	mcp initialize	ok	200	102 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
5 h ago	mcp initialize	ok	200	140 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
6 h ago	mcp initialize	ok	200	104 ms	server failecho 0.1.0 · protocol 2025-06-18 · 4 tools
8 h ago

Tools observed via MCP handshake

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
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 failu
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 -- servi
report_recovery_outcome — After acting on a failure -- retry, wait, refresh_schema, reconnect, use_fallback, reauthenticate -- report whether it worked. Every recommendation others get i

Declared by sources

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

mcpmodel-context-protocolagentsreliabilityretriesfailures

kind Official MCP Registry

name Official MCP Registry

license npm registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

No capability could be derived with confidence. Owners can declare capabilities after claiming.

Provenance

Every source is kept verbatim. Field changes are logged as events.

npm registryfailecho-mcp

first seen 17 d ago · fetched 13 h agoopen ↗

PyPIfailecho-mcp

first seen 26 d ago · fetched 7 h agoopen ↗

Official MCP Registrycom.failecho/failecho

first seen 28 d ago · fetched 20 h agoopen ↗

Field history (12 recent events)

16 d ago · observed · packageFacts → {"name":"failecho-mcp","registry":"npm","publishedAt":"2026-09-23T11:25:42.514Z","latestVersion":"0.2.3","weeklyDownload
17 d ago · observed · packageFacts → {"name":"failecho-mcp","registry":"npm","publishedAt":"2026-09-22T08:37:57.421Z","latestVersion":"0.2.2","weeklyDownload
18 d ago · observed · packageFacts → {"name":"failecho-mcp","registry":"pypi","publishedAt":"2026-09-19T18:25:12.906279Z","latestVersion":"0.2.1"}
26 d ago · claimed · ownership → {"method":"dns_txt","target":"failecho.com"}
26 d ago · declared · license → "MIT"
26 d ago · observed · packageFacts → {"name":"failecho-mcp","registry":"pypi","publishedAt":"2026-09-13T10:44:24.667402Z","latestVersion":"0.1.1"}
26 d ago · declared · version → "0.2.0"