Detects OTA reconciliation exceptions and stages recovery actions until recovered revenue is posted.
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":"leakledger-ota-recovery","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 |
|---|---|---|---|---|---|
| 35 min ago | mcp initialize | ok | 200 | 311 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 8 h ago | mcp initialize | ok | 200 | 277 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 16 h ago | mcp initialize | ok | 200 | 307 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 24 h ago | mcp initialize | ok | 200 | 269 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 33 h ago | mcp initialize | ok | 200 | 266 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 267 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 277 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 270 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 2 d ago | mcp initialize | ok | 200 | 255 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 tools |
| 3 d ago | mcp initialize | ok | 200 | 275 ms | server LeakLedger OTA Recovery 0.1.0 · protocol 2025-06-18 · 2 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.