Now part of GAIP Witness: tests supplier claims and compares them with published metadata.
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":"gaip-procurement-evidence-agent","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 |
|---|---|---|---|---|---|
| 7 h ago | mcp initialize | ok | 200 | 2859 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 13 h ago | mcp initialize | ok | 200 | 3040 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 19 h ago | mcp initialize | ok | 200 | 2762 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 26 h ago | mcp initialize | ok | 200 | 2841 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 33 h ago | mcp initialize | ok | 200 | 2621 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 1865 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 2695 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 3330 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 1823 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 1 tools |
| 3 d ago | mcp initialize | ok | 200 | 2393 ms | server gaip-procurement-verify 1.4.0 · protocol 2025-06-18 · 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.