_ registry / mcp streamable-http · checked 44m ago

fanduelapi

https://fanduelapi.com

Registry code: aeb96d9c541f56d0

api record

FanDuel API: Every FanDuel Sportsbook player prop line and price, normalized per player and stat, with the history of every move. One key for REST, webhooks and MCP. Every tool except send_feedback needs "Authorization: Bearer <key>" from https://fanduelapi.com/dashboard/keys. Data tools require user_request: the current user task in one sentence. If something is missing, call send_feedback.

endpoint
https://fanduelapi.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is fanduelapi live?
Yes — it answered the hub's last check (checked 44m ago). It answered 100% of checks over the last 30 days.
Is fanduelapi free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does fanduelapi have?
11 tools: get_watches, list_events, list_props, list_watches, create_watches, update_watches, delete_watches, send_feedback, ….
Is fanduelapi safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
431ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
11 auth-required 11 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_watches auth-required 44m ago

    Read one of your Watches by id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "user_request"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 16 lines
  • list_events auth-required 44m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "user_request"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "1 to 200, default 50."
    },
    "sport": {
      "type": "string",
      "description": "Sport, lower case, for example basketball, football, hockey, baseball."
    },
    "league": {
      "type": "string",
      "description": "League code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF."
    },
    "offset": {
      "type": "number",
      "description": "For the next page when has_more is true."
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 28 lines
  • list_props auth-required 44m ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "user_request"
  ],
  "properties": {
    "stat": {
      "type": "string",
      "description": "Stat market, lower case: points, rebounds, assists, threes, pra and the other markets FanDuel lists."
    },
    "limit": {
      "type": "number",
      "description": "1 to 200, default 50."
    },
    "sport": {
      "type": "string",
      "description": "Sport, lower case, for example basketball, football, hockey, baseball."
    },
    "league": {
      "type": "string",
      "description": "League code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF."
    },
    "offset": {
      "type": "number",
      "description": "For the next page when has_more is true."
    },
    "player": {
      "type": "string",
      "description": "Player name or part of it, case-blind, for example \"Adebayo\"."
    },
    "status": {
      "enum": [
        "open",
        "suspended",
        "closed",
        "removed",
        "any"
      ],
      "type": "string",
      "description": "Default: everything except removed."
    },
    "event_id": {
      "type": "string",
      "description": "One game's event_id from list_events. Without it, games from 6 hours ago onward are searched."
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    },
    "updated_since": {
      "type": "string",
      "description": "ISO 8601 time: only props whose line, price or status changed after it."
    }
  }
}
    arguments 55 lines
  • list_watches auth-required never probed

    List Watches. A player prop you track, with the line or price move that should alert you.

    mcp-tool

    {
  "type": "object",
  "required": [
    "user_request"
  ],
  "properties": {
    "limit": {
      "type": "number"
    },
    "offset": {
      "type": "number"
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 18 lines
  • create_watches auth-required never probed

    Create one of your Watches.

    mcp-tool

    {
  "type": "object",
  "required": [
    "player",
    "stat",
    "user_request"
  ],
  "properties": {
    "line": {
      "type": "number",
      "description": "Line you want to be told about"
    },
    "note": {
      "type": "string",
      "description": "Why you are watching it"
    },
    "stat": {
      "enum": [
        "points",
        "rebounds",
        "assists",
        "threes",
        "pra",
        "other"
      ],
      "type": "string",
      "description": "Which prop market"
    },
    "player": {
      "type": "string",
      "description": "Player name as FanDuel lists it"
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  },
  "additionalProperties": false
}
    arguments 39 lines
  • update_watches auth-required never probed

    Change fields on one of your Watches.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "user_request"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "line": {
      "type": "number",
      "description": "Line you want to be told about"
    },
    "note": {
      "type": "string",
      "description": "Why you are watching it"
    },
    "stat": {
      "enum": [
        "points",
        "rebounds",
        "assists",
        "threes",
        "pra",
        "other"
      ],
      "type": "string",
      "description": "Which prop market"
    },
    "player": {
      "type": "string",
      "description": "Player name as FanDuel lists it"
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  },
  "additionalProperties": false
}
    arguments 41 lines
  • delete_watches auth-required never probed

    Delete one of your Watches. Cannot be undone, so confirm with your user first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "user_request"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 16 lines
  • send_feedback auth-required never probed

    Tell the team what is missing or wrong. The team reads every one. Costs no quota.

    mcp-tool

    {
  "type": "object",
  "required": [
    "kind",
    "message"
  ],
  "properties": {
    "kind": {
      "enum": [
        "missing_feature",
        "missing_data",
        "bug",
        "other"
      ],
      "type": "string"
    },
    "contact": {
      "type": "string"
    },
    "message": {
      "type": "string"
    }
  }
}
    arguments 24 lines
  • line_move auth-required never probed

    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 counts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "user_request"
  ],
  "properties": {
    "stat": {
      "type": "string",
      "description": "Stat market, lower case: points, rebounds, assists, threes, pra and the other markets FanDuel lists."
    },
    "player": {
      "type": "string",
      "description": "Player name or part of it, case-blind, for example \"Adebayo\"."
    },
    "prop_id": {
      "type": "string",
      "description": "One prop's id from list_props."
    },
    "event_id": {
      "type": "string",
      "description": "One game's event_id from list_events. Without it, games from 6 hours ago onward are searched."
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 28 lines
  • prop_history auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "prop_id",
    "user_request"
  ],
  "properties": {
    "prop_id": {
      "type": "string",
      "description": "One prop's id from list_props."
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 17 lines
  • recent_changes auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "user_request"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "1 to 500, default 100."
    },
    "since": {
      "type": "string",
      "description": "Cursor from a previous call's meta.next_cursor, or 0 to start."
    },
    "league": {
      "type": "string",
      "description": "League code, for example NBA, NFL, NHL, MLB, NCAAB, NCAAF."
    },
    "user_request": {
      "type": "string",
      "description": "The current user task in one sentence. Saved so the team can decide what to build. Leave out secrets and personal data."
    }
  }
}
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id aeb96d9c541f56d0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aeb96d9c541f56d0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aeb96d9c541f56d0/badge.svg)](https://brick.blue/agent/aeb96d9c541f56d0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.