"Flask" matching MCP tools:

• list_sports

  flash-props-api

  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 }> }. id is what you pass as the sport parameter to other tools. status: "live" = props posted now, "idle" = in-season but none posted, "offseason" = out of season. projectionCapability tells you WHERE the depth is: "advanced_context" (CoD: projections + form + splits + map logs) and "flash_projection" (MLB: real season baselines + form + splits) vs "posted_lines_only" (everything else today). contextCapability "deep" means get_player_context returns data; "none" means it will be empty. 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.

  Connector

• find_game

  flash-props-api

  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 (e.g. "Yankees" or "New York Yankees" resolve for MLB) — short codes like "NYY" or "NY" do NOT match unless they are literally a substring of the team name. If no game is found, the matchup may not be scheduled for today or the sport may be off-season. When to use: when you know both team names and want the eventId without browsing the full slate. When not to use: use list_games instead when you want to browse all games on the slate. Use get_game_props directly if you already have the eventId.

  Connector

• security_fetch_package_licence

  DataNexus MCP

  Fetch the SPDX licence identifier for an open source package version. Read-only. No side effects. Idempotent. package: Package name e.g. flask. Required. version: Exact version string e.g. 2.3.0. Required. ecosystem: One of PyPI, npm, Maven, Go, Cargo, NuGet, RubyGems. Required. Returns the SPDX licence identifier e.g. MIT, Apache-2.0, GPL-3.0. Use this to verify licence compatibility before including a dependency. Use security_fetch_package_vulnerabilities instead when checking for security issues not licences. Verified source: deps.dev (Google). 1-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="security_fetch_package_licence", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".

  Connector

• list_games

  flash-props-api

  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 bv- for Bovada); live is true when the game is in progress; source is "underdog" or "bovada". 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.

  Connector

• get_game_props

  flash-props-api

  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 }. flashProjection (present for modeled markets, CoD + MLB today, when available) is { value, sampleN, method, marketKey }, the Flash season-baseline projection, never fabricated. 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 NBA, "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 bv- (Bovada source). 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 (e.g. all strikeout props today). Use find_player_props when you know the player name but not which game they are in.

  Connector

• scan_props

  flash-props-api

  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, starter: 100, pro+: 500). Returns: { sport, stat, count, rows: Array<{ player, stat, line, overOdds, underOdds, bookCount, gameState?, flashProjection?, eventId, sport, homeTeam, awayTeam, startTime, source, fetchedAt }> }. Each row is a player prop merged with its event context — there is no team or opponent field; use homeTeam/awayTeam instead. overOdds/underOdds are American-format integers; null when odds unavailable. Use scan_props when you need a broad cross-game market view — e.g. every player with a strikeouts prop today, all passing-yards lines for the slate, or which players have the most active markets. Returns count=0 with an empty rows array (not an error) when no props are posted for the day yet. When to use: broad market discovery across all games for a sport. When not to use: use get_game_props instead when you already have an eventId and want one game only — it is faster and not row-capped. Use find_player_props instead when you want all markets for one player by name.

  Connector

• get_leaders

  flash-props-api

  Ranked boards for a sport with a Flash pack. Read-only. No side effects. Pro tier and above (free/starter get a deny message). metric=gap ranks the widest Flash-vs-book edges on the live board (player, market, bookLine, flashLine, gap, gapPct); metric=form ranks players by recent mean vs their Flash Line (delta); metric=sample ranks by baseline size. Returns { sport, metric, stat, count, leaders[], note }. Works for any sport with a pack (CoD and MLB today). No picks -- a ranking of real numbers. When to use: "biggest CoD/MLB edges tonight", "who is trending over their projection". When not to use: for one prop use get_prop_evidence; for raw rows use scan_props.

  Connector

