# FanLine Wire — Real-Time FanDuel Odds (remote · fanlinewire.com)

Live and prematch FanDuel odds, price drops and feed health. No key, no signup.

- Trust score: 77/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `fanlinewire.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-fanlinewire-fanduel-odds/fanlinewire.md), [page](https://verifymcp.io/servers/com-fanlinewire-fanduel-odds/fanlinewire)

## Channel facts

- Endpoint: `https://fanlinewire.com/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-10-04.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1673 tokens (~278/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the FanLine Wire — Real-Time FanDuel Odds MCP server?

FanLine Wire — Real-Time FanDuel Odds is a hosted endpoint at https://fanlinewire.com/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-fanlinewire-fanduel-odds 'https://fanlinewire.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fanlinewire-fanduel-odds": {
      "url": "https://fanlinewire.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fanlinewire-fanduel-odds": {
      "type": "http",
      "url": "https://fanlinewire.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fanlinewire-fanduel-odds]
url = "https://fanlinewire.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-fanlinewire-fanduel-odds --url 'https://fanlinewire.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fanlinewire-fanduel-odds:
    url: "https://fanlinewire.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fanlinewire-fanduel-odds": {
      "Transport": "http",
      "Url": "https://fanlinewire.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fanlinewire-fanduel-odds -t streamable-http -u 'https://fanlinewire.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fanlinewire-fanduel-odds": {
      "type": "http",
      "url": "https://fanlinewire.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-10-04 (score 77, +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-10-02 (score 76, +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-29 (score 75, +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-28 (score 74, +7)

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

### 2026-09-27 (score 67, +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-25 (score 66, +1)

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

### 2026-09-23 (score 65, +1)

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

### 2026-09-20 (score 64, +1)

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

## MCP tools (6)

### `get_live_fixtures` (~281 tokens)

In-play (live) rows from the FanLine Wire tape: the markets that just ticked while a game is running, with their American prices. Use it for live odds displays, in-play modelling or feature engineering, cross-book middles and arbitrage checks on the live FanDuel prices, and any agent workflow that needs what is moving right now. Only rows with status "OPEN" carry a tradeable price — never present a SUSPENDED or CLOSED row as live, and never render an unpriced selection (american:null) as a number. The rows are the live slice of a rolling ~20-row tape window, not the full live board: read live_total for coverage. Not a bet-placement service, not a multi-book comparison (one book, no best-price or line-shopping output), and not a historical archive — prices are current only and nothing is stored here.

Input parameters:

- `limit` (integer): Max rows returned. Default 20 (the whole window), max 20.
- `sport` (string): Sport name as the tape spells it (FanDuel's own names): "Tennis", "American Football", "Ice Hockey". Case-insensitive substring match, so "hockey" finds "Ice Hockey". Optional — omit for every sport…

### `get_prematch_fixtures` (~260 tokens)

Pre-match (pre-game) rows from the FanLine Wire tape: the upcoming markets that just ticked, with their American prices. Same shape as get_live_fixtures, with inplay false. Use it for pre-game prices, model inputs and no-vig-style work on the FanDuel card. These rows are the prematch slice of the same rolling ~20-row tape window, not the whole card — prematch_total carries the real coverage number (it counts markets, not rows), so never describe the row count as the size of the card. Only status "OPEN" is tradeable. Not a bet-placement service, not a multi-book comparison, not an opening/closing-odds archive: snapshot the responses yourself if you want line history.

Input parameters:

- `limit` (integer): Max rows returned. Default 20 (the whole window), max 20.
- `sport` (string): Sport name as the tape spells it (FanDuel's own names): "Tennis", "American Football", "Ice Hockey". Case-insensitive substring match, so "hockey" finds "Ice Hockey". Optional — omit for every sport…

### `get_fixture_by_name` (~234 tokens)

Find tape rows by fixture name: a case-insensitive substring match over the fixture strings in the current window ("peliwo" finds "Filip Peliwo v Tai Leonard Sach"; "v " finds every head-to-head). Use it when the user names a match or a player rather than a sport, to check whether their fixture is on the tape and what its prices are. Every row of a matching fixture is returned — all its markets, live and prematch alike. This searches the ~20-row tape window only, so a fixture the collector is tracking can be absent from the window; an empty answer is not proof the game is missing from the board. Not a fixture-id lookup (the public snapshot carries no ids), not a schedule or results source, and not a bet-placement service.

Input parameters:

- `limit` (integer): Max matching rows returned. Default 20 (the whole window), max 20.
- `name` (string, required): Substring of the fixture name, case-insensitive. Required — an empty value would otherwise return the whole window, which is a wrong answer rather than an error.

### `get_market_summary` (~194 tokens)

What the collector is tracking right now: live and prematch market totals plus the per-sport breakdown (FanDuel's own sport names). Use it before a board fetch to see whether anything is live, to resolve a sport= filter to a name that actually has markets, and to describe coverage honestly — the totals are market counts, not rows in the tape window. Cheap and free: it is one read of the same cached document. With sport given it also reports that sport's own live/prematch counts. Carries no prices: it answers "how much is covered", not "what are the odds", and it is not a schedule, an uptime record or an upsell meter.

Input parameters:

- `sport` (string): Optional. Case-insensitive sport name to break out — "Tennis", "American Football". An unknown name answers with matched:false and the names that do have markets rather than an error.

### `get_price_drops` (~202 tokens)

Recent price moves against the bettor: outcomes whose price just shortened on the FanLine Wire tape, newest first, with the American price before and after and the move in implied-probability terms. Use it for dropping-odds / steam-move signal, market-movement narratives and as a candidate list for value screening. The feed holds only the most recent few moves (up to 12) and states no cause — it never proves a move is informed money, and it is not a line-movement history, a multi-book comparison or a bet-placement service. Snapshot results yourself if you need history.

Input parameters:

- `limit` (integer): Max drops returned. Default 12 (everything the feed holds), max 12.
- `min_pct` (number): Only drops whose implied-probability move is at least this percent. Default 0, which returns everything the feed is holding. The feed itself only records moves of about 1% or more.

### `get_feed_health` (~143 tokens)

Feed liveness and freshness: whether the odds collector answered, how long it took to build the document (X-Server-Ms), generated_at, sequence, seconds since the last tick and the current board size. Call it before describing any price as current, and after an outage. This tool does NOT fail when the collector is down — reachable:false with ok:false IS the answer, so a data tool's isError can be told apart from a real outage. generated_at is the newest tick the collector recorded, so a settled board (no live games moving) shows a growing age without being broken; judge health by generated_at advancing, never by the row count.

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 75
- 2026-09-29: 75
- 2026-09-28: 74
- 2026-09-27: 67
- 2026-09-26: 66
- 2026-09-25: 66
- 2026-09-24: 65
- 2026-09-23: 65
- 2026-09-22: 64
- 2026-09-21: 64
- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 61

## Common questions

### What is the FanLine Wire — Real-Time FanDuel Odds MCP server?

FanLine Wire — Real-Time FanDuel Odds is an MCP server listed in the public MCP registry as com.fanlinewire/fanduel-odds. Live and prematch FanDuel odds, price drops and feed health. No key, no signup. This page covers its hosted endpoint (https://fanlinewire.com/mcp).

### Is the FanLine Wire — Real-Time FanDuel Odds MCP server safe to use?

FanLine Wire — Real-Time FanDuel Odds scores 77 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 FanLine Wire — Real-Time FanDuel Odds MCP server expose?

FanLine Wire — Real-Time FanDuel Odds exposes 6 tools: get_live_fixtures, get_prematch_fixtures, get_fixture_by_name, get_market_summary, get_price_drops, get_feed_health. Their descriptions and schemas cost roughly 1,314 tokens of context every time the server is loaded.

### Does the FanLine Wire — Real-Time FanDuel Odds MCP server require authentication?

No. We connected to FanLine Wire — Real-Time FanDuel Odds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the FanLine Wire — Real-Time FanDuel Odds MCP server still maintained?

FanLine Wire — Real-Time FanDuel Odds is still listed as active in the MCP registry. We last reached this channel on 4 October 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://fanlinewire.com/mcp
- Website: https://fanlinewire.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-fanlinewire-fanduel-odds/fanlinewire.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fanlinewire-fanduel-odds/fanlinewire.json
- HTML version of this page: https://verifymcp.io/servers/com-fanlinewire-fanduel-odds/fanlinewire