BetsBeats MCP server: frequently asked questions

The BetsBeats MCP server is a free, read-only endpoint at https://api.betsbeats.com/mcp with six tools, no key and a limit of 60 requests a minute per IP address. It checks sealed picks, reads the public record and does odds arithmetic. It cannot place bets. For adults 21+, for analysis and entertainment.

Examples are real responses from the live server, captured on 1 November 2026.

What is the BetsBeats MCP server?

It is a Model Context Protocol server that lets an AI assistant call six tools: verify_pick, get_record, get_results, convert_odds, expected_value and parlay_payout. Three read the public BetsBeats record and three do odds arithmetic.

Does it cost anything or need an API key?

No. The endpoint https://api.betsbeats.com/mcp is public. There is no account, key or sign-in.

Can it place bets or move money?

No. It is read-only. BetsBeats does not take bets, and the tools cannot touch any account.

Can it tell me today's pick?

Not before it settles. Until then the server shows only the hash, when it was sealed and the kickoff time. The selection is revealed afterwards. Today's free pick is at /free.

What is the rate limit?

About 60 requests per minute per IP address. The server reports the limit and what remains in X-RateLimit headers.

Which AI clients work with it?

Any MCP client that supports Streamable HTTP. This site has setup pages for Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code with GitHub Copilot and Windsurf.

What does a match from verify_pick prove?

That the revealed text hashes to the value published before kickoff, so it was not edited afterwards. It does not prove the pick was good or that every pick was published, so read the full record too.

Where is the source code and what is the license?

The server README is at github.com/betsbeats/betsbeats-mcp and the standalone verifier at github.com/betsbeats/seal-verify. The server repository is MIT licensed.