Bet Better Data MCP server
online · 100% uptimeby edushinka·
io.github.edushinka/betbetter-mcp·v1.1.0Predicted scores, win chances and checked sport stats for 29 competitions. Free and licensed tools.
C65/100grade C
Safety scan
C65/100
not scanned yet
Adoption
New
26 downloads/wk
Reviews
Write oneNobody has reviewed Bet Better Data yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Bet Better Data tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Bet Better Data compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 118 ms
- faster than 80% of 30,031 servers
- Downloads a week
- 26
- more than 13% of 12,191 servers with a package
Release history: 2 versions in the registry since 2026-07-26, latest 2026-10-23, typically one every 89 days.
Install Bet Better Data in Claude Code, Cursor or VS Code
claude mcp add --transport http betbetter-mcp https://betbetter.world/mcp
Bet Better Data: common questions
- Is Bet Better Data MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Bet Better Data safety report
- How do I install Bet Better Data?
- It runs remotely at betbetter.world. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Bet Better Data need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Bet Better Data maintained?
- The latest release is v1.1.0.
- Is Bet Better Data up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Bet Better Data compare with other MCP servers?
- safety score 65/100 (higher than 20% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 118 ms (faster than 80% of 30,031 servers). Full comparison.