mcp server
Batru — Dota 2, Deadlock & Marvel Rivals win predictor
Real, calibrated Dota 2, Deadlock & Marvel Rivals win predictions, tier lists & counters.
Description as published by the maintainer. Source
- version 0.3.1
- active
active — Most recent push to the repository was 2026-07-18.
What this server can do
20 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_deadlock_ban_rates(limit, context)- Get the most-banned Deadlock heroes from real games. Ban rate reveals what players FEAR facing — a different signal from win rate. Empirical data from batru.gg's match aggregation. Heroes come sorted most-banned first. Args: limit: Max number of heroes to return (default 15). Returns {generated_at, ban_matches, heroes:[{hero, rank, ban_rate_pct, bans}]}. `ban_matches` is the sample of matches with ban data; cite `generated_at` when freshness matters. Report numbers verbatim. Required: context.
get_deadlock_counters(hero, limit, context)- Get the strongest matchups (counters) for a Deadlock hero from real games. Returns opponents this hero performs BEST and WORST against, by real observed matchup win rate (with sample sizes). Empirical meta data from batru.gg's match aggregation, not a guess. The hero name is normalised internally. Args: hero: The hero to look up (name/alias). limit: Max number of matchups to return (default 12). Returns {hero, best_against:[...], worst_against:[...]} where each row has {opponent, winrate_pct, matches}. winrate_pct > 50 means `hero` beats that opponent. Report numbers verbatim. Required: hero, context.
get_deadlock_tier_list(limit, context)- Get the current Deadlock hero tier list (best heroes) from real games. Ranked by batru.gg's match aggregation — empirical meta, not a guess. Heroes come sorted best-first (rank 1 = strongest). Report numbers verbatim. Args: limit: Max number of heroes to return (default 20). Returns {total_matches, generated_at, heroes:[{hero, rank, winrate_pct, pick_rate_pct, matches}]}. Cite `total_matches` for the sample size. Required: context.
get_dota_counters(hero, limit, context)- Get the strongest matchups (counters) for a Dota 2 hero from real games. Returns opponents this hero performs BEST and WORST against, by real observed matchup win rate (with sample sizes). This is empirical meta data from batru.gg's match aggregation, not a guess. The hero name is normalised internally. Args: hero: The hero to look up (name/alias/shortName). limit: Max number of matchups to return (default 12). Returns {hero, best_against:[...], worst_against:[...]} where each row has {opponent, winrate_pct, matches}. winrate_pct > 50 means `hero` beats that opponent. Report numbers verbatim. Required: hero, context.
get_dota_hero_momentum(hero, limit, context)- Get which Dota 2 heroes are rising or falling in the current patch. Compares each hero's win rate over the last 14 days vs the prior 14 days WITHIN the current patch — real trend data from batru.gg's match aggregation, not a guess. Useful for "what's getting stronger lately?" questions between patches. Args: hero: Optional — a specific hero to look up. Empty returns the top risers and fallers overview. limit: Max risers/fallers to return in overview mode (default 10). Returns {patch, window_days, data_through, ...} plus either one hero's {hero, wr_recent_pct, wr_prev_pct, delta_pp, n_recent, n_prev} or {risers:[...], fallers:[...]}. delta_pp is percentage-point change; small deltas (<1pp) are noise — say so rather than over-reading them. Required: context.
get_dota_matchup(hero, context, opponent)- Get the head-to-head win rate for one specific Dota 2 hero pair. Returns how `hero` performs AGAINST `opponent` (opposite teams) from real observed games, with the sample size. Empirical data from batru.gg's match aggregation covering every tracked pair — not a guess. Both names are normalised internally. Args: hero: Your hero (name/alias/shortName). opponent: The enemy hero (name/alias/shortName). Returns {hero, opponent, winrate_pct, matches}. winrate_pct > 50 means `hero` beats `opponent` more often than not. Report numbers verbatim. Required: hero, opponent, context.
get_dota_synergy(hero, limit, context)- Get the best (and worst) TEAMMATES for a Dota 2 hero from real games. Returns teammates this hero performs BEST and WORST paired with (same team), by real observed team win rate with sample sizes. Empirical meta data from batru.gg's match aggregation, not a guess. The hero name is normalised internally. Args: hero: The hero to look up (name/alias/shortName). limit: Max number of teammates to return (default 12). Returns {hero, best_with:[...], worst_with:[...]} where each row has {teammate, winrate_pct, matches}. winrate_pct is the pair's team win rate when both heroes play together. Report numbers verbatim. Required: hero, context.
get_dota_tier_list(limit, context)- Get the current Dota 2 hero tier list (best heroes this patch) from real games. Ranked by batru.gg's match aggregation over ~real games — empirical meta, not a guess. Heroes come sorted best-first (rank 1 = strongest). Report numbers verbatim. Args: limit: Max number of heroes to return (default 20). Returns {total_matches, generated_at, heroes:[{hero, rank, winrate_pct, pick_rate_pct, matches}]}. `total_matches` is the sample the ranking is drawn from — cite it when stating how strong the signal is. Required: context.
get_dota_tier_list_by_rank(rank, limit, context)- Get the Dota 2 hero tier list for a specific rank bracket. The meta differs a LOT by skill level — heroes that stomp Herald games can be poor in Immortal. Data comes in four bands: Herald & Guardian, Crusader & Archon, Legend & Ancient (merged pairs — the source has no finer grain), and Divine & Immortal ("highrank"). Args: rank: A rank name — one of herald, guardian, crusader, archon, legend, ancient, divine, immortal (or a band key like "herald-guardian"). limit: Max number of heroes to return (default 20). Returns {bracket, total_matches, generated_at, heroes:[{hero, rank, winrate_pct, pick_rate_pct, matches}]} sorted best-first. Report numbers verbatim and mention which band the numbers come from. Required: rank, context.
get_marvel_rivals_ban_rates(limit, context)- Get the most-banned Marvel Rivals heroes from real competitive games. Ban rate reveals what players FEAR facing — a different signal from win rate. Empirical data from batru.gg's match aggregation (competitive mode, where bans exist). Heroes come sorted most-banned first. Args: limit: Max number of heroes to return (default 15). Returns {generated_at, ban_matches, heroes:[{hero, rank, ban_rate_pct, bans}]}. ALWAYS cite `generated_at` — ban snapshots can lag the current season. Report numbers verbatim. Required: context.
get_marvel_rivals_counters(hero, limit, context)- Get the strongest matchups (counters) for a Marvel Rivals hero from real games. Returns opponents this hero performs BEST and WORST against, by real observed matchup win rate (with sample sizes). Empirical meta data from batru.gg's match aggregation, not a guess. The hero name is normalised internally. Args: hero: The hero to look up (name/alias). limit: Max number of matchups to return (default 12). Returns {hero, best_against:[...], worst_against:[...]} where each row has {opponent, winrate_pct, matches}. winrate_pct > 50 means `hero` beats that opponent. Report numbers verbatim. Required: hero, context.
get_marvel_rivals_synergy(hero, limit, context)- Get the best (and worst) TEAMMATES for a Marvel Rivals hero from real games. Returns teammates this hero performs BEST and WORST paired with, by real observed team win rate (with sample sizes). Empirical meta data from batru.gg's match aggregation, not a guess. The hero name is normalised internally. Args: hero: The hero to look up (name/alias). limit: Max number of teammates to return (default 12). Returns {hero, best_with:[...], worst_with:[...]} where each row has {teammate, winrate_pct, matches}. winrate_pct > 50 means the pairing wins more than average. Report numbers verbatim. Required: hero, context.
get_marvel_rivals_tier_list(limit, context)- Get the current Marvel Rivals hero tier list (best heroes) from real games. Ranked by batru.gg's match aggregation — empirical meta, not a guess. Heroes come sorted best-first (rank 1 = strongest). Report numbers verbatim. Args: limit: Max number of heroes to return (default 20). Returns {total_matches, generated_at, heroes:[{hero, rank, winrate_pct, pick_rate_pct, matches}]}. Cite `total_matches` for the sample size. Required: context.
get_model_track_record(limit, context)- Get batru.gg's public model evaluation ledger — every weekly test, wins AND losses. batru.gg publishes EVERY champion-vs-challenger evaluation of its Dota 2 model (promoted or rejected), auto-generated from the promotion gate's append-only log — nothing is hand-picked. Use this when a user asks whether the model is any good or how it is validated. HOW TO PRESENT IT: lead with CALIBRATION (ECE — lower is better; ~0.006 means a stated 60% wins ~60% of the time), then BCE. Do NOT headline raw accuracy: Dota drafts are balanced by design, so ~55% is near the game-imposed ceiling for ANY model — calibration is the meaningful claim. Args: limit: Max evaluations to return, newest first (default 10). Returns {generated_at, ledger, total_evaluations, total_promotions, evaluations:[{decided_at, promote, challenger:{ece,bce,acc}, champion:{ece,bce,acc}, holdout_n}]}. Report numbers verbatim. Required: context.
get_more_tools(context)- Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback. Required: context.
lookup_hero(game, query, context)- Normalise a hero name/alias/shortName to its canonical identity. Use this to turn messy user input ("am", "anti mage", "Anti-Mage") into the exact key batru.gg expects before calling the prediction tools. The backend SILENTLY DROPS hero names it doesn't recognise, so always normalise first. Args: query: A hero name, alias, or short name. game: "dota2" (default), "deadlock", or "marvel-rivals". Returns {id, displayName, shortName, game} for the best match, or an error with `did_you_mean` candidates if nothing matches. Required: query, context.
predict_deadlock_draft(context, team0_heroes, team1_heroes)- Predict the CALIBRATED win probability for a Deadlock 6v6 draft. Backed by batru.gg's Deadlock production model. Provide 6 heroes per team (names are normalised to Deadlock hero ids internally). A reported 60% reflects a real ~60% empirical win rate — it is calibrated, not a guess. Args: team0_heroes: Team 0's 6 heroes (names/aliases). team1_heroes: Team 1's 6 heroes (names/aliases). Returns calibrated win-rate percentages for both teams. Report verbatim. Required: team0_heroes, team1_heroes, context.
predict_dota_winrate(context, my_side, my_heroes, enemy_heroes)- Predict the CALIBRATED win rate for a Dota 2 draft. Backed by batru.gg's production model (trained on ~20M real matches and calibrated, so a reported 60% reflects a real ~60% empirical win rate — it is not a guess). Partial drafts are fine; an empty draft returns 50/50. Hero names are normalised internally to shortNames. Args: my_heroes: Your team's heroes (names/aliases, 0-5). enemy_heroes: Enemy heroes (names/aliases, 0-5). my_side: "radiant" (default) or "dire" — which side is "my_heroes". Returns calibrated win-rate percentages for both teams. Report these numbers verbatim; do not adjust them. Required: my_heroes, enemy_heroes, context.
predict_marvel_rivals_draft(context, team0_heroes, team1_heroes)- Predict the CALIBRATED win probability for a Marvel Rivals 6v6 draft. Backed by batru.gg's live Marvel Rivals production model (weekly auto-retrained on real matches). Provide exactly 6 heroes per team (names are normalised to Marvel Rivals hero ids internally). The probability is CALIBRATED — a reported 60% reflects a real ~60% empirical win rate, not a guess. Report the number verbatim. This is a COMPOSITION-ONLY estimate: it reflects the hero draft, NOT player skill, rank, or in-game execution. It is for draft analysis only — not betting advice. Do not headline a raw "accuracy" figure; present it as a calibrated probability. Args: team0_heroes: Team 0's 6 heroes (names/aliases). team1_heroes: Team 1's 6 heroes (names/aliases). Returns calibrated win-rate percentages for both teams. Report verbatim. Required: team0_heroes, team1_heroes, context.
recommend_dota_pick(context, my_side, my_heroes, enemy_heroes)- Recommend the top 3 Dota 2 heroes to pick next, with calibrated win rates. Backed by batru.gg's production model. Each suggestion comes with the CALIBRATED win rate your team would have after adding that hero against the given enemy draft (a reported 60% reflects a real ~60% empirical win rate). Hero names are normalised internally. Args: my_heroes: Heroes your team has already picked (names/aliases, 0-4). enemy_heroes: Enemy heroes (names/aliases, 0-5). my_side: "radiant" (default) or "dire" — which side is "my_heroes". Returns a list of up to 3 {displayName, shortName, win_rate_pct}. Report the win rates verbatim. Required: my_heroes, enemy_heroes, context.
Last successful function declaration observed on . Source: https://batru.gg/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://batru.gg/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-18 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.3.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-25 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-25 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 20 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | batru.gg | |
| mcp endpoint status | ok | The server listed 20 functions when asked. | as of probe | batru.gg |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json