mcpbeat

Skipodds MCP Server

com.skipodds/skipodds
answering

Skipodds is answering right now. Last checked moments ago. It exposes 5 tools.

Fair sports win probabilities - bookmaker consensus, de-vigged to sum to 100%. 13 sports, 69+ books.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
116 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add skipodds --transport http https://skipodds.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "skipodds": {
      "url": "https://skipodds.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.skipodds]
url = "https://skipodds.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "skipodds": {
      "url": "https://skipodds.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "skipodds": {
      "url": "https://skipodds.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fixture
fixture_movement
How the SkipOdds Index moved over time for one fixture — timestamped consensus snapshots. hours defaults to 24 (max 72, or 336 on the Scale tier).
get_fixture
A single fixture by id with its full de-vigged consensus: fair probability per outcome, fair odds, bookmaker count, last update.
fixtures
list_fixtures
Upcoming and recent fixtures with the de-vigged SkipOdds Index: every surveyed bookmaker price averaged and stripped of its margin, so fair win probabilities sum to exactly 100%. Covers 13 sports from 69+ bookmakers. Omit sport for soccer.
golf
golf_tournaments
Golf tournaments with normalised outright-winner probabilities. Pass key for one tournament with its full priced player field.
tournament
tournament_outrights
Soccer tournament-winner probabilities, normalised across the still-alive field (eliminated teams excluded).

Endpoints

URLTransportStateLatencyChecked
https://skipodds.com/mcp streamable-http answering 102 ms 0 min ago

Skipodds — questions

Answers built from our own checks of this server.

What can Skipodds do?
It exposes 5 tools, read directly from the server on our last check. Among them: fixture_movement, get_fixture, golf_tournaments, list_fixtures, tournament_outrights. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Skipodds working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 116 ms. The bar chart above shows every period we have measured.
How do I connect Skipodds?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Skipodds need an API key?
No. Skipodds completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Skipodds?
It answers our handshake in 116 ms on average, which is faster than 80% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.