flash-props-api
Flash Props API: player-prop analysis, projections, evidence, and line movement over REST/MCP.
使うべきか
品質と安全性
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"flash-props-api": {
"url": "https://api.flashodds.live/mcp"
}
}
}リモートエンドポイント
https://api.flashodds.live/mcpstreamable-httpできること
ツール一覧
ツール(12)
🟢list_sports
List every sport supported by Flash Props API with its live status and how deep the Flash model goes. Read-only. No side effects. Rate-limited per your tier. Returns { sports: Array<{ id, name, category, enabled, status, activeGames, activeProps, projectedProps, projectionCapability, effectiveProjection, contextCapability, marketFamilies, supportedMarkets, sources, lastFetchedAt, cacheAgeSeconds, shapeCanaryTripped, legalLine, notes, dataStatus, dataReason, projectableMarkets, projectionBasis, coverage, snapshotId, event, season }> }. id is what you pass as the sport parameter to other tools. status: "live" = props posted now, "idle" = none posted now but lines were archived recently, "offseason" = no lines archived for an extended period (observed, never a calendar). snapshotId identifies the exact board the counts describe. projectionCapability is the structural model ceiling; effectiveProjection tempers that by what is actually posted right now. contextCapability "deep" means a registered Flash pack can serve player context; "none" means it cannot. Call this tool instead of hard-coding which sports are modeled. enabled=false means the sport is outside your tier. When to use: to discover valid sport ids, or to check which sport actually has projections/context before asking for them. When not to use: if you already know the sport id and just want its props.
入力スキーマ
{
"type": "object",
"properties": {}
}🟢get_market_metadata(sport)
Return the machine-readable stat vocabulary for a sport: for each live market, its label, family, scope (map1/maps13/full_game), unit, display order, and whether a Flash projection is supported (with a reason when not). Read-only. No side effects. Rate-limited per your tier. Returns { sport, count, markets: Array<{ statKey, label, family, scopeKind, scope, scopeLabel, unit, displayOrder, uiGroup, projection: { supported, reason }, contextSupported, lineOnly, alternateLine }> }. This is what turns a raw stat key like "kills_on_game_1" into a labeled, scoped market so you can group props without guessing. Projection support is provider-driven per market, so partially modeled sports stay honest. When to use: after scan_props / get_game_props, to explain or group the raw stat keys you got back. When not to use: if you only need one sport's existence/access, list_sports already carries marketFamilies.
入力スキーマ
{
"type": "object",
"properties": {
"sport": {
"description": "Sport id (cod, nba, mlb, ...). Omit for the current in-season sport.",
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_games(sport)
Return today's games that have player props available for a sport. Read-only. No side effects. Requires an API key; rate-limited per your tier. Returns: { sport, count, games: Array<{ id, sport, homeTeam, awayTeam, startTime, live, source }> }. id is the eventId to pass to get_game_props (prefixed ud- for Underdog or sc- for the soccer odds board); live is true when the game is in progress; source is "underdog" or "theoddsapi". Live games sort first; scheduled games follow. Typical workflow: call list_games to discover eventIds, then pass an eventId to get_game_props. If sport is omitted the server selects the active in-season league automatically. Returns count=0 with an empty games array (not an error) when no props are posted yet for the day. When to use: to browse all games on the slate or to find an eventId before calling get_game_props. When not to use: if you already have the eventId, skip this and call get_game_props directly. Use find_game instead when you know the team names but want a single-game eventId without browsing the full slate.
入力スキーマ
{
"type": "object",
"properties": {
"sport": {
"description": "Sport id: nba, basketball, mlb, nfl, nhl, ncaab, ncaaf, soccer, tennis, cs2, valorant, dota2, esports, or cod. Omit to default to the current in-season sport.",
"type": "string"
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_game_props(eventId, sport, stats)
Fetch all player props for one game identified by eventId. Read-only. No side effects. Requires an API key; rate-limited per your tier. Returns: { eventId, sport, homeTeam, awayTeam, startTime, props: Array<{ player, stat, line, overOdds, underOdds, bookCount, gameState?, flashProjection? }>, sources: string[], fetchedAt, delayed, snapshotId, snapshotConsistency }. flashProjection is present when that sport + market has a registered Flash model and a player baseline is available; it is { value, sampleN, method, marketKey, basis, seasonId, basisNote } and is never fabricated. basis prior_season means a prior-season baseline, never current form. overOdds and underOdds are American-format integers (e.g. -110, +115); null when odds are not available. The stats parameter filters to specific markets (e.g. "points,rebounds" for basketball, "strikeouts,hits_allowed" for MLB). Typical workflow: (1) call list_games to get eventIds, (2) call get_game_props with the eventId. Alternatively, call find_game with team names to resolve the eventId when you know the matchup. Event ids are prefixed ud- (Underdog Fantasy source) or sc- (soccer odds board). Returns an error when the event id is not found, the game has ended with no active props, or lines have not been posted yet. When to use: when you have an eventId and want all props for that specific game. When not to use: use scan_props instead when you want a cross-game market view. Use find_player_props when you know the player name but not which game they are in.
入力スキーマ
{
"type": "object",
"properties": {
"eventId": {
"type": "string",
"description": "Event id from list_games or find_game. Prefixed ud- or sc-, e.g. \"ud-119284\"."
},
"sport": {
"description": "Sport id. Must match the sport the event belongs to. Omit to use the current in-season sport.",
"type": "string"
},
"stats": {
"description": "Comma-separated list of stat keys to return, e.g. \"points,rebounds,assists\" for basketball or \"strikeouts,hits_allowed\" for MLB. Omit to return all available markets.",
"type": "string"
}
},
"required": [
"eventId"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢scan_props(sport, stat, limit)
Flatten every active player prop across all of today's games for a sport into a single list. Read-only. No side effects. Requires an API key; rate-limited and row-capped per your tier (Free 25 rows, Builder 100, Pro 3,000, Enterprise 5,000). Returns: { sport, stat, count, rows: Array<{ player, stat, line, overOdds, underOdds, bookCount, gameState?, flashProjection?, eventId, sport, homeTeam, awayTeam, startTime, source, fetchedAt }>, snapshotId, snapshotConsistency }. Each row is a player prop merged with its event context; use homeTeam/awayTeam for matchup context. overOdds/underOdds are American-format integers; null when odds unavailable. Use scan_props when you need a broad cross-game market view. Returns count=0 with an empty rows array (not an error) when no props are posted for the day yet. When not to use: use get_game_props when you already have an eventId; use find_player_props for one player.
入力スキーマ
{
"type": "object",
"properties": {
"sport": {
"description": "Sport id. Omit to use the current in-season sport.",
"type": "string"
},
"stat": {
"description": "Filter to exactly one stat market. Omit to return all stat types.",
"type": "string"
},
"limit": {
"description": "Maximum number of rows to return. Capped at your tier limit (Free 25 rows, Builder 100, Pro 3,000, Enterprise 5,000). Omit to return up to your tier maximum.",
"type": "integer",
"minimum": 1,
"maximum": 5000
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢find_game(home, away, sport)
Translate a matchup (home team + away team) into the eventId needed by get_game_props. Read-only. No side effects. Requires an API key; rate-limited per your tier. Use this when you know the teams playing but don't have the eventId. On success returns: { eventId }. Pass that id straight to get_game_props. On failure returns an error explaining that the game was not found on today's board. If multiple games match the team names (rare), returns the first match sorted by start time. Matching is case-insensitive substring containment against the full team name. When not to use: use list_games to browse a slate, or get_game_props directly if you already have the eventId.
入力スキーマ
{
"type": "object",
"properties": {
"home": {
"type": "string",
"description": "Home team name or city, matched as a case-insensitive substring of the full team name."
},
"away": {
"type": "string",
"description": "Away team name or city, matched the same way."
},
"sport": {
"description": "Sport id. Omit to default to the current in-season sport.",
"type": "string"
}
},
"required": [
"home",
"away"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢find_player_props(name, sport)
Every active prop for one player across today's board for a sport; same rows as scan_props, filtered by name (exact normalized match preferred, case-insensitive contains match as a fallback; see matchType in the response) instead of stat. Read-only. No side effects. Requires an API key. When to use: you know the player but not which game or event they are in, and you want their posted lines. When not to use: get_prop_evidence explains ONE prop with its line, gap and form; get_player_context gives season baselines and recent form but no posted lines; scan_props is the whole board.
入力スキーマ
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Player name or gamertag, e.g. \"Judge\" or \"Shotzzy\""
},
"sport": {
"description": "Sport id. Defaults to the in-season sport.",
"type": "string"
}
},
"required": [
"name"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_player_context(name, sport)
Season context from the sport's registered Flash pack: per-market baselines, recent form, and sport-native splits. Free and Builder receive the same basic context shape as REST; Pro adds the dense recent map/game log when available. If the sport has no registered pack or the player is unmatched, returns an honest empty context, never fabricated data. Use list_sports first when you need to discover which sports currently advertise deep context. When to use: "what is this player averaging", "how has this player been playing lately". When not to use: it returns NO posted lines; use find_player_props for the board and get_prop_evidence for one prop against its line.
入力スキーマ
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Player name or gamertag. Exact match is preferred; no invented identity mapping."
},
"sport": {
"description": "Sport id. Use list_sports to discover contextCapability. Defaults to cod for backward compatibility.",
"type": "string"
}
},
"required": [
"name"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_prop_evidence(player, stat, sport, event)
Assemble the whole story of a single prop in one call. Read-only. No side effects. Requires an API key and is tier-shaped exactly like REST: Free gets the book/Flash/gap teaser, Builder adds recent form + Confidence summary + movement delta + teaser splits, and Pro gets the full evidence stack including movement series and deep splits. Paywall metadata says exactly which fields are withheld. No picks, no advice. Available when the sport has a registered Flash provider; otherwise returns found:false with a reason, never fake data. When to use: explain one prop end-to-end. When not to use: scan_props for broad discovery or get_player_context for a player overview.
入力スキーマ
{
"type": "object",
"properties": {
"player": {
"type": "string",
"description": "Player name or gamertag (exact normalized match preferred, contains-match fallback)."
},
"stat": {
"type": "string",
"description": "Stat key. Call get_market_metadata for the vocabulary."
},
"sport": {
"description": "Sport id. Use list_sports/get_market_metadata to discover whether the sport + market is modeled. Defaults to cod.",
"type": "string"
},
"event": {
"description": "Optional event id to disambiguate multi-game slates.",
"type": "string"
}
},
"required": [
"player",
"stat"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_prop_history(player, sport, stat, event, limit)
Chronological line/odds history for a player prop, with opened/current/movement. Free is locked with a structured tier_required response naming Builder as the first unlock. Builder receives the most recent history window; Pro receives full history. History accrues from when archiving started, so early results may be short. When to use: "has this line moved since it opened", "what did this prop open at", the timeline of ONE player prop. When not to use: scan_movers ranks movement across the whole board; get_prop_evidence already includes the movement delta beside the line.
入力スキーマ
{
"type": "object",
"properties": {
"player": {
"type": "string",
"description": "Player name (case-insensitive contains match)."
},
"sport": {
"description": "Sport id, e.g. mlb.",
"type": "string"
},
"stat": {
"description": "Stat key, e.g. total_bases.",
"type": "string"
},
"event": {
"description": "Restrict to one event id.",
"type": "string"
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 5000
}
},
"required": [
"player"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢scan_movers(sport, stat, since, limit)
Props whose line moved most within a lookback window (default 24h, max 7d), sorted by absolute movement. Free is locked with Builder as the first unlock. Builder gets a limited board; Pro gets the full movement board. When to use: "biggest movers", "which lines moved the most today", steam across a sport. When not to use: the history of one prop is get_prop_history; the current board without movement is scan_props.
入力スキーマ
{
"type": "object",
"properties": {
"sport": {
"description": "Sport id, e.g. nfl.",
"type": "string"
},
"stat": {
"description": "Stat key, e.g. passing_yards.",
"type": "string"
},
"since": {
"description": "Lookback window: e.g. 6h, 24h, 3d (1h min, 7d max). Defaults to 24h.",
"type": "string"
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 500
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_leaders(metric, sport, stat, limit)
Ranked boards for a sport with a registered Flash pack. Read-only. No side effects. Tier-shaped exactly like REST: Free sees the top 3 teaser, Builder the top 10, and Pro the full board. metric=gap ranks Flash-vs-book gaps; metric=form ranks recent mean vs Flash Line; metric=sample ranks baseline size. Paywall metadata includes totalAvailable and the next unlock when rows are capped. No picks. Use list_sports to discover which sports have deep context. When to use: "where does Flash disagree most with the books", "biggest projection gaps", "who has the strongest sample". When not to use: one player is get_player_context; the posted board is scan_props; one prop end to end is get_prop_evidence.
入力スキーマ
{
"type": "object",
"properties": {
"metric": {
"description": "gap (default), form, or sample.",
"type": "string",
"enum": [
"gap",
"form",
"sample"
]
},
"sport": {
"description": "Sport id with a registered Flash pack. Defaults to cod.",
"type": "string"
},
"stat": {
"description": "Restrict the gap board to one market.",
"type": "string"
},
"limit": {
"description": "Max rows before tier shaping (default 20).",
"type": "integer",
"minimum": 1,
"maximum": 100
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}コミュニティ
エビデンス