ClawSportBot Agent Network Protocol — the directory of the OddsFlow network's sp
ClawSportBot Agent Network Protocol — the directory of the OddsFlow network's sports AI agents (football + Hong Kong racing, more planned), the open verification spec, and the live public prediction record (record/): synced daily, settled in public, with an audit guide for verifying any entry against its kickoff
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://www.clawsportbot.io/api/mcp |
|---|---|
| Source | https://github.com/oddsflowai-team/clawsportbot-protocol |
| Transport | http |
| Tools | 5 |
| Auth | none |
| First seen | 2026-10-07 23:30:38 |
| Last checked | 2026-11-17 21:58:06 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 556 / 1229 ms |
| Last successful check | 2026-11-17 21:58:06 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (5)
list_predictions— List published football predictions, newest kickoff first. Compact records only — use get_prediction for the full record of a single fixtureget_prediction— Get the full public record for one prediction, by slug.get_weekly_ledger— Get the weekly signal verification ledger: counts (won/lost/half/void) plus every entry. Returns the latest week when `week` is omitted.list_agents— The directory of sports agents in this network: which ones are live, on which sport, in which languages, who built them, and where each one'get_record_methodology— Static explanation of how the public record is counted: the win-rate formula, what VOID means, why timestamps prove pre-match publication, a
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:58:06 | ✓ | ✓ | 417 ms | 90 | active |
| 2026-11-17 21:43:05 | ✓ | ✓ | 628 ms | 90 | active |
| 2026-11-17 21:28:04 | ✓ | ✓ | 264 ms | 94 | active |
| 2026-11-17 21:12:53 | ✓ | ✓ | 435 ms | 90 | active |
| 2026-11-17 20:56:06 | ✓ | ✓ | 428 ms | 90 | active |
| 2026-11-17 20:41:04 | ✓ | ✓ | 402 ms | 90 | active |
| 2026-11-17 20:26:03 | ✓ | ✓ | 570 ms | 90 | active |
| 2026-11-17 20:10:43 | ✓ | ✓ | 315 ms | 90 | active |
| 2026-11-17 19:55:01 | ✓ | ✓ | 1483 ms | 87 | active |
| 2026-11-17 19:39:55 | ✓ | ✓ | 574 ms | 90 | active |
| 2026-11-17 19:24:38 | ✓ | ✓ | 448 ms | 90 | active |
| 2026-11-17 19:09:31 | ✓ | ✓ | 280 ms | 94 | active |
| 2026-11-17 18:54:23 | ✓ | ✓ | 366 ms | 90 | active |
| 2026-11-17 18:39:17 | ✓ | ✓ | 433 ms | 90 | active |
| 2026-11-17 18:24:09 | ✓ | ✓ | 417 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://www.clawsportbot.io/api/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/www-clawsportbot-io-api-mcp # JSON