AI support agent platform for small businesses. Query pricing, features, and examples.
Listed on its own since 2026-09-26. Until then it was part of codereclaimers-capability-oracle, where its earlier checks remain.
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":"recursive-support-oracle","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 | 343 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 10 h ago | mcp initialize | ok | 200 | 314 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 16 h ago | mcp initialize | ok | 200 | 310 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 23 h ago | mcp initialize | ok | 200 | 349 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 30 h ago | mcp initialize | ok | 200 | 348 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 2 d ago | mcp initialize | ok | 200 | 316 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 2 d ago | mcp initialize | ok | 200 | 305 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 2 d ago | mcp initialize | ok | 200 | 343 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 2 d ago | mcp initialize | ok | 200 | 304 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
| 3 d ago | mcp initialize | ok | 200 | 291 ms | server Recursive Support Oracle 1.0 · protocol 2025-11-25 |
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.