MCP server for interacting with the Scryfall MTG API
FanDuel API is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
FanDuel Sportsbook player props, lines and prices as JSON, with every line and price move.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http fanduel-api-mcp https://fanduelapi.com/api/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# list_watches, get_watches, create_watches and 16 more
It needs AUTHORIZATION (Bearer followed by your FanDuel API key (free at fanduelapi.com) for the data tools): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
FanDuel API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer followed by your FanDuel API key (free at fanduelapi.com) for the data tools) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http fanduel-api-mcp https://fanduelapi.com/api/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take Authorization header (Bearer followed by your FanDuel API key (free at fanduelapi.com) for the data tools.) if you want to set it.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List Watches. A player prop you track, with the line or price move that should alert you.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | — |
| offset | number | no | — |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Read one of your Watches by id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Create one of your Watches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| player | string | yes | Player name as FanDuel lists it |
| stat | string | yes | Which prop market |
| line | number | no | Line you want to be told about |
| note | string | no | Why you are watching it |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Change fields on one of your Watches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| player | string | no | Player name as FanDuel lists it |
| stat | string | no | Which prop market |
| line | number | no | Line you want to be told about |
| note | string | no | Why you are watching it |
| id | string | yes | — |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Delete one of your Watches. Cannot be undone, so confirm with your user first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Tell the team what is missing or wrong. The team reads every one. Costs no quota.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| message | string | yes | — |
| contact | string | no | — |
Current FanDuel player prop lines and prices. Use it to answer "what is the line for <player> <stat>?" or to scan a game or league board. Each prop has line, over and under prices in American and decimal odds, status, and a move summary from open. Filter by player, stat, sport, league or event_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| player | string | no | Player name or part of it, case-blind, for example "Adebayo". |
| stat | string | no | Stat market, lower case: points, rebounds, assists, threes, pra and the other markets FanDuel lists. |
| sport | string | no | Sport, lower case, for example basketball, football, hockey, baseball. |
| league | string | no | League code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF. |
| event_id | string | no | One game's event_id from list_events. Without it, games from 6 hours ago onward are searched. |
| status | string | no | Default: everything except removed. |
| updated_since | string | no | ISO 8601 time: only props whose line, price or status changed after it. |
| limit | number | no | 1 to 200, default 50. |
| offset | number | no | For the next page when has_more is true. |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
How a prop moved from open to now. Use it to answer "has <player>'s line moved?" or "which way is the money going?". Give a prop_id for one prop, or a player (optionally stat or event_id) for all of that player's props. Returns open and current line and prices, line_move in stat units, line_direction, fair_over_move_pp (no-vig over probability shift in percentage points), price_direction and move
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prop_id | string | no | One prop's id from list_props. |
| player | string | no | Player name or part of it, case-blind, for example "Adebayo". |
| stat | string | no | Stat market, lower case: points, rebounds, assists, threes, pra and the other markets FanDuel lists. |
| event_id | string | no | One game's event_id from list_events. Without it, games from 6 hours ago onward are searched. |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Every recorded state of one prop, oldest first: each line move, price move and suspension with its time, plus the move summary. Use it after list_props or line_move when you need the full path, not just open and current.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prop_id | string | yes | One prop's id from list_props. |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
The change feed: every new prop, line move, price move and status change after a cursor, oldest first. Use it to keep up with the market without rereading the board. Start with since 0, then pass back meta.next_cursor each time. Optional league filter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | Cursor from a previous call's meta.next_cursor, or 0 to start. |
| league | string | no | League code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF. |
| limit | number | no | 1 to 500, default 100. |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Upcoming and live games FanDuel lists, with each game's event_id, start time, in-play flag and how many props it carries. Use it to find a game before calling list_props with event_id. Filter by sport or league.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sport | string | no | Sport, lower case, for example basketball, football, hockey, baseball. |
| league | string | no | League code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF. |
| limit | number | no | 1 to 200, default 50. |
| offset | number | no | For the next page when has_more is true. |
| user_request | string | yes | The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data. |
Search the FanDuel API docs, guides and answers. No key. Returns ids for fetch_doc.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What you want to know, in a few words. |
Read one doc from search_docs in full, by id or URL. No key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | An id or URL from search_docs. |
Search FanDuel API docs and answers. The search shape ChatGPT connectors use. No key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query. |
Fetch one FanDuel API doc by id from search. The fetch shape ChatGPT connectors use. No key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Id from search. |
Up to 10 real FanDuel player props, delayed like the free plan, so you can check fit before signup. No key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sport | string | no | nba, nfl, nhl, mlb, ncaab or ncaaf. |
| stat | string | no | points, rebounds, assists, threes and so on. |
| player | string | no | Part of a player name. |
| limit | number | no | 1 to 10. |
What agent signup needs and its limits. No key.
No parameter schema on file.
Start a key for your user. Ask them for their email and what they are building; never guess. They approve an emailed link (signing in first if the email already has an account); then call finish_signup.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Your user's own email address. | |
| use_case | string | yes | What they are building. |
| sports | string | no | Which sports matter most. |
| agent | string | no | Your name, plain words, up to 60 characters. |
Collect the key after your user approves the email. Poll every interval seconds. The key is returned once: store it as FANDUEL_API_KEY.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| device_code | string | yes | device_code from start_signup. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install FanDuel API or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_watches | no tags | |
| get_watches | no tags | |
| create_watches | no tags | |
| update_watches | no tags | |
| delete_watches | no tags | |
| send_feedback | no tags | |
| list_props | no tags | |
| line_move | no tags | |
| prop_history | no tags | |
| recent_changes | no tags | |
| list_events | no tags | |
| search_docs | no tags | |
| fetch_doc | untrusted-input | untrusted-input: keyword "fetch" |
| search | no tags | |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| get_sample_props | no tags | |
| describe_signup | no tags | |
| start_signup | no tags | |
| finish_signup | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish FanDuel API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.