v12-dfs

Name: v12-dfs
Author: Jorgeperez0825

MCP serverMCP

AI-driven DFS lineup optimizer for MLB & NBA — build FanDuel & DraftKings lineups via MCP.

by Jorgeperez0825v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"v12-dfs","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability109/109 checks ok

Endpoints

https://v12dfs-production.up.railway.app/mcpmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	154 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
9 h ago	mcp initialize	ok	200	154 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
15 h ago	mcp initialize	ok	200	155 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
22 h ago	mcp initialize	ok	200	155 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
29 h ago	mcp initialize	ok	200	155 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	160 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	156 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	154 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	176 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools
3 d ago	mcp initialize	ok	200	156 ms	server V12 DFS Optimizer 1.0.0 · protocol 2025-06-18 · 34 tools

Tools observed via MCP handshake

agent_guide — Agent Guide Self-serve onboarding: connect any agent (Claude/MCP or REST) to drive the V12 motor, the same engine the dashboard agent uses. No auth. Returns co
health_check — Health ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "Status",
health_v12 — Health V12 Deep health check for the V12 pipeline. Surfaces: - last nightly regression run (pass/fail + per-slate deltas) - regression baseline metadata
list_slates — Get Slates List available V12 slates for today. Returns slate IDs, game counts, and lock times. ### Responses: **200**: Successful Response (Success Response
get_slate_players — Get Slate Players Endpoint Get the V12 player pool for a specific slate ID. ### Responses: **200**: Successful Response (Success Response) Content-Type: appl
slate_health — Slate Health Pre-flight diagnostic for a slate. Returns whether odds, projections, matchup, and FD master-session are ready BEFORE the agent invokes /v1/genera
slate_refresh — Slate Refresh Re-fetch projections + odds + slate metadata for a date. Writes to the configured store (Supabase in prod). Returns a summary dict (date, slate_
slate_diff — Slate Diff Compute what changed since a previously-stored snapshot. Body shape: { "slate_id": 32867, "date": "2026-05-11", "sport": "NBA", "
list_presets — Get Presets List the available strategy presets (gpp_pro_pattern, gpp_sniper, gpp_balanced, gpp_volume, cash_grinder, gpp_contrarian, gpp_mass_entry) with thei
generate_lineups — Generate Lineups ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status": "S
run_mlb_postmortem — Run Mlb Postmortem ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "status":
list_contests — Contest Registry List contest strategy registry entries for agents and the dashboard. ### Responses: **200**: Successful Response (Success Response) Content-
list_live_contests — Live Contests Return latest V12 contest context without backend identifiers. ### Responses: **200**: Successful Response (Success Response) Content-Type: app
contest_semaforo — Contest Semaforo VIP-only: per-contest play/skip verdict from the owner's verified P&L bands + structure gates + rake/fill math. See core/data/contest_semaforo
scout_field — Scout Field VIP-only (owner order 8/16): opponent-scouting profiles for the small single-entry band. The owner's $65 table runs the SAME regulars nightly; this
contest_advice — Contest Advice Advice for a concrete contest name. Resolves the name against the LIVE lobby FIRST so a real live contest is never reported missing (the curated
fill_template — Fill Template Fill a downloaded FanDuel/DK entries-template with already-generated lineups WITHOUT re-running the optimizer — the MCP-callable equivalent of th
admin_issue_key — Issue Key Idempotently issue a user's API key and ALWAYS return the paste-able connect block. Returns the email's existing active key (or mints one) so a user
betting_agent_guide — Betting Agent Guide How any agent uses the MLB betting tools + how to read the output. ### Responses: **200**: Successful Response (Success Response) Content
betting_player_form — Player Form Streak / splits / recent form for any player ('racha de X'). ### Responses: **200**: Successful Response (Success Response) Content-Type: applica
betting_analyze_prop — Analyze Prop Model a single player's prop vs tonight's FanDuel line -> edge. ### Responses: **200**: Successful Response (Success Response) Content-Type: app
betting_scan_edges — Scan Edges Tonight's prop board ranked by model edge (VALUE first). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/
betting_best_bets — Best Bets THE board sweep — scans EVERY main prop market (HR/RBI/hit/total_bases/ 2+hits/stolen_base) in one call and returns the top edges across all of them,
betting_build_parlay — Build Parlay Deterministic parlay analysis for BOTH leg shapes. Body: {legs:[...], ticket_odds?}. PROP legs {name, prop, threshold} keep the legacy correlation
betting_log_bet — Log Bet Record a bet you placed (per user) so we can track P&L + CLV over time. Body: {uid, market, selection, odds (American), stake, line?, prop?, team?, gam
betting_my_bets — My Bets A user's bet history + P&L / CLV summary. avg_clv_pct > 0 over time = you're beating the closing line = real edge (the only durable proof). ### Respon
betting_settle_bet — Settle Bet Settle a logged bet. Body: {uid, bet_id, result: won|lost|push, closing_odds?}. closing_odds lets us compute CLV (did you beat the close). ### Resp
betting_cross_book — Cross Book Cross-book value: FanDuel vs DraftKings (DK pulled via ESPN's public API, no key/WS). LINE_SHOP (the books hang different numbers — take the easier
betting_game_lines — Game Lines GAME markets — moneyline / run total / run line for today's MLB games. This answers the 'quién gana / cuántas carreras / pronóstico Yankees vs Toron
betting_market — Market FULL FanDuel market board for a team's game — EVERY market with real odds + de-vig fair price, so NO market question goes unanswered. Game lines (ML / t
betting_sharp — Sharp SHARP value — FanDuel vs PINNACLE (the sharpest book, ~2% hold). Pinnacle's de-vigged line ≈ TRUE probability, so this is the most reliable value signal
betting_game_model — Game Model MODEL the GAME run markets — TEAM TOTALS (over/under) and NRFI/YRFI — vs the FanDuel line, MARKET-ANCHORED: expected_runs = the book's de-vigged imp
betting_matchup — Matchup GROUNDING — the real game for a team today: probable pitchers + the POSTED lineup (ACTUAL player names from MLB statsapi) + the market line + the CONTE
betting_market_movers — Market Movers MARKET pattern (not model opinion): how FanDuel lines MOVED today, from the captured snapshots. A line that shortened = money coming in (sharp/ne

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

analytics.reportingReporting & Dashboards54%data.databaseDatabases53%dev.ci-cdCI/CD & Deploy53%productivity.crmCRM & Sales53%ai.promptingPrompt Management53%content.writingWriting & Editing51%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.Jorgeperez0825/v12-dfs

first seen 1 mo ago · fetched 2 h agoopen ↗

Field history (5 recent events)

1 mo ago · declared · summary → "AI-driven DFS lineup optimizer for MLB & NBA — build FanDuel & DraftKings lineups via MCP."
1 mo ago · declared · description → "AI-driven DFS lineup optimizer for MLB & NBA — build FanDuel & DraftKings lineups via MCP."
1 mo ago · declared · publisherName → "Jorgeperez0825"
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · protocols → ["mcp"]