Skip to content

FanLine Wire — Real-Time FanDuel Odds MCP server

com.fanlinewire/fanduel-oddsfanlinewire.comstreamable-httpv1.0.0Scanned

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

6 tools: 6 only read.

Tools: 0 delete, 0 irreversible, 0 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the FanLine Wire — Real-Time FanDuel Odds MCP server can do

The FanLine Wire — Real-Time FanDuel Odds MCP server is published by fanlinewire.com, a domain the MCP Registry verified. It has 6 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (get_feed_health).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Only reads 6Show 6 read-only tools
  • get_feed_healthFeed 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 …Reads private dataNo findings

    Why it is in this group

    • The name "get_feed_health" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_fixture_by_nameFind 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 ever…No findings

    Why it is in this group

    • The name "get_fixture_by_name" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_live_fixturesIn-play (live) rows from the FanLine Wire tape: the markets that just ticked while a game is running, with their American prices.No findings

    Why it is in this group

    • The name "get_live_fixtures" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_market_summaryWhat the collector is tracking right now: live and prematch market totals plus the per-sport breakdown (FanDuel's own sport names).No findings

    Why it is in this group

    • The name "get_market_summary" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_prematch_fixturesPre-match (pre-game) rows from the FanLine Wire tape: the upcoming markets that just ticked, with their American prices.No findings

    Why it is in this group

    • The name "get_prematch_fixtures" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • get_price_dropsRecent 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-…No findings

    Why it is in this group

    • The name "get_price_drops" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:38 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fanduel-odds https://fanlinewire.com/mcp
claude mcp add --transport http fanduel-odds https://fanlinewire.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fanduel-odds__get_live_fixtures",
      "mcp__fanduel-odds__get_prematch_fixtures",
      "mcp__fanduel-odds__get_fixture_by_name",
      "mcp__fanduel-odds__get_market_summary",
      "mcp__fanduel-odds__get_price_drops",
      "mcp__fanduel-odds__get_feed_health"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fanduel-odds. Review it before you use it.

Capability tags behind 1 rule
  • mcp__fanduel-odds__get_feed_health private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.fanlinewire/fanduel-odds/verify?hash=0a8ffdbd670421b90b7f57e087c34ffcd3313a368deb7c00597cb0b6477527c5" | jq -e '.changed == false'

Pinned hash 0a8ffdbd6704, from Nov 13, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.fanlinewire/fanduel-odds/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.fanlinewire/fanduel-odds
[![Anlyon Radar](https://radar.anlyon.com/badge/com.fanlinewire/fanduel-odds.svg)](https://radar.anlyon.com/servers/com.fanlinewire/fanduel-odds)

Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.

FanLine Wire — Real-Time FanDuel Odds MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 6 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the FanLine Wire — Real-Time FanDuel Odds MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FanLine Wire — Real-Time FanDuel Odds MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FanLine Wire — Real-Time FanDuel Odds MCP server have?

6 tools: 6 read. get_live_fixtures, get_prematch_fixtures, get_fixture_by_name, get_market_summary, get_price_drops and get_feed_health.

Does the FanLine Wire — Real-Time FanDuel Odds MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FanLine Wire — Real-Time FanDuel Odds MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FanLine Wire — Real-Time FanDuel Odds MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.