• deploy

  mcp

  Deploy an application to sota.io. The platform auto-detects your framework and builds a Docker image automatically: - Next.js: Detected via next.config.js/ts. Add output: 'standalone' to next.config for optimal builds. - Node.js: Detected via package.json with a "start" script. Works with Express, Fastify, Koa, Hapi, etc. - Python: Detected via requirements.txt or pyproject.toml. Works with Flask, FastAPI, Django. - Custom Dockerfile: If a Dockerfile exists in the project root, it takes priority over auto-detection. Use this for Go, Rust, Java, or any other language. The EXPOSE directive in the Dockerfile is used to detect the app port automatically. THREE WAYS to supply the source code — pick EXACTLY ONE: 1. **files** (inline source from AI): Pass a map of relative paths to UTF-8 text content. Best when you've just generated a small app in this conversation and want to deploy it without any filesystem step. Up to 200 files, 10 MB total. Include the framework manifest (package.json, requirements.txt, or Dockerfile) so auto-detection works. 2. **git_url** (clone a public repo): Pass an https://, git://, ssh://, or git@host:path URL. We shallow-clone it (--depth=1 --single-branch) on the server and deploy. Optional git_branch picks a non-default branch. Only public repos are supported in v1. Max 200 MB after clone. 3. **directory** (local filesystem): Pass an absolute path. Only works when the MCP client has filesystem access (Claude Code / CLI; not Claude.ai web). Defaults to the current working directory when omitted. IMPORTANT: Your app MUST listen on the PORT environment variable. For auto-detected frameworks (Next.js, Node.js, Python) PORT is 8080. For custom Dockerfiles, the port is auto-detected from the EXPOSE directive (e.g. EXPOSE 3000 sets PORT=3000). If no EXPOSE is found, it defaults to 8080. Every project includes a managed PostgreSQL 17 database. Six environment variables are auto-injected into your container — no manual database configuration needed: DATABASE_URL (full connection string), PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE. Libraries that follow libpq conventions (node-postgres, pgx, psycopg2, Django) pick up the PG* variables automatically with no configuration. If your app needs database migrations, run them on startup. Deployments use blue-green strategy for zero downtime. The old container keeps running until the new one passes health checks (60s timeout). Use get-logs to monitor build progress. Files matching .gitignore, .git/, node_modules/, .env, and .DS_Store are excluded from the archive.

  Connector

• get_market_metadata

  flash-props-api

  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 "Map 1 Kills" (kills family, map scope, projectable) so you can label and group props without guessing. 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.

  Connector

• find_player_props

  flash-props-api

  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. Use this when you know the player but not which game/event they're in.

  Connector

• get_prop_evidence

  flash-props-api

  Assemble the whole story of a single prop in one call. Read-only. No side effects. Rate-limited per your tier. Pro tier and above; free/starter keys get a structured tier_required deny. No picks, no advice -- a data feed. Returns { found, sport, player, market, event, book:{line,source,odds}, flash:{line,rawBaseline,method,sampleN,sampleStrength,mode}, gap, gapPct, form:{n,recentMean,median,stdev,min,max,hitRateVsBookLine,hitRateVsFlashLine,recent}, splits, modeSplit, opponentSplit, recentMaps, movement:{openedLine,currentLine,delta,series?}, freshness:{contextGeneratedAt,ageHours,stale,observedThrough,observedAgeHours,observedStale,note}, missingReasons, disclaimer }. freshness splits two clocks: ageHours/stale is the pack BUILD age; observedThrough/observedAgeHours/observedStale is the real age of the form data (can be far staler if ingest froze), with `note` a human "Form data through <date>" line. hitRateVsBookLine is how often recent maps went over the POSTED line (what a bettor asks); hitRateVsFlashLine is vs the Flash projection. The movement point series is Pro-only (free gets opened/current/delta). Available for sports with a registered Flash pack (CoD and MLB today); other sports return found:false with a reason, never fake data. Every absent section carries an explicit missingReason instead of being silently dropped. When to use: to explain or justify one prop end-to-end (why the Flash line sits where it does, how the player has trended, whether the line moved). When not to use: for a broad market view use scan_props; for a player overview use get_player_context.

  Connector

• create-project

  mcp

  Create a new project on sota.io. Each project automatically provisions: (1) a managed PostgreSQL 17 database accessible via the DATABASE_URL environment variable (auto-injected, no configuration needed), (2) PgBouncer connection pooling (pool size 20, max 100 clients), (3) automatic daily database backups with 7-day retention, (4) a live URL at https://{slug}.sota.io with automatic HTTPS via Let's Encrypt. The project slug is auto-generated from the name (lowercase, hyphens, max 63 chars) and is immutable after creation. Supported frameworks: Next.js, Node.js (Express/Fastify/Koa), Python (Flask/FastAPI/Django), or any language via custom Dockerfile. You can also add up to 5 custom domains per project with automatic HTTPS (via API: POST /v1/projects/:id/domains with {domain: "yourdomain.com"}). DNS: A record to 23.88.45.28 for apex domains, CNAME to {slug}.sota.io for subdomains. Optionally associate the project with a public git repository at create-time by passing `git_url` (and optional `git_branch`). The association is informational — it shows up in the dashboard and the `sota deploy --git` CLI flag can default to it — but does NOT enable auto-deploy-on-push yet.

  Connector

• calcular_energia_incidente_hv

  Arc Flash Platform — Estudos Elétricos

  Energia incidente para sistemas > 15 kV — FORA do IEEE 1584:2018 / NBR 17227 (arco ao ar livre fase-terra). É TRIAGEM, NÃO laudo: o motor IEEE 1584 da plataforma NÃO é usado; gap e configuração de eletrodos não se aplicam. `metodo` ∈ {osha (padrão), lee, epri}: • osha — OSHA 1910.269 Apêndice E, Tab. 6/7 (base ArcPro). `tipo_trabalho` ∈ {luva (Tab.6, 4–46 kV), vara (Tab.7, 4–800 kV)}. Devolve a BANDA de EPI conservadora (≤4/5/8/12 ou >12 cal/cm²), não um ponto. • lee — cota TEÓRICA superior; exige `dist_trabalho_mm`. • epri — modelo de alta tensão; exige `dist_trabalho_mm` + `comprimento_arco_m` (vão físico fase-terra, em metros). Gratuito (uso limitado).

  Connector

