Agent Failure Archive
REMOTE · DESKTOP-AI2ATA5-1.TAILFEB765.TS.NET · SCANNED SEP 14
186 real AI agent post-mortems, 107 of them measurement failures. Free tools, paid via x402.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Agent Failure Archive MCP server?
Agent Failure Archive is a hosted endpoint at https://desktop-ai2ata5-1.tailfeb765.ts.net/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 · desktop-ai2ata5-1.tailfeb765.ts.net
claude mcp add --transport http hanbeenmoon-agent-failure-archive 'https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp'
{
"mcpServers": {
"hanbeenmoon-agent-failure-archive": {
"url": "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp"
}
}
} {
"servers": {
"hanbeenmoon-agent-failure-archive": {
"type": "http",
"url": "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp"
}
}
} [mcp_servers.hanbeenmoon-agent-failure-archive] url = "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"hanbeenmoon-agent-failure-archive": {
"type": "remote",
"url": "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp",
"enabled": true
}
}
} openclaw mcp add hanbeenmoon-agent-failure-archive --url 'https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp' --transport streamable-http
mcp_servers:
hanbeenmoon-agent-failure-archive:
url: "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp" {
"McpServers": {
"hanbeenmoon-agent-failure-archive": {
"Transport": "http",
"Url": "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp"
}
}
} assistant mcp add hanbeenmoon-agent-failure-archive -t streamable-http -u 'https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp'
{
"mcpServers": {
"hanbeenmoon-agent-failure-archive": {
"type": "http",
"url": "https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Sept 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 9 Sept 26 0
- DNSSEC: fail → unverified ▼ security
- 8 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.43 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 14 Sept 2026 · Probed https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of desktop-ai2ata5-1.tailfeb765.ts.net. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| desktop-ai2ata5-1.tailfeb765.ts.net. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp | Unreachable | ||
| http (plaintext) | http://desktop-ai2ata5-1.tailfeb765.ts.net/mcp | HTTPS enforced |
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 →
archive ~27
$1.00. Every case in one response. One payment, no subscription, no account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
audit ~52
$0.02. Full audit of a claim: why each tripped check matters, the incident behind it with measured numbers, and what to run.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| evidence | string | – | – |
No output schema declared.
No examples provided.
brief ~39
$0.05. Pre-flight risk brief before an irreversible action, drawn from the ways that class of action actually failed.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
No output schema declared.
No examples provided.
catalog ~28
Free, no wallet. What the archive holds, what each paid tool costs, and how payment works.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
contents ~57
Free, no wallet. Every case title in the archive, tagged with the trap it illustrates. Titles only, no bodies. Read this to see what the paid archive actually contains before deciding it is worth a dollar.
| Name | Type | Req | Description |
|---|---|---|---|
| theme | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
precheck ~86
Free, no wallet. Check a conclusion against nine known ways of fooling yourself and get back which checks it trips plus the question each one asks. Use it before writing 'we found that'. The paid audit tool adds why each matters, the real incident with the numbers measured at the time, and what to run.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| evidence | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
research ~38
$0.25. The 107 measurement failures from an eight-month attempt to measure one person's individuation with embeddings.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | – |
No output schema declared.
No examples provided.
sample ~22
Free, no wallet. Two complete post-mortems from the archive.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search ~45
$0.01. Three real agent post-mortems matching a symptom, each with root cause, the fix that worked, and the prevention rule.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | – |
No output schema declared.
No examples provided.
What is the Agent Failure Archive MCP server?
Agent Failure Archive is an MCP server listed in the public MCP registry as io.github.HanbeenMoon/agent-failure-archive. 186 real AI agent post-mortems, 107 of them measurement failures. Free tools, paid via x402. This page covers its hosted endpoint (https://desktop-ai2ata5-1.tailfeb765.ts.net/mcp).
Is the Agent Failure Archive MCP server safe to use?
Agent Failure Archive scores 0 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 Agent Failure Archive MCP server expose?
Agent Failure Archive exposes 9 tools: precheck, sample, catalog, contents, audit, and 4 more. Their descriptions and schemas cost roughly 394 tokens of context every time the server is loaded.
Does the Agent Failure Archive MCP server require authentication?
Its publisher declares no required credentials for Agent Failure Archive. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Agent Failure Archive MCP server still maintained?
Agent Failure Archive has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 7 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.