# VotePredictor Elections (remote · votepredictor.com)

2026 US election forecasts with a public accuracy record, plus congressional voting records.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `votepredictor.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-votepredictor-elections/api-mcp.md), [page](https://verifymcp.io/servers/com-votepredictor-elections/api-mcp)

## Channel facts

- Endpoint: `https://votepredictor.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 568 tokens (~142/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the VotePredictor Elections MCP server?

VotePredictor Elections is a hosted endpoint at https://votepredictor.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-votepredictor-elections 'https://votepredictor.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-votepredictor-elections": {
      "url": "https://votepredictor.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-votepredictor-elections": {
      "type": "http",
      "url": "https://votepredictor.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-votepredictor-elections]
url = "https://votepredictor.com/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-votepredictor-elections --url 'https://votepredictor.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-votepredictor-elections:
    url: "https://votepredictor.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-votepredictor-elections": {
      "Transport": "http",
      "Url": "https://votepredictor.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-votepredictor-elections -t streamable-http -u 'https://votepredictor.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-votepredictor-elections": {
      "type": "http",
      "url": "https://votepredictor.com/api/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-09-20 (score 86, +1)

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

### 2026-09-18 (score 85, +1)

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

### 2026-09-16 (score 84, +1)

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

### 2026-09-14 (score 83, +1)

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

### 2026-09-12 (score 82, +1)

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

### 2026-09-09 (score 81, +1)

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

### 2026-09-07 (score 80, +1)

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

### 2026-09-05 (score 79, +1)

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

## MCP tools (4)

### `forecast_race` (~157 tokens)

Forecast a 2026 race

Current VotePredictor forecast for one 2026 US election: win probability, predicted margin, whether it comes from polls or fundamentals, how far it has moved this cycle, and the candidates. Accepts a state name or code ('Ohio', 'OH') or a district ('CA-12'). Returns an explicit refusal for races where a candidate has left the ballot and no forecast is published.

Input parameters:

- `office` (string, required): Which office: SEN for U.S. Senate, GOV for governor, HOUSE for a U.S. House district.
- `where` (string, required): Where the race is: a state name ('Ohio'), a two-letter state code ('OH'), or a House district ('CA-12'). Pass what the user said.

Output parameters:

- `dem_candidate`
- `forecast_published` (boolean): False when this site declines to publish a probability for the race
- `location`: State code, or district id for the House
- `movement_points`: Change in win probability in POINTS since the first snapshot this cycle, positive toward Democrats
- `n_polls`
- `no_forecast_reason`: Why nothing is published, e.g. a candidate has left the ballot. Do not substitute your own estimate.
- `office`
- `p_dem_win`: Democratic win probability, 0.01-0.99. Never 0 or 1: an election that has not happened is not certain.
- `pred_margin`: Predicted Dem-minus-Rep margin in points
- `race_id` (string): Canonical id, {year}_{OFFICE}_{location}
- `rating`: Safe D / Likely D / Lean D / Toss-up / Lean R / Likely R / Safe R
- `rep_candidate`
- `source`: 'polls' where a poll-driven forecast exists, otherwise 'fundamentals' (lean, incumbency, national environment)
- `state_name`
- `summary` (string): One-paragraph answer suitable for reading aloud
- `url` (string): Cite this

### `chamber_outlook` (~80 tokens)

Chamber control outlook

Who is favoured to control the Senate or House after 2026: control probability, expected seats with an 80% range, how far it has moved since January, and the races that have moved most.

Input parameters:

- `chamber` (string, required): Which chamber of Congress: 'senate' (51 seats for control) or 'house' (218).

Output parameters:

- `as_of` (string)
- `biggest_movers` (array)
- `chamber` (string)
- `change_points_since` (number): Points moved since the first snapshot, positive toward Democrats
- `expected_dem_seats` (number)
- `p_dem_control` (number): Probability Democrats control the chamber
- `range_80pct` (array): [p10, p90] seats in 80% of simulations
- `seats_from_fundamentals` (number): Forecast without any poll, because none exists
- `seats_needed` (number)
- `seats_total` (number)
- `seats_with_forecast` (number)
- `seats_without_forecast` (number): Publishing nothing, because a candidate left the ballot
- `since_date` (string)
- `summary` (string)
- `url` (string)

### `forecaster_accuracy` (~104 tokens)

Forecast accuracy track record

How accurate each election forecaster, model, prediction market and pollster has been on resolved races, adjusted for how hard each race was. Use this to answer 'whose election forecast should I trust'. Difficulty adjustment matters: on raw scores whoever rated the safest races wins.

Input parameters:

- `limit` (integer): How many ranked entries to return, best first. Default 10.
- `office` (string): Restrict the board to one office, or ALL for every resolved race.

Output parameters:

- `adjusted_for_difficulty` (boolean): True. Raw scores reward whoever rated the safest races, so unadjusted rankings mislead.
- `entries` (array)
- `lower_is_better` (boolean)
- `metric` (string)
- `office` (string)
- `summary` (string)
- `url` (string)

### `member_profile` (~92 tokens)

Member of Congress

A member of Congress by name or bioguide id: party, state, ideology score, reported net worth from financial disclosures, and the 2026 race for their seat.

Input parameters:

- `who` (string, required): Who to look up: a surname ('Pelosi'), a full name, or a bioguide id ('P000197'). If several sitting members match, the tool returns the candidates rather than choosing one.

Output parameters:

- `ambiguous_matches`: Populated when the name matches several sitting members; ask the user which, do not pick one
- `bioguide_id`
- `chamber`
- `currently_serving`: False for a former member. Lookup still resolves them, but they are not in office and are not a candidate.
- `found` (boolean)
- `name`
- `net_worth_range`: [low, high] in dollars. Disclosures report brackets, never an exact figure.
- `net_worth_year`
- `party`
- `race_2026`: Race id for their seat, if it is on the 2026 ballot AND they still hold it
- `state`
- `summary` (string)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-09-21: 86
- 2026-09-20: 86
- 2026-09-19: 85
- 2026-09-18: 85
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 81
- 2026-09-08: 80
- 2026-09-07: 80
- 2026-09-06: 79
- 2026-09-05: 79
- 2026-09-04: 78
- 2026-09-03: 78
- 2026-09-02: 77
- 2026-09-01: 77
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 75
- 2026-08-28: 75
- 2026-08-27: 74
- 2026-08-26: 74

## Common questions

### What is the VotePredictor Elections MCP server?

VotePredictor Elections is an MCP server listed in the public MCP registry as com.votepredictor/elections. 2026 US election forecasts with a public accuracy record, plus congressional voting records. This page covers its hosted endpoint (https://votepredictor.com/api/mcp).

### Is the VotePredictor Elections MCP server safe to use?

VotePredictor Elections scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VotePredictor Elections MCP server expose?

VotePredictor Elections exposes 4 tools: forecast_race, chamber_outlook, forecaster_accuracy, member_profile. Their descriptions and schemas cost roughly 433 tokens of context every time the server is loaded.

### Does the VotePredictor Elections MCP server require authentication?

No. We connected to VotePredictor Elections without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VotePredictor Elections MCP server still maintained?

VotePredictor Elections is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

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