Is the Hanbeenmoon Agent Failure Archive MCP server down?

mcp-registry/io.github.hanbeenmoon/agent-failure-archive · v1.29.1

Also listed as github/hanbeenmoon/agent-failure-archive, glama/hanbeenmoon/agent-failure-archive

As of 2026-10-25 03:15 UTC, the Hanbeenmoon Agent Failure Archive MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 104 outages in 90 days, with a median recovery of 6 minutes.

186 real AI agent post-mortems, 107 of them measurement failures. Free tools, paid via x402.

claude mcp add --transport http hanbeenmoon-agent-failure-archive-mcp-se https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp

{
  "mcpServers": {
    "hanbeenmoon-agent-failure-archive-mcp-se": {
      "type": "http",
      "url": "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

What to fix (4)

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive/fixes

{
  "name": "archive",
  "description": "$1.00. Every case in one response. One payment, no subscription, no account.",
  "inputSchema": {
    "type": "object",
    "title": "archiveArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "search",
  "description": "$0.01. Three real agent post-mortems matching a symptom, each with root cause, the fix that worked, and the prevention rule.",
  "inputSchema": {
    "type": "object",
    "title": "searchArguments",
    "required": [
      "q"
    ],
    "properties": {
      "q": {
        "type": "string",
        "title": "Q"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.hanbeenmoon/agent-failure-archive"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.hanbeenmoon/agent-failure-archive"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~744 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.57% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• precheck ~150 tokens
• contents ~104 tokens
• audit ~99 tokens
• brief ~80 tokens
• search ~79 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive.svg)](https://glimind.com/server/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.hanbeenmoon%2Fagent-failure-archive?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:38dad4aa4b33df3c…, first seen 2026-10-17, included at leaf 9383 of 63,560. Version history · verify what your client received.

Tools (10)

• archive
• audit
• brief
• catalog
• contents
• precheck
• research
• sample
• search
• service_info

Compare: most reliable knowledge servers · most reliable other servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Hanbeenmoon Agent Failure Archive MCP server down right now?

As of 2026-10-25 03:15 UTC, the Hanbeenmoon Agent Failure Archive MCP server is up with a Glimind reliability score of 77/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 104 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Hanbeenmoon Agent Failure Archive MCP server provide?

Hanbeenmoon Agent Failure Archive MCP server advertises 10 tools, including archive, audit, brief, catalog, contents.

How do I install Hanbeenmoon Agent Failure Archive MCP server?

Point your MCP client at this streamable-http endpoint: https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp

Is the Hanbeenmoon Agent Failure Archive MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Hanbeenmoon Agent Failure Archive MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.