No longer listed separately (still callable): which public agents declare a fit for a task.
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-opportunity-broker","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 |
|---|---|---|---|---|---|
| 57 min ago | mcp initialize | ok | 200 | 2331 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 7 h ago | mcp initialize | ok | 200 | 2831 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 14 h ago | mcp initialize | ok | 200 | 2713 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 20 h ago | mcp initialize | ok | 200 | 1819 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 26 h ago | mcp initialize | ok | 200 | 4680 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 32 h ago | mcp initialize | ok | 200 | 1917 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 2489 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 2105 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 2009 ms | server gaip-opportunity-broker 1.4.0 · protocol 2025-06-18 · 1 tools |
| 2 d ago | mcp initialize | ok | 200 | 1848 ms | server gaip-opportunity-broker 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.