Oddiwire MCP server

• Registry namecom.oddiwire/esports-oddsverified in the MCP registry

The registry name sits under oddiwire.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools7
• Server calls itselfwire-api
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 222 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
• Answeredmeasuring4 of the 7 daily checks it takes to print a share
• Median first answer225 ms
• Space in an agent's context≈ 1,591 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…