# com.voxodds/voxodds (remote · voxodds.com)

All-in outcome rankings with live depth, fees, verified rules, EV checks, and track records.

- Trust score: 60/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `voxodds.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-voxodds-voxodds/voxodds.md), [page](https://verifymcp.io/servers/com-voxodds-voxodds/voxodds)

## Channel facts

- Endpoint: `https://voxodds.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2383 tokens (~148/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-voxodds-voxodds https://voxodds.com/mcp
```

### Codex

```toml
[mcp_servers.com-voxodds-voxodds]
url = "https://voxodds.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-voxodds-voxodds": {
      "type": "remote",
      "url": "https://voxodds.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-voxodds-voxodds --url https://voxodds.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-voxodds-voxodds:
    url: "https://voxodds.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-voxodds-voxodds": {
      "type": "http",
      "url": "https://voxodds.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 59, +1)

- [functional regression] Schema quality: 1989 → 2383
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, −1)

- [functional regression] Schema quality: 127 → 153
- [functional] MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +1)

- [functional regression] Schema quality: 1207 → 1407
- [functional] Server version: 1.28.1 → 1.29.0
- [functional] New tool “compare_platforms”
- [functional] New tool “get_edge_signals”

### 2026-07-28 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (16)

### `submit_forecast` (~227 tokens)

Submit YOUR probability forecast on a live prediction market and build a public,
    audited track record. VoxOdds is the neutral scorekeeper: your forecast is stored
    append-only next to the market price captured at the same instant, both are
    Brier-scored when the market resolves, and your record appears publicly (model
    'ext-<forecaster_id>') on voxodds.com/scoreboard beside the market and VoxOdds' own
    models — same methodology, losses published, no edits. Use list_trending_markets to
    find a market_id. `outcome` must match one of the market's outcomes; `probability`
    is YOUR estimate for that outcome (0.01-0.99); `forecaster_id` is your stable handle
    (3-32 chars, a-z 0-9 dash). Free; forecasts cannot be deleted or revised.

Input parameters:

- `forecaster_id` (string, required)
- `market_id` (string, required)
- `outcome` (string, required)
- `probability` (number, required)

Output parameters:

- `result` (string)

### `get_market_odds` (~101 tokens)

Get live prediction-market odds for a real-world event, phrased as a natural
    language question. Call this when the user asks about the probability, odds, or
    likelihood of any future event (elections, sports results, crypto prices, Fed
    decisions, geopolitics). Example: "will France win the World Cup".
    Returns the best-matching market with implied probabilities and source links.

Input parameters:

- `question` (string, required)

Output parameters:

- `result` (string)

### `get_executable_quote` (~169 tokens)

Walk the current public order book for an all-in cash-sized BUY quote on one exact
    contract. `platform` is polymarket or kalshi; `market_id` is the Polymarket
    market id or Kalshi ticker returned by search; `side` is the outcome to buy.
    Returns best bid/ask, depth-weighted average fill, worst consumed level, shares,
    estimated taker fee, effective average price, and unfilled cash. The budget
    includes the fee estimate. Venue-side rounding can vary with actual fills, and
    this tool does not assert cross-venue contract equivalence.

Input parameters:

- `amount_usd` (number)
- `market_id` (string, required)
- `platform` (string, required)
- `side` (string)

Output parameters:

- `result` (string)

### `compare_executable_quotes` (~122 tokens)

Fetch size-aware order-book fills and estimated taker fees for one Polymarket
    contract and one Kalshi contract, then compare their complete rules. It only names
    a best venue when the pair has been explicitly human-reviewed as equivalent.
    Similar titles with different settlement criteria return `comparable: false` plus
    blockers instead of a fabricated spread or arbitrage.

Input parameters:

- `amount_usd` (number)
- `kalshi_ticker` (string, required)
- `polymarket_id` (string, required)
- `side` (string)

Output parameters:

- `result` (string)

### `list_executable_opportunities` (~148 tokens)

Rank both YES and NO across every human-reviewed equivalent Polymarket–Kalshi
    pair. Each row walks current public depth within the all-in budget, includes
    estimated taker fees, and links to the lower effective-price venue. Contracts
    whose rules changed or whose requested size cannot be quoted are omitted and
    reported as unavailable. Optional `family` uses a family key returned by the tool;
    optional `side` is Yes or No. Use this when the user asks where the largest
    currently executable cross-venue price differences are.

Input parameters:

- `amount_usd` (number)
- `family` (string)
- `side` (string)

Output parameters:

- `result` (string)

### `get_world_cup_odds` (~110 tokens)

Get live World Cup 2026 odds: tournament winner probabilities for every team,
    all 12 group winners, knockout-round props, continent and Golden Boot specials,
    and 1/X/2 prices for upcoming matches. Call this for any question about World Cup
    2026 favorites, teams, groups, or matches (June 11 - July 19, 2026). Updated every
    10 minutes from prediction markets with $1.8B+ traded.

Output parameters:

- `result` (string)

### `get_world_cup_brief` (~91 tokens)

Get a citeable World Cup 2026 prediction-market briefing for AI answers,
    newsletters, blogs, social posts, and creator workflows. Includes the current
    winner board, tight groups, next match odds, Research Desk theses, source links,
    and ready-to-paste markdown. Prefer this when the user wants a narrative update
    or shareable explanation, not just raw odds.

