failecho MCP server
com.failecho/failechofailecho.comstreamable-httpv0.2.0Scanned
Check what other agents hit the same tool failure — and what recovery worked. Ask before retrying.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the failecho MCP server can do
The failecho MCP server is published by failecho.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: check_tool_failure, report_tool_failure, report_tool_success and report_recovery_outcome), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 4Claude Code: ask
check_tool_failureUse FailEcho when another tool fails, before retrying blindly.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The input schema at properties.operation.description names "mcp__github__create_issue", a tool on another server "github".
What this check looks forMatched text
inputSchema.properties.operation.description: "...ver names it, e.g. 'create_issue', not 'mcp__github__create_issue'."
Description, as the server wrote it 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 `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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
report_recovery_outcomeAfter acting on a failure -- retry, wait, refresh_schema, reconnect, use_fallback, reauthenticate -- report whether it worked.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
report_tool_failureReport a failed tool/API/MCP call so others can recognise it; call after a failure, alongside check_tool_failure.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Warn
The input schema at properties.operation.description names "mcp__github__create_issue", a tool on another server "github".
What this check looks forMatched text
inputSchema.properties.operation.description: "...ver names it, e.g. 'create_issue', not 'mcp__github__create_issue'."
Description, as the server wrote it 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 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
report_tool_successReport that a call SUCCEEDED.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Warn
The input schema at properties.operation.description names "mcp__github__create_issue", a tool on another server "github".
What this check looks forMatched text
inputSchema.properties.operation.description: "...ver names it, e.g. 'create_issue', not 'mcp__github__create_issue'."
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://failecho.com/mcp: tools/list returned 4 tools to an anonymous client, including check_tool_failure (write), report_tool_failure (write), report_tool_success (write), report_recovery_outcome (write)
Findings
Matches of fixed checks, with the text they matched.
The input schema at properties.operation.description names "mcp__github__create_issue", a tool on another server "github".
What this check looks forMatched text
inputSchema.properties.operation.description: "...ver names it, e.g. 'create_issue', not 'mcp__github__create_issue'."
The input schema at properties.operation.description names "mcp__github__create_issue", a tool on another server "github".
What this check looks forMatched text
inputSchema.properties.operation.description: "...ver names it, e.g. 'create_issue', not 'mcp__github__create_issue'."
The input schema at properties.operation.description names "mcp__github__create_issue", a tool on another server "github".
What this check looks forMatched text
inputSchema.properties.operation.description: "...ver names it, e.g. 'create_issue', not 'mcp__github__create_issue'."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http failecho https://failecho.com/mcpclaude mcp add --transport http failecho https://failecho.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__failecho__check_tool_failure",
"mcp__failecho__report_tool_failure",
"mcp__failecho__report_tool_success",
"mcp__failecho__report_recovery_outcome"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as failecho. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.failecho/failecho/verify?hash=1eee885649b5896020c1089adf56b30524f9d23e2b090444c1520edc98dc8a68" | jq -e '.changed == false'Pinned hash 1eee885649b5, from Nov 10, 2026, 15:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.failecho/failecho/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.failecho/failecho)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:54 UTC.
failecho MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the failecho MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the failecho MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the failecho MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the failecho MCP server have?
- 4 tools: 4 write. check_tool_failure, report_tool_failure, report_tool_success and report_recovery_outcome.
Does the failecho MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the failecho MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the failecho MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.