How to Use the MLB Start Score
MLB fantasy is a daily problem. Unlike NFL — where one bye week or an injury forces a single hard decision — baseball managers are making start/sit and streaming calls every day of a 162-game season. Most of the information available (recent stats, opponent reputation, the park name) is useful in vague ways without a structured framework to weigh it. The MLB Start Score is that framework.
What the number means
The Score rates each player's expected fantasy output for a single upcoming game (batters and relievers) or start (starting pitchers), then maps that projection to a 0–100 percentile rank within the scored pool at their position. An 80 means that player is in roughly the top 20% of startable options at their position for this game. A 35 means they're below midline — a bench option tonight regardless of their season reputation.
The percentile is position-specific. An 80 for a shortstop and an 80 for a catcher reflect the same thing: a strong expected performance relative to available options at that position. A first baseman at 70 isn't being compared to shortstops; he's being compared to other first basemen in today's scorable pool.
The three components
Every score is the product of three inputs: Form, Matchup, and Park. They're all visible on the tool — the number exists to aggregate them, not to replace them.
Form is season-to-date fantasy points per game (batters) or per start (SPs). It's the baseline — what this player typically produces in a normal game against an average pitcher in a neutral park. The minimum threshold is 10 plate appearances for batters and 3 innings pitched for pitchers, which eliminates the noise from early-season call-ups or players with one-game samples.
Matchup is where the daily calibration happens. For batters, it's the opposing starting pitcher's season WHIP compared to league average. A starter with a 1.60 WHIP is meaningfully different from one with a 1.05 — the batter's matchup multiplier moves accordingly. The multiplier is bounded between 0.80 and 1.20, so a strong matchup might lift a score 15–20 points, and a difficult one pulls it down the same amount. When no probable starter has been named yet, the matchup defaults to neutral (1.0).
For starting pitchers in the current version, the matchup defaults to neutral — the SP opponent lineup quality adjustment is a planned upgrade. Park factor is still applied to SPs.
Park is the home ballpark's FanGraphs 5-year regressed run factor. A park with a 110 run factor (10% more run-scoring than average) boosts batter and RP scores — more runs, more RBIs, more plate appearances in high-leverage situations. The same factor lowers SP scores by an equivalent amount. Coors Field carries the largest park multiplier in baseball; pitcher-friendly parks like Petco Park or Oracle Park flip the adjustment the other way.
Park factor is the input most managers underweight. It's stable year-over-year, it's citable, and it moves scores enough to matter on borderline decisions.
Starting pitchers — the probable starter gate
SPs are only scored when named as the probable starter in the MLB schedule for that game. An SP who pitches every fifth day has at most one scored game per week. If no probable starter is listed, no SP score appears for that slot — the tool never manufactures a score from incomplete data.
This gate matters for streaming. You shouldn't be making SP streaming decisions based on a projection that doesn't know whether the pitcher is actually starting. When the probable is confirmed, the score appears. Until then, the slot is intentionally blank.
Relief pitchers
Relievers use a simplified version of the formula: season fantasy points per game, adjusted only for park factor. There's no matchup signal for RPs — a reliever's game situation (the lead, the inning, the leverage) determines their output far more than the opposing lineup, and the model doesn't pretend otherwise. All active-roster relievers with enough sample are scored for every upcoming team game.
What it's most useful for
The Score is a tiebreaker and a prioritizer, not a scout report. Its best applications:
Start/sit between similar batters. Two corner outfielders at roughly the same season production, one facing an erratic walk-prone starter (high WHIP, good matchup) and one facing a control pitcher working efficiently (low WHIP, tougher). The matchup term captures that difference automatically.
Park-driven decisions. If you're streaming a batter or deciding between two marginal options, whether tonight's game is at Coors or Petco is a real edge that compounds. The park factor is already baked into the score.
Sorting the streaming pool. Rather than evaluating 15 potential streaming adds from memory, filter by position, sort by Score, and let the number do the first-pass work. You're still making the final call — but the field is narrowed to the options that actually make sense for tonight.
What it can't tell you
The Score is built on data through the previous night. Day-of lineup scratches, late-announced pitching changes, and a manager deciding to sit a righty against a tough same-handed pitcher — none of that is in the model. Check lineup cards before you lock in.
Early in the season, per-game averages are noisy. A batter in his 12th game has a less reliable form component than the same player in July. The tool shows sample sizes; low-sample scores carry more uncertainty than the number alone conveys.
SP matchup uses a neutral multiplier in the current version. For SP streaming decisions where opponent lineup quality is the swing factor, the MLB Pitcher Report surfaces that context directly alongside confirmed probable starters.
The formula is published and every component is visible. When the Score is wrong — when the batter with an 82 goes 0-for-4, or the pitcher with a 71 gives up five in the third — the components tell you exactly which input missed: the matchup adjustment was too optimistic, the park factor didn't account for wind, or one game produced variance. That traceability is the reason the formula is published.
Check today's ratings at RankFantasy's MLB Start Score.
All content is for fantasy baseball informational purposes only — not betting, DFS, or financial advice. Data via MLB Stats API (statsapi.mlb.com) and FanGraphs park factors. Not affiliated with or endorsed by MLB or any MLB club.
Related tools
A transparent 0–100 per-game rating for every MLB player — season form, matchup, and park factor — formula published, every input citable.
Open tool →MLB Pitcher ReportTonight's named probable starters — season form, matchup grade, and park context — the game-first SP complement to the MLB Start Score.
Open tool →MLB Fantasy Streaming FinderBest waiver-wire pickups for the next 7 days — Start Scores aggregated across all upcoming games to rank SP and batter streamers, with a 2-start bonus for pitchers.
Open tool →