v12-dfs
AI-driven DFS lineup optimizer for MLB & NBA — build FanDuel & DraftKings lineups via MCP.
https://v12dfs-production.up.railway.app/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- V12 DFS Optimizer
- Version
- 1.0.0
- Capability keys
- experimental, tools
- Tool names
- agent_guide, health_check, health_v12, list_slates, get_slate_players, slate_health, slate_refresh, slate_diff, list_presets, generate_lineups, run_mlb_postmortem, list_contests, list_live_contests, contest_semaforo, scout_field, contest_advice, fill_template, admin_issue_key, betting_agent_guide, betting_player_form, betting_analyze_prop, betting_scan_edges, betting_best_bets, betting_build_parlay, betting_log_bet, betting_my_bets, betting_settle_bet, betting_cross_book, betting_game_lines, betting_market, betting_sharp, betting_game_model, betting_matchup, betting_market_movers
DFS workflow: (1) list_slates(playable=true) -> pick slate_id. (2) slate_health(slate_id, sport) BEFORE generate_lineups — a slate-locked blocker is a hard stop; 'odds/projections not cached' is only a WARNING (generate fetches them live; call slate_refresh first for the freshest data and the latest confirmations). (3) Resolve the contest: contest_advice(name) -> live_match.contest_id, or list_contests / list_live_contests. Pass a UNIQUE contest_id, never a name: if contest_advice returns ambiguous:true (same name on >1 slate), pick from alternatives by slate_id/start_time. (4) generate_lineups(date, sport, slate_id, contest_id, preset, lineups) — pass entry_template_csv (your downloaded FanDuel entries-template) for an upload-ready CSV; WITHOUT it you get a review-only roster CSV that FanDuel rejects with '0 entries updated'. Pass X-API-Key on heavy tools.
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 102ms
- respondsMCP initialize · 8s limit · HTTP 200 · 120ms
- respondsMCP initialize · 8s limit · HTTP 200 · 87ms
- respondsMCP initialize · 8s limit · HTTP 200 · 69ms