MCP servers · cloudcorprecords

failshare: local MCP bridge to the FailEcho shared failure-knowledge server

A local MCP bridge to a hosted FailEcho server, through which agents check and report known tool failures.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

The bridge is a small local connector to FailEcho's hosted MCP server, a shared knowledge base of failures. It keeps no failure data and computes nothing itself. It serves the upstream tool list locally and forwards each tool call upstream, returning the result unchanged.

An agent would reach for it when a tool, API or MCP call fails and it wants to see what others have recorded about that exact failure before retrying. The four tools are check_tool_failure, which returns a status, counts, recovery actions with success rates and one recommendation; report_tool_failure; report_tool_success, which supplies the denominator for failure rates; and report_recovery_outcome, which records whether an action such as a retry or reconnect worked.

It runs as an MCP stdio server, a CLI in which each tool is a subcommand taking one JSON argument, or a Docker container whose default command is mcp. The upstream endpoint can be overridden with FAILECHO_MCP_URL, and FAILECHO_REPORTER_ID adds a reporter header to upstream requests when set. Upstream failures come back as error results beginning with "failshare error:". The test suite runs against a stubbed upstream and makes no live network calls.

Limitations and requirements

Requires network access to the hosted FailEcho endpoint, which defaults to failecho.com. Failure reports are shared with that network, so the publisher says to send only failure metadata, never prompts, arguments, results, headers or keys. Error text is normalised server-side. If FAILECHO_REPORTER_ID is set, its value is sent with every upstream request.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/failshare

    Shared failure knowledge for agents: check known tool failures, report failures and outcomes.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
cloudflare

Cloudflare MCP servers

Cloudflare's hosted MCP servers for its products: documentation search, sandbox containers, browser rendering, Radar internet data, logs and analytics, Workers and more.

4.5K GitHub starsCloud & DevOpsSoftware development
Updated 18 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 18 Nov 2026
MCP servers
microsoft

Playwright MCP (browser automation)

Microsoft's MCP server that lets an AI assistant open web pages, click, type and read them through a real browser, using the page structure instead of screenshots.

39.6K GitHub starsTesting & QAWeb, search & browser
Updated 18 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 18 Nov 2026
failshare: local MCP bridge to the FailEcho shared failure-knowledge server | AI Gate Discover