Choose the safest next action after an API, MCP, or agent failure before retrying.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"recover-safe-next-step-decisions-after-machine-f","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 4 h ago | mcp initialize | ok | 200 | 223 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 10 h ago | mcp initialize | ok | 200 | 167 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 16 h ago | mcp initialize | ok | 200 | 216 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 23 h ago | mcp initialize | ok | 200 | 1130 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 29 h ago | mcp initialize | ok | 200 | 210 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 179 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 176 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 201 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 199 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
| 3 d ago | mcp initialize | ok | 200 | 209 ms | server RECOVER 0.1.2 · protocol 2025-11-25 · 1 tools |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.