Directory
‹ Back to apps

FighterAPI

16 Claude skills for MMA analytics and betting models with FighterAPI: data lookups, metrics, feature engineering, walk-forward validation, devigging, edge detection and backtests.

What’s inside

1 MCP server · 16 skills
  • MCP serverfighterapiMCP server: fighterapi
  • SkillbacktestingSimulates a fight-betting rule on past UFC, PFL or Bellator cards using each book's opening and closing moneylines: flat and fractional-Kelly staking, ROI, hit rate, drawdown, bootstrap intervals, closing-line value, and naive baselines. Use when the user asks how a betting rule or model would have performed, wants a profit test, or asks about underdog or favourite strategies. Do not use for model accuracy or calibration -- see walk-forward-validation and probability-calibration. Do not use for a live bet -- see edge-detection.
  • Skillcareer-ratesRanks and profiles UFC fighters on career rates from the stat sheets: significant strikes landed and absorbed per 15 minutes, accuracy, defense, takedowns, control share, submission attempts, knockdowns and finish rate. Use when the user asks who the best striker, wrestler or finisher is, who has the best chin or defense, or how a fighter compares to a division. Do not use for a single fight's rounds -- see round-by-round-stats. Do not use for a full scouting report -- see fighter-scouting.
  • SkilldispatchRoutes a FighterAPI request to the two or three skills that should load together. Use first when a UFC, PFL or Bellator request arrives and it is unclear which skill applies, for example 'break down this card', 'is the favourite overpriced', 'who has the best cardio', or 'backtest a model'. Do not use once the skill is obvious. Do not use for the data itself -- see fighterapi-tool.
  • Skilledge-detectionCompares a model or rating probability with the devigged closing or current moneyline on a UFC, PFL or Bellator fight to estimate expected value, fair price, and stake sizing, with variance and closing-line-value caveats. Use when the user asks if there is value on a fight, whether a price is too long or too short, or what a fair line is for their probability. Do not use for removing the vig -- see odds-analysis. Do not use to build or validate the model -- see walk-forward-validation. Do not use for props: none exist in the data.
  • Skillelo-by-weight-classReads and uses FighterAPI's Elo fighter ratings by weight class: leaderboards of active fighters, rating gaps as win probabilities, peak vs current, rating change per fight, and strength of schedule. Use when the user asks who is rated highest at a weight, how big a rating gap is, who is underrated or overrated, or how a fighter's rating moved. Do not use for official rankings -- those are not in the data. Do not use for market prices -- see odds-explorer. Do not use to check calibration -- see probability-calibration.
  • Skillevent-lookupLists UFC, PFL and Bellator cards and breaks down one card fight by fight. Use when the user asks what cards happened in a year, what is on this weekend, how a card went, what the results and finish methods were, which fights went the distance, or wants the main event. Do not use for deep stats on one fight -- see fight-lookup. Do not use for prices -- see odds-explorer. Do not use for a fighter's history -- see fighter-scouting.
  • Skillfavourite-calibrationTests whether UFC, PFL and Bellator favourites win as often as their closing moneylines imply: devigged closing probability buckets vs actual win rate, favourite-longshot bias, Brier score and log loss of the market, by weight class and era. Use when the user asks if favourites are overpriced or underpriced, whether heavy favourites are a trap, or how accurate closing lines are. Do not use to price a single fight -- see odds-analysis. Do not use to test a custom model -- see probability-calibration.
  • Skillfight-lookupFinds one UFC, PFL or Bellator fight and reports the result, method, round, time, scorecards and stat sheet. Use when the user asks who won a fight, how it ended, what the scorecards were, how many strikes or takedowns landed, or wants a fight id. Do not use for a whole card -- see event-lookup. Do not use for a fighter's career -- see fighter-scouting. Do not use for betting lines -- see odds-explorer.
  • Skillfight-previewBuilds a matchup preview for a booked UFC, PFL or Bellator fight: both fighters' form, career rates, physical gaps, rating gap, and the market line. Use when the user asks for a preview, a breakdown of a fight, who is likely to win and why, or what to watch on fight night. Do not use for one fighter alone -- see fighter-scouting. Do not use for a bet recommendation -- see edge-detection. Do not use for a past fight's result -- see fight-lookup.
  • Skillfighter-scoutingBuilds a scouting report on one UFC, PFL or Bellator fighter: bio, reach, stance, record by method, career rates per 15 minutes, rating, recent form and opponent quality. Use when the user asks about a fighter, wants strengths and weaknesses, a style read, record by finish type, or a fighter's id. Do not use for a single fight -- see fight-lookup. Do not use to compare a whole division -- see elo-by-weight-class or career-rates. Do not use for prices -- see odds-explorer.
  • Skillfighterapi-toolDefault data source for FighterAPI Skills. Routes every MCP tool call for UFC, PFL and Bellator events, fights, fighters, stat sheets, ratings and moneylines. Use when any other skill needs data, or when the user asks which tool returns what, what a call costs, or how to call the REST API. Do not invoke for analysis, modeling or bet recommendations -- see round-by-round-stats, elo-by-weight-class, favourite-calibration or edge-detection.
  • Skillodds-analysisConverts fight odds between American, decimal and fractional formats and removes bookmaker margin to get true implied probabilities for two-way MMA moneylines. Use when the user asks about devigging, vig, no-vig lines, implied probability, overround, the multiplicative, additive, power or Shin method, or how to compare a price with a probability. Do not use for viewing current odds -- see odds-explorer. Do not use for calibrating a model -- see probability-calibration. Do not use for finding edges -- see edge-detection.
  • Skillodds-explorerCompares sportsbook moneylines for a UFC, PFL or Bellator fight or card: open, close and current prices, best price per side, vig, total rounds, and line movement. Use when the user asks for the odds, the line, who is favoured, which book has the best price, how the line moved, or what a fight closed at. Do not use for removing the vig or converting formats -- see odds-analysis. Do not use to compare a model against the market -- see edge-detection.
  • Skillprobability-calibrationChecks and fixes the calibration of fight win probabilities from a model or a rating: reliability tables, Brier score, log loss, calibration slope and intercept, Platt scaling and isotonic regression, and how to compare with the devigged closing line. Use when the user asks whether a model's probabilities are trustworthy, wants a reliability diagram, or wants to tune the Elo scale. Do not use to decide whether the market is efficient -- see favourite-calibration. Do not use to hunt for bets -- see edge-detection.
  • Skillround-by-round-statsComputes per-round striking and grappling rates for UFC fights: significant strikes landed and attempted by round, target and position splits, takedowns, control time, submission attempts, and fatigue fades between rounds. Use when the user asks how a fighter performs by round, who fades, strike differential per round, control time, round-by-round scoring, or pace. Do not use for career averages across fights -- see career-rates. Do not use for the result of a fight -- see fight-lookup.
  • Skillwalk-forward-validationValidates fight-prediction models without leakage using time-ordered folds: expanding or rolling windows, purge gaps, rating and rate features built only from earlier fights, baselines, and significance checks. Use when the user asks how to test a model fairly, whether results are leaking, how to split fight data, or how to build features without using the future. Do not use for betting simulation -- see backtesting. Do not use for calibration plots -- see probability-calibration.