About betsbeats
BetsBeats is a read-only MCP server for checking sealed BetsBeats picks and their public record. It also provides odds conversion and betting-math calculations, without betting actions or user data.
Key features
- 01Verify sealed picks with SHA-256
- 02Read the main pick record
- 03List settled picks by date
- 04Convert odds between formats
- 05Calculate expected value and parlay payouts
Use cases
- 01Check whether a revealed pick matches its published hash
- 02Review results for a particular date
- 03Convert odds and implied probability
- 04Estimate expected value or parlay returns
MCP support
The public server exposes read-only verification, record, results, and odds-math tools over Streamable HTTP. It requires no authentication or API key.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.betsbeats.com/mcpclaude mcp add --transport http betsbeats-betsbeats https://api.betsbeats.com/mcp{"mcpServers":{"betsbeats-betsbeats":{"type":"http","url":"https://api.betsbeats.com/mcp"}}}Open in Cursor{"servers":{"betsbeats-betsbeats":{"type":"http","url":"https://api.betsbeats.com/mcp"}}}Open in VS Code{"mcpServers":{"betsbeats-betsbeats":{"type":"http","url":"https://api.betsbeats.com/mcp"}}}{"mcpServers":{"betsbeats-betsbeats":{"serverUrl":"https://api.betsbeats.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEBetsBeats 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
| Tool | What it does |
|---|---|
verify_pick | hash (64 hex, or a unique prefix of 16+). Before settlement: confirms the hash exists, with sealed_at and kickoff_at only. After reveal: returns the preimage, recomputes SHA-256 server-side (matches), the result and a verify_url. |
get_record | Running record of the main pick: wins, losses, voids, streak, date range. |
get_results | date (YYYY-MM-DD). Settled picks that day with hashes and results. |
convert_odds | odds + format (american, decimal, fractional, probability) to all formats and implied probability. |
expected_value | odds, format, win_probability_percent, optional stake. EV, break-even probability, edge. |
parlay_payout | legs (2 to 20 of {odds, format}), optional stake. Combined odds, payout, profit. |
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
curl -s https://api.betsbeats.com/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"verify_pick","arguments":{"hash":"93c087c1418ff2cf86be7b503e04786c10811971e5bcb169659b2933483e369a"}}}'
curl -s https://api.betsbeats.com/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"convert_odds","arguments":{"odds":"+150","format":"american"}}}'
Ask an assistant: "Verify BetsBeats pick 93c087c1..." or "What is the BetsBeats record?"
Add it to a client
Claude Code
claude mcp add --transport http betsbeats https://api.betsbeats.com/mcp
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)
{ "mcpServers": { "betsbeats": { "url": "https://api.betsbeats.com/mcp" } } }
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.