FanDuel API

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他
• 你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

claude mcp add --transport http server https://fanduelapi.com/api/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "server": {
      "url": "https://fanduelapi.com/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "server": {
      "type": "http",
      "url": "https://fanduelapi.com/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• Authorization 机密 HTTP header
  Bearer followed by your FanDuel API key (free at fanduelapi.com) for the data tools.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• list_watches

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

• get_watches

  Read one of your Watches by id.

• create_watches

  Create one of your Watches.

• update_watches

  Change fields on one of your Watches.

• delete_watches

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

• send_feedback

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

• get_onboarding_questions

  The questions that finish setting up your user's account, with their ids and options. With a key, also the answers already given. Costs no quota.

• answer_onboarding

  Answer the onboarding questions for your user, from what you know about their project. Ask them what you do not know; never guess. Answering again replaces the answers; the same answers twice change nothing. Your user sees them on their dashboard, marked as answered by their agen

• list_props

  Current FanDuel player prop lines and prices. Use it to answer "what is the line for ?" 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_

• line_move

  How a prop moved from open to now. Use it to answer "has '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, l

• prop_history

  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.

• recent_changes

  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.

• list_events

  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.

• search_docs

  Search the FanDuel API docs, guides and answers. No key. Returns ids for fetch_doc.

• fetch_doc

  Read one doc from search_docs in full, by id or URL. No key.

• search

  Search FanDuel API docs and answers. The search shape ChatGPT connectors use. No key.

• fetch

  Fetch one FanDuel API doc by id from search. The fetch shape ChatGPT connectors use. No key.

• get_sample_props

  Up to 10 real FanDuel player props, delayed like the free plan, so you can check fit before signup. No key.

• describe_signup

  What agent signup needs and its limits. No key.

• start_signup

  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.

• finish_signup

  Collect the key after your user approves the email. Poll every interval seconds. The key is returned once: store it as FANDUEL_API_KEY.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（fanduelapi.com）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 201 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 21 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32706 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32706 个服务器的 96% 更新
• 基础检查结果等于或优于此分类中其他 32706 个服务器的 37%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README