Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.failecho/failecho

REMOTE · FAILECHO.COM · 3 COMPONENTS · SCANNED SEP 21

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

Available components

remote · failecho.com 70 npm · failecho-mcp 40 pypi · failecho-mcp 47
+4 this week 70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1151 tokens (~287/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the com.failecho/failecho MCP server?

com.failecho/failecho is a hosted endpoint at https://failecho.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · failecho.com

# add to Claude Code
claude mcp add --transport http com-failecho-failecho 'https://failecho.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-failecho-failecho": {
      "url": "https://failecho.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-failecho-failecho": {
      "type": "http",
      "url": "https://failecho.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-failecho-failecho]
url = "https://failecho.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-failecho-failecho": {
      "type": "remote",
      "url": "https://failecho.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-failecho-failecho --url 'https://failecho.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-failecho-failecho:
    url: "https://failecho.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-failecho-failecho": {
      "Transport": "http",
      "Url": "https://failecho.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-failecho-failecho -t streamable-http -u 'https://failecho.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-failecho-failecho": {
      "type": "http",
      "url": "https://failecho.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “report_recovery_outcome” rewrote its description, which is the text the model reads security
    • Tool “report_tool_failure” rewrote its description, which is the text the model reads security
    • Tool “report_tool_success” rewrote its description, which is the text the model reads security
    • Tool “check_tool_failure” rewrote its description, which is the text the model reads security
    • Schema quality: 454 → 278 ▲ functional
    • “check_tool_failure” added an optional parameter “verbose” cosmetic
    • “check_tool_failure” reworded the description of “error_code” cosmetic
    • “check_tool_failure” reworded the description of “error_message” cosmetic
    • “check_tool_failure” reworded the description of “error_type” cosmetic
    • “check_tool_failure” reworded the description of “operation” cosmetic
    • “check_tool_failure” reworded the description of “reporter_id” cosmetic
    • “check_tool_failure” reworded the description of “schema_hash” cosmetic
    • “check_tool_failure” reworded the description of “service” cosmetic
    • “check_tool_failure” reworded the description of “version” cosmetic
    • “report_recovery_outcome” reworded the description of “action” cosmetic
    • “report_recovery_outcome” reworded the description of “fingerprint” cosmetic
    • “report_tool_failure” reworded the description of “operation” cosmetic
    • “report_tool_failure” reworded the description of “service” cosmetic
    • “report_tool_success” reworded the description of “operation” cosmetic
    • “report_tool_success” reworded the description of “service” cosmetic
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +2
    • HSTS header: fail → pass ▲ security
  • 13 Sept 26 +1
    • Tool “check_tool_failure” rewrote its description, which is the text the model reads security
  • 12 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_tool_failure” rewrote its description, which is the text the model reads security
    • Schema quality: 361 → 437 ▼ functional
    • “report_tool_failure” reworded the description of “service” cosmetic
    • “report_tool_success” reworded the description of “operation” cosmetic
    • “report_tool_failure” reworded the description of “operation” cosmetic
    • “report_tool_success” reworded the description of “service” cosmetic
    • “check_tool_failure” reworded the description of “service” cosmetic
    • “check_tool_failure” reworded the description of “operation” cosmetic
  • 11 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://failecho.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=failecho.com CN=WE1,O=Google Trust Services,C=US 10 Sept 2026 9 Dec 2026 ECDSA 256 ECDSA-SHA256 d718b6bca61e6e570e4266073f18c05d
SANs: failecho.com, *.failecho.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of failecho.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
failecho.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self' https://lab.failecho.com; form-action 'self'; frame-ancestors 'none'; base-uri 'none'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://failecho.com/mcp Verified 200
http (plaintext) http://failecho.com/mcp HTTPS enforced 308 https://failecho.com/mcp
MCP tools · 4 exposed · ~978 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_tool_failure ~357

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.

NameTypeReqDescription
error_codestring–Code, e.g. '422', 'ECONNRESET'.
error_messagestring–The error text only; normalized server-side, not stored by this call.
error_typestring–Failure class, e.g. 'validation_error', 'timeout', 'rate_limit', 'auth_error'.
operationstringyesThe tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'.
reporter_idstring–Optional stable agent id; hashed, never stored raw. Lets from_other_agents be answered.
schema_hashstring–Short hash of the tool schema you used (separates 'API broke' from 'schema stale').
servicestringyesThe MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias.
verboseboolean–Full record (timestamps, rates, effective counts, every action). Default: the compact answer.
versionstring–Service/tool version, if known.

Structured output declared, but exposes no named fields.

No examples provided.

report_recovery_outcome ~141

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.

NameTypeReqDescription
actionstringyesWhat you tried, e.g. 'refresh_schema' ([a-z0-9_.-]).
fingerprintstringyesFrom check_tool_failure or report_tool_failure (32 hex chars).
reporter_idstring–Optional stable agent id; hashed, never stored raw.
successfulbooleanyesTrue when the action resolved the failure.

Structured output declared, but exposes no named fields.

No examples provided.

report_tool_failure ~304

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.

NameTypeReqDescription
error_codestring–Protocol/vendor code, e.g. '422'.
error_messagestring–Error text. Normalized before storage; no secrets please.
error_typestring–Short failure class, e.g. 'validation_error'.
latency_msinteger–Observed call latency in milliseconds.
operationstringyesThe tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'.
reporter_idstring–Optional stable identifier for your agent. Salted and hashed on arrival; never stored raw.
schema_hashstring–Short hash of the tool schema used.
servicestringyesThe MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias.
versionstring–Version of the service/tool.

Structured output declared, but exposes no named fields.

No examples provided.

report_tool_success ~176

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.

NameTypeReqDescription
latency_msinteger–Observed call latency in milliseconds.
operationstringyesThe tool or endpoint as the server names it, e.g. 'create_issue', not 'mcp__github__create_issue'.
reporter_idstring–Optional stable agent id; hashed, never stored raw.
schema_hashstring–Short hash of the tool schema used.
servicestringyesThe MCP server's own name (serverInfo.name) or the API host, e.g. 'api.github.com'. Not your client's local alias.
versionstring–Version of the service/tool.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the com.failecho/failecho MCP server?

com.failecho/failecho is an MCP server listed in the public MCP registry as com.failecho/failecho. Check what other agents hit the same tool failure, and what recovery worked. Ask before retrying. This page covers its hosted endpoint (https://failecho.com/mcp).

Is the com.failecho/failecho MCP server safe to use?

com.failecho/failecho scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.failecho/failecho MCP server expose?

com.failecho/failecho exposes 4 tools: check_tool_failure, report_tool_failure, report_tool_success, report_recovery_outcome. Their descriptions and schemas cost roughly 978 tokens of context every time the server is loaded.

Does the com.failecho/failecho MCP server require authentication?

No. We connected to com.failecho/failecho without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.failecho/failecho MCP server still maintained?

com.failecho/failecho is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.