• get_player_context

  flash-props-api

  Season context for a player from the sport's Flash pack: per-market baselines, recent form, and sport-native splits (CoD also carries per-mode stats + a map log). Sports with a registered pack (CoD and MLB today) return data; other sports and unmatched players return an honest empty context, never fabricated. Pro tier and above; free/starter keys get a structured tier_required deny.

  Connector

• get_strategy_doc

  flash-props-api

  Returns the Flash Odds Automation OS strategy document (2026-07-17). 14 sections covering: current architecture map, automation scorecard (26/70), event model, state machine, social operating strategy, live automation maturity ladder, competitive differentiation thesis, proprietary analytics catalog, product experience, prioritized roadmap, and a concrete build-now engineering spec for the CDL result-provider adapter. Use this to understand how Flash Odds is built, what is and is not automated, what to build next, and the core design invariants (frozen claims, no fabrication, approval-gated X posts, Chamber loopback-only). Read-only. No side effects. No API key required.

  Connector

• tempo_de_atuacao

  Arc Flash Platform — Estudos Elétricos

  Tempo de atuação de um dispositivo de proteção à corrente de falta, pela curva composta 4-segmentos do motor da plataforma (IEC 60255-151 / IEEE C37.112): 51 inversa · 50 curto-tempo · 50 instantânea. É o ELO entre o curto e o arco: encadeie calcular_curto_circuito → tempo_de_atuacao → calcular_energia_incidente (o `tempo_s` daqui é o `t_arc_s`, o parâmetro mais difícil de estimar à mão). MANUAL (universal): `pickup_A` = pickup do 51 (relé: RTC×tap; disjuntor: Ir); `curva` ∈ IEC/IEEE; `tms` = TMS (IEC) ou time-dial (IEEE); `instantaneo_A`+`t_disjuntor_ms` (50 instantânea) e `curto_tempo_A`+`t_curto_tempo_ms` (50 temporizada) são opcionais — sem eles, só a inversa opera. CATÁLOGO: `device_id` de MCCB/ACB (use listar_dispositivos). Gratuito (uso limitado).

  Connector

• listar_dispositivos

  Arc Flash Platform — Estudos Elétricos

  Lista o catálogo de dispositivos (devices_db) para descobrir o `device_id` usado no modo catálogo de tempo_de_atuacao. Por padrão só MCCB/ACB (trip eletrônico com In_A real); `tipo` filtra ('MCCB','ACB','Relay','MCB','Fuse','Transformer'); `todos=True` inclui todos os tipos. Gratuito (uso limitado).

  Connector

• elevacao_temperatura_painel

  Arc Flash Platform — Estudos Elétricos

  Elevação de temperatura do ar interno de um painel BT (IEC 60890) e verificação de aceitação (61439-1). `perda_W` = perdas dissipadas no invólucro; dimensões em metros. Exposição das faces (muda a área de resfriamento): `face_topo` ∈ {exposto,coberto}; `face_traseira`/`face_laterais` ∈ {exposta,coberta} (coberta = encostada na parede / em fila → aquece mais). `tipo_instalacao` 1–5 (Fig. 4); `limite_equip_C` = limite térmico do equipamento interno (2º veredito); `regime` ∈ {BT, MT (estimativa)}. Gratuito (uso limitado).

  Connector

• calcular_curto_circuito

  Arc Flash Platform — Estudos Elétricos

  Curto-circuito (IEC 60909) pelo motor da plataforma: Icc 3φ/2φ/fase-terra, X/R e pico. Informe a rede por `potencia_curto_mva` OU `icc_rede_kA`. `com_transformador=True` dá o Icc no secundário (trafo_*). `xr_rede`/`xr_trafo` = relações X/R (regem κ, pico ip e assimetria — o making do disjuntor); `tipo_aterramento` ∈ {solido, resistivo, isolado} + `Rn_ohm` regem a corrente de falta fase-terra (Icc_1φ). `com_cabo=True` (+ cabo_secao_mm2/cabo_m) dá o Icc no PONTO de instalação após o cabo (menor que no barramento). Gratuito (uso limitado).

  Connector

• listar_dispositivos

  Arc Flash Platform — Estudos Elétricos

  Lista o catálogo de dispositivos (devices_db) para descobrir o `device_id` usado no modo catálogo de tempo_de_atuacao. Por padrão só MCCB/ACB (trip eletrônico com In_A real); `tipo` filtra ('MCCB','ACB','Relay','MCB','Fuse','Transformer'); `todos=True` inclui todos os tipos. Gratuito (uso limitado).

  Connector