BetsBeats MCP server
A public, read-only Model Context Protocol server that lets AI assistants verify a BetsBeats sealed pick and read the public record.
- Endpoint:
https://api.betsbeats.com/mcp (Streamable HTTP, stateless, no auth, no API key)
- Site: https://betsbeats.com
- Registry name:
io.github.betsbeats/betsbeats
21+ only. Entertainment and analysis. No wins are promised and past results do not predict future ones. BetsBeats does not take bets. The server has no betting actions and exposes no user data.
How sealing works
Before kick-off BetsBeats publishes a SHA-256 hash of the pick (fixture, market, selection, odds, kickoff time and a secret salt). After the game settles it reveals the preimage, so anyone can hash it and compare. See seal-verify for the exact format and a standalone verifier.
Tools
Formulas: decimal = 1 + a/100 (american +a), 1 + 100/a (american -a), 1 + n/d (fractional); implied probability = 1/decimal; EV = stake * (p * (decimal - 1) - (1 - p)); parlay decimal = product of leg decimals (legs treated as independent).
Example calls
Ask an assistant: "Verify BetsBeats pick 93c087c1..." or "What is the BetsBeats record?"
Add it to a client
Claude Code
Claude Desktop / claude.ai: Settings, Connectors, Add custom connector, URL https://api.betsbeats.com/mcp.
ChatGPT: Settings, Connectors, enable Developer mode, Create, MCP server URL https://api.betsbeats.com/mcp, authentication none.
Cursor (~/.cursor/mcp.json)
Client menus change between releases; the URL is the only thing you need.
Limits
About 60 requests per minute per IP. CORS is open for this endpoint only.
License
MIT. See LICENSE.