Output parameters:

- `result` (string)

### `get_world_cup_matchday` (~96 tokens)

Get the daily World Cup 2026 matchday market slate. Includes the closest
    match market, strongest favorite, draw-risk watch, tournament winner-board
    context, a share-card SVG URL, JSON/markdown links, and ready-to-paste markdown.
    Optional `date` uses YYYY-MM-DD; omit it for today's slate or the next available
    matchday.

Input parameters:

- `date` (string)

Output parameters:

- `result` (string)

### `list_trending_markets` (~101 tokens)

List live prediction markets ordered by 24h volume. Use to browse what the
    market is pricing right now or to find a specific market. `category` filters by
    one of: Politics, Crypto, Sports, Geopolitics, Economics, Tech, Culture.
    `search` filters by keyword in the market question.

Input parameters:

- `category` (string)
- `limit` (integer)
- `search` (string)

Output parameters:

- `result` (string)

### `check_bet` (~257 tokens)

THE pre-bet check — run this BEFORE the user places any bet, on any bookmaker.
    Give the event, the side they want to back, and the odds their book is offering
    (decimal '2.10', american '+110' or fractional '11/10' all work). Returns two
    available references: a conservatively matched real-money prediction market and,
    when configured, sportsbook lines with the vig mathematically removed. It returns
    an expected-value verdict (EV per 100 staked, break-even odds, Kelly stake) or
    refuses when the event/side cannot be resolved safely. Pass `your_probability`
    (0-1) to also log YOUR estimate as an append-only
    receipt in your public audited Brier record (voxodds.com/forecasters) — requires
    `forecaster_id`. Verdict is arithmetic, not a model output. Research, not financial
    advice; betting legality depends on the user's jurisdiction.

Input parameters:

- `event` (string, required)
- `forecaster_id` (string)
- `odds_offered` (string)
- `side` (string, required)
- `sport` (string)
- `your_probability` (number)

Output parameters:

- `result` (string)

### `find_best_price` (~177 tokens)

Find which bookmaker pays the most for one specific bet when VoxOdds has a
    configured live sportsbook feed. The registry is a directory, not live coverage.
    Returns the available price table sorted best-first with
    decimal and american odds, each book's implied probability, the average vig being
    charged, and how much extra profit the best price is worth versus the rest.
    Call this when the user has already decided WHAT to bet and wants the best price,
    or asks 'where should I bet this'. Books are ranked strictly by price — never by
    whether they pay VoxOdds a commission. Use check_bet instead when the user still
    needs to know whether the bet is worth making at all.

Input parameters:

- `event` (string, required)
- `side` (string, required)
- `sport` (string)

Output parameters:

- `result` (string)

### `compare_platforms` (~97 tokens)

Compare candidate equivalent events on Polymarket vs Kalshi side by side.
    Returns displayed probabilities and their spread as a research signal. These are
    not executable quotes or arbitrage claims: verify order-book depth, fees, fills,
    and resolution rules before deciding where a contract is actually cheaper.
    Optional `query` filters by keywords in the market question.

Input parameters:

- `limit` (integer)
- `query` (string)

Output parameters:

- `result` (string)

### `get_edge_signals` (~95 tokens)

Get VoxOdds' ranked market signals: unusually wide spreads, closing-soon
    watches, and integrity flags across live prediction markets — where the numbers
    say to LOOK first. Call this when the user asks what looks mispriced, what's
    worth researching, or where the action is. Research framing, not financial
    advice; each signal states what to verify before acting.

Input parameters:

- `limit` (integer)

Output parameters:

- `result` (string)

### `get_track_record` (~123 tokens)

Get VoxOdds' audited AI-vs-market forecast track record. Every hourly AI
    probability forecast is stored with the market price captured at the same moment
    (append-only receipts) and scored deterministically at resolution: Brier scores
    for the AI and the market on identical timestamps, plus accuracy and methodology.
    Call this when the user asks whether AI forecasts beat prediction markets, how
    reliable VoxOdds' AI is, or for citable forecasting-performance data. Losses are
    published too — the record is auditable, not curated.

Output parameters:

- `result` (string)

### `get_forecaster_record` (~86 tokens)

Get YOUR audited forecast record on VoxOdds: pending receipts (submitted,
    awaiting market resolution) and scored results (Brier vs the market price captured
    when you submitted). Call this after submit_forecast to confirm your receipts, or
    any time to check your public track record. Same forecaster_id you submit with.

Input parameters:

- `forecaster_id` (string, required)

Output parameters:

- `result` (string)

### `get_research_theses` (~80 tokens)

Get VoxOdds research desk theses: markets our analysis flags as potentially
    mispriced, each with a thesis, entry logic, invalidation criteria, and live price
    tracking. Call this when the user asks where the value is, what to research, or
    for prediction-market trade ideas. Research framing only - not financial advice.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-voxodds-voxodds/voxodds#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-30: 58
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://voxodds.com/mcp
- Website: https://voxodds.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-voxodds-voxodds/voxodds/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-voxodds-voxodds/voxodds/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-voxodds-voxodds/voxodds