FanLine Wire — Real-Time FanDuel Odds
REMOTE · FANLINEWIRE.COM · SCANNED OCT 4
Live and prematch FanDuel odds, price drops and feed health. No key, no signup.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · fanlinewire.com
claude mcp add --transport http com-fanlinewire-fanduel-odds 'https://fanlinewire.com/mcp'
{
"mcpServers": {
"com-fanlinewire-fanduel-odds": {
"url": "https://fanlinewire.com/mcp"
}
}
} {
"servers": {
"com-fanlinewire-fanduel-odds": {
"type": "http",
"url": "https://fanlinewire.com/mcp"
}
}
} [mcp_servers.com-fanlinewire-fanduel-odds] url = "https://fanlinewire.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-fanlinewire-fanduel-odds": {
"type": "remote",
"url": "https://fanlinewire.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-fanlinewire-fanduel-odds --url 'https://fanlinewire.com/mcp' --transport streamable-http
mcp_servers:
com-fanlinewire-fanduel-odds:
url: "https://fanlinewire.com/mcp" {
"McpServers": {
"com-fanlinewire-fanduel-odds": {
"Transport": "http",
"Url": "https://fanlinewire.com/mcp"
}
}
} assistant mcp add com-fanlinewire-fanduel-odds -t streamable-http -u 'https://fanlinewire.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +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.
- 2 Oct 26 +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.
- 29 Sept 26 +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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +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.
- 20 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://fanlinewire.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fanlinewire.com | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ac2ed16063117d50132438c5ce0aecc2 |
| SANs: fanlinewire.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fanlinewire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fanlinewire.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fanlinewire.com/mcp | Verified | 200 | |
| http (plaintext) | http://fanlinewire.com/mcp | HTTPS enforced | 301 | https://fanlinewire.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_feed_health ~143
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fixture_by_name ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matching rows returned. Default 20 (the whole window), max 20. |
| name | string | yes | 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. |
No output schema declared.
No examples provided.
get_live_fixtures ~281
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
get_market_summary ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_prematch_fixtures ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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… |
No output schema declared.
No examples provided.
get_price_drops ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.