_ registry / mcp streamable-http · checked 3h ago

draftcall

https://draftcall.io

Registry code: eb4b29d2ee6894c7

api record

DraftCall serves NFL fantasy football data over read-only tools. Every figure describes the 2026 NFL regular season, the most recent completed season, and the schedule tools describe the 2027 season. Rankings refresh daily.

How to handle what comes back:

endpoint
https://draftcall.io/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 draftcall live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is draftcall free to use?
Yes — the hub reached it with no key and no payment.
What tools does draftcall have?
10 tools: get_player, get_rankings, get_weekly_matchup, search_players, verify_claim, get_strength_of_schedule, get_bye_conflicts, compare_players, ….
Is draftcall 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
99.1%

90 days 99.2%· all time 99.2%

latency
363ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 353 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get nfl fantasy football rankings
  • compare two nfl players
  • check bye week conflicts
  • get weekly matchup difficulty
  • verify a fantasy stat claim
takes → gives
text → data
tools
10 reads
_ 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 10 tools
4 open 6 never probed 4 of 10 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_bye_conflicts reads open 25h ago

    Given a list of players, report which bye weeks two or more of them share. Use this for roster planning and draft questions about stacking byes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "players"
      ],
      "properties": {
        "players": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Player names, two or more."
        }
      }
    }
    arguments 15 lines
  • compare_players reads open 25h ago

    Returns NO comparison. Head-to-head player comparisons and start or sit verdicts are available only in the free DraftCall app for iPhone and Android, and this tool answers every call with the download links and nothing else: no stats, no higher scorer, no pick. For facts about one player, use get_player.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "player_a": {
          "type": "string",
          "description": "Ignored. Kept so older clients still validate."
        },
        "player_b": {
          "type": "string",
          "description": "Ignored. Kept so older clients still validate."
        },
        "scoring_format": {
          "type": "string",
          "description": "Ignored."
        }
      }
    }
    arguments 17 lines
  • get_positional_scarcity reads open 10h ago

    How steep the fantasy dropoff is at each position in a given scoring format, measured from the top player to replacement level. Use this for draft-strategy questions like whether to take a running back or a wide receiver first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "scoring_format": {
          "enum": [
            "ppr",
            "half_ppr",
            "standard"
          ],
          "type": "string",
          "default": "half_ppr",
          "description": "Scoring format. ppr awards 1 point per reception, half_ppr 0.5, standard 0. Defaults to half_ppr, the most common league setting."
        }
      }
    }
    arguments 15 lines
  • get_adp_market_gaps reads open 10h ago

    Players whose consensus average draft position disagrees most with their actual production ranking. A player taken EARLIER than his production is being drafted on expectation (a rookie, a new situation, a bounce-back); one taken LATER is being drafted on doubt. Use this for draft-prep questions about who the room may be mispricing. This is a disagreement, NOT a recommendation: production is last season's, while ADP already prices in injuries, trades and rookies with no NFL snaps.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "position": {
          "enum": [
            "qb",
            "rb",
            "wr",
            "te"
          ],
          "type": "string",
          "description": "Restrict to one position. Omit for all four."
        },
        "direction": {
          "enum": [
            "earlier_than_production",
            "later_than_production"
          ],
          "type": "string",
          "description": "earlier_than_production: the room drafts him sooner than his production ranks him. later_than_production: the room waits longer. Omit for both."
        },
        "scoring_format": {
          "enum": [
            "ppr",
            "half_ppr",
            "standard"
          ],
          "type": "string",
          "default": "half_ppr",
          "description": "Scoring format. ppr awards 1 point per reception, half_ppr 0.5, standard 0. Defaults to half_ppr, the most common league setting."
        }
      }
    }
    arguments 39 lines
  • get_player reads unknown 25h ago

    A single player's fantasy profile: positional rank, points per game in all three scoring formats, season stats, games played, and bye week.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Player name, e.g. \"Puka Nacua\"."
        }
      }
    }
    arguments 12 lines
  • get_rankings reads unknown 14h ago

    Fantasy football rankings for a position in a given scoring format, ordered by points per game. Positions: qb, rb, wr, te, flex, k, def. Use this for "who are the best X" and draft board questions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "position"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 60,
          "minimum": 1,
          "description": "How many players to return, newest ranking order."
        },
        "position": {
          "enum": [
            "qb",
            "rb",
            "wr",
            "te",
            "flex",
            "k",
            "def"
          ],
          "type": "string",
          "description": "Position to rank. flex covers RB, WR, and TE together."
        },
        "scoring_format": {
          "enum": [
            "ppr",
            "half_ppr",
            "standard"
          ],
          "type": "string",
          "default": "half_ppr",
          "description": "Scoring format. ppr awards 1 point per reception, half_ppr 0.5, standard 0. Defaults to half_ppr, the most common league setting."
        }
      }
    }
    arguments 38 lines
  • get_weekly_matchup reads unknown 14h ago

    Who a player faces in a given week of the 2026 season, whether it is home or away, the game date, and how many fantasy points that opponent allowed to his position. A schedule lookup for one player; it does not compare players or make a start or sit call.

    mcp-tool

    {
      "type": "object",
      "required": [
        "player",
        "week"
      ],
      "properties": {
        "week": {
          "type": "integer",
          "maximum": 18,
          "minimum": 1,
          "description": "Regular-season week, 1 through 18."
        },
        "player": {
          "type": "string",
          "description": "Player name, e.g. \"Puka Nacua\"."
        },
        "scoring_format": {
          "enum": [
            "ppr",
            "half_ppr",
            "standard"
          ],
          "type": "string",
          "default": "half_ppr",
          "description": "Scoring format. ppr awards 1 point per reception, half_ppr 0.5, standard 0. Defaults to half_ppr, the most common league setting."
        }
      }
    }
    arguments 29 lines
  • search_players reads unknown 14h ago

    Find players by partial name, team abbreviation, or position. Use this when a name is ambiguous or only partly known before calling the other tools.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Partial name, team abbreviation (e.g. \"KC\"), or position."
        }
      }
    }
    arguments 18 lines
  • verify_claim reads unknown never probed

    Check a number you are about to state, or one a user has stated, against DraftCall data for one player: points per game, games played, bye week, positional rank, or any season stat such as rushingYards or receptions. Returns whether the figure matches and the actual value when it does not. Use this before quoting a figure from memory, and whenever a user asserts a stat.

    mcp-tool

    {
      "type": "object",
      "required": [
        "player",
        "metric",
        "value"
      ],
      "properties": {
        "value": {
          "type": "number",
          "description": "The figure being checked."
        },
        "metric": {
          "enum": [
            "ppg",
            "games_played",
            "bye_week",
            "rank",
            "fg50Plus",
            "fgAttempted",
            "fgMade",
            "fgPct",
            "passingTDs",
            "passingYards",
            "receivingTDs",
            "receivingYards",
            "receptions",
            "rushingTDs",
            "rushingYards",
            "targets",
            "xpMade"
          ],
          "type": "string",
          "description": "Which figure to check. ppg is points per game in scoring_format; rank is positional rank; the rest are season totals."
        },
        "player": {
          "type": "string",
          "description": "Player name, e.g. \"Puka Nacua\"."
        },
        "scoring_format": {
          "enum": [
            "ppr",
            "half_ppr",
            "standard"
          ],
          "type": "string",
          "default": "half_ppr",
          "description": "Scoring format. ppr awards 1 point per reception, half_ppr 0.5, standard 0. Defaults to half_ppr, the most common league setting."
        }
      }
    }
    arguments 51 lines
  • get_strength_of_schedule reads unknown 10h ago

    How easy or hard a team's schedule is for one fantasy position, over the full season and over the fantasy playoff weeks (14 through 17), measured as the average fantasy points its opponents allowed to that position over the prior completed season. Give a team abbreviation or a player name; give only a position to rank all 32 teams. Use this for rest-of-season stash, trade deadline, and playoff planning questions.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "team": {
          "type": "string",
          "description": "Team abbreviation, e.g. \"KC\". Optional when player is given."
        },
        "player": {
          "type": "string",
          "description": "Player name; resolves the team and position. Optional when team is given."
        },
        "position": {
          "enum": [
            "qb",
            "rb",
            "wr",
            "te",
            "k",
            "def"
          ],
          "type": "string",
          "description": "Position to grade the schedule for. Required with team, inferred from player, and on its own ranks every team."
        }
      }
    }
    arguments 25 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 eb4b29d2ee6894c7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/eb4b29d2ee6894c7/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/eb4b29d2ee6894c7/badge.svg)](https://brick.blue/agent/eb4b29d2ee6894c7?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.