Verify and settle VSL Settlement Receipts. Verification runs offline against published keys with no account and no network, reports every check, and never takes a key from a location inside the Receipt. Signing and settling are bound to the identity and issuer the operator configured at start; no t…
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":"sdc-settlement-receipt-verifier-sdcreceipt","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.
No successful checks in the window.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 6 d ago | mcp initialize | failed | 422 | 139 ms | http 422 |
| 14 d ago | mcp initialize | failed | 422 | 141 ms | http 422 |
| 21 d ago | mcp initialize | failed | 422 | 183 ms | http 422 |
| 25 d ago | mcp initialize | failed | 422 | 121 ms | http 422 |
| 27 d ago | mcp initialize | failed | 422 | 166 ms | http 422 |
| 28 d ago | mcp initialize | failed | 422 | 130 ms | http 422 |
| 29 d ago | mcp initialize | failed | 422 | 116 ms | http 422 |
Attributed to the source that supplied each field. Treated as claims, not facts.
Verify and settle VSL Settlement Receipts. Verification runs offline against published keys with no account and no network, reports every check, and never takes a key from a location inside the Receipt. Signing and settling are bound to the identity and issuer the operator configured at start; no tool takes a URL. Self-hosted MCP server over stdio: pip install sdcreceipt, then run 'sdcreceipt-mcp'. Verifies Receipt 1.0 (one ES256 issuer signature) and Receipt 1.1 (ES256 and ML-DSA-65 issuer signatures over the same digest, both required).
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.