Oddsradarwire — Live & Prematch Betradar Odds with No-Vig Probabilities
Live and prematch Betradar odds with no-vig fair prices.
What it can do
What data it sees
Do you need an account
An API key from the service settings is required
Live and prematch Betradar odds with no-vig fair prices. Free demo access, no key.
How to connect
How to connect Oddsradarwire — Live & Prematch Betradar Odds with No-Vig Probabilities to Claude
The server address to paste into Claude settings:
https://oddsradarwire.com/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Oddsradarwire — Live & Prematch Betradar Odds with No-Vig Probabilities to ChatGPT
The server address to paste into ChatGPT settings:
https://oddsradarwire.com/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Oddsradarwire — Live & Prematch Betradar Odds with No-Vig Probabilities to Cursor
The server address to paste into Cursor settings:
https://oddsradarwire.com/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (7)
Raw names from tools/list. Only developers need these.
| get_live_odds | Current live (in-play) odds for this product's board: every fixture with its OPEN markets, decimal prices and the no-vig probability on each selection. Use it for live odds displays, arbitrage or middles checks against another book, in-play models and feature engineering, no-vig fair value, and agent workflows that need current prices. Each selection's probability is the provider's own no-vig number passed through unmodified, sitting beside the priced odds at up to ~8.4% overround. Only a market whose structure is 'exclusive' partitions the outcome space, so never sum a 'ladder', 'union' or 'partial' market. Not a multi-book scanner — one provider, so there is no comparison, best-price or line-shopping output here. Not a historical archive — prices are current only and nothing is stored for backtests. Not a bet-placement tool. A live match that is effectively decided closes its moneyline; that is the market lifecycle, not missing data. |
| get_prematch_odds | Current prematch (pre-game) odds for this product's board — the upcoming fixtures with their OPEN markets, decimal prices and the no-vig probability on each selection. Use it for pre-game prices, closing-line-value work, pre-match modelling and no-vig fair value on tomorrow's card. Same shape as get_live_odds. Snapshot the responses yourself if you want line history; this is not an opening/closing-odds archive, not a multi-book scanner and not a bet-placement tool. |
| get_fixture | One fixture in full by id: every normalized market with its canonical key, tier, structure, status, decimal price and the no-vig probability per selection. Use it after get_live_odds or get_prematch_odds returns an id, when one match needs its whole market list. Only OPEN markets are returned by default; include=closed,suspended,resulted reveals the untradeable ones, and a RESULTED selection never carries a price under any query. A fixture leaves the board when it finishes, so an id from an earlier call can 404 — that is the market lifecycle, not an outage. |
| get_coverage | What is on the board right now: live and pre-game fixture counts per sport, plus the time of the last catalog walk. Cheap — call it first to decide whether a full board fetch is worth the request, and to resolve a sport= filter to a sport that actually has fixtures. Counts describe this product only. It is not an upsell meter and carries no prices. |
| get_health | Feed liveness and freshness: whether the upstream is connected, seconds since the last price frame, board size, market coverage and walk errors. Does not count against the rate limit. Call it before describing any data as current or fresh, and after a 503. generated_at is response time, not the age of a source price tick. |
| list_sports | Every sport id this wire understands, so a sport= filter is never a guess. Costs no API quota. A listed sport may have no fixtures today, and each product serves only its own provider — use get_coverage for what is actually on the board. Answers "which sport ids exist", not "what is live". |
| get_my_plan | This key: plan, per-second/per-minute/per-day limits, SSE entitlement and usage so far today. Costs no API quota. Use it to explain a 429 or a 401 to the user, and to tell them which limits they are actually on — the demo bucket is shared across every demo caller, so it can be spent by someone else. Not a billing or payment-history endpoint. |