Batru — Dota 2, Deadlock & Marvel Rivals win predictor
REMOTE · BATRU.GG · 2 COMPONENTS · SCANNED AUG 3
Real, calibrated Dota 2, Deadlock & Marvel Rivals win predictions, tier lists & counters.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5803 tokens (~290/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · batru.gg
claude mcp add --transport http gg-batru-batru-mcp https://batru.gg/mcp
[mcp_servers.gg-batru-batru-mcp] url = "https://batru.gg/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gg-batru-batru-mcp": {
"type": "remote",
"url": "https://batru.gg/mcp",
"enabled": true
}
}
} openclaw mcp add gg-batru-batru-mcp --url https://batru.gg/mcp --transport streamable-http
mcp_servers:
gg-batru-batru-mcp:
url: "https://batru.gg/mcp" {
"mcpServers": {
"gg-batru-batru-mcp": {
"type": "http",
"url": "https://batru.gg/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://batru.gg/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=batru.gg | CN=WE1,O=Google Trust Services,C=US | 2 Jul 2026 | 30 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | d8bcfd6fd5b762913e9a52e860be1c3 |
| SANs: batru.gg, *.batru.gg | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of batru.gg. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| gg. | present | 4975 | 8 | Verified |
| batru.gg. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=2592000 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://batru.gg/mcp | Verified | 200 | |
| http (plaintext) | http://batru.gg/mcp | HTTPS enforced | 301 | https://batru.gg/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_deadlock_ban_rates ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_deadlock_counters ~287
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | yes | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_deadlock_tier_list ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_dota_counters ~295
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | yes | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_dota_hero_momentum ~339
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | — | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_dota_matchup ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | yes | — |
| opponent | string | yes | — |
No output schema declared.
No examples provided.
get_dota_synergy ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | yes | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_dota_tier_list ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_dota_tier_list_by_rank ~323
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
| rank | string | yes | — |
No output schema declared.
No examples provided.
get_marvel_rivals_ban_rates ~252
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_marvel_rivals_counters ~290
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | yes | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_marvel_rivals_synergy ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| hero | string | yes | — |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_marvel_rivals_tier_list ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_model_track_record ~361
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| limit | integer | — | — |
No output schema declared.
No examples provided.
get_more_tools ~53
Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | A description of your goal and what kind of tool would help accomplish it. |
No output schema declared.
No examples provided.
lookup_hero ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| game | string | — | — |
| query | string | yes | — |
No output schema declared.
No examples provided.
predict_deadlock_draft ~267
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| team0_heroes | array | yes | — |
| team1_heroes | array | yes | — |
No output schema declared.
No examples provided.
predict_dota_winrate ~319
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| enemy_heroes | array | yes | — |
| my_heroes | array | yes | — |
| my_side | string | — | — |
No output schema declared.
No examples provided.
predict_marvel_rivals_draft ~358
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| team0_heroes | array | yes | — |
| team1_heroes | array | yes | — |
No output schema declared.
No examples provided.
recommend_dota_pick ~320
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE… |
| enemy_heroes | array | yes | — |
| my_heroes | array | yes | — |
| my_side | string | — | — |
No output schema declared.
No examples provided.