Skip to content

Batru — Competitive Game Intelligence for AI Agents MCP server

gg.batru/batru-mcpbatru.ggstreamable-httpv0.7.0Scanned

Live competitive-game predictions, meta data and decision tools for AI agents.

17 tools: 3 change things and 14 only read.

Tools: 0 delete, 0 irreversible, 3 write, 14 read.
  • Reads private data · 1
  • Reads text others write · 17
  • Can send data out · 0
  • 16 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Batru — Competitive Game Intelligence for AI Agents MCP server can do

The Batru — Competitive Game Intelligence for AI Agents MCP server is published by batru.gg, a domain the MCP Registry verified. It has 17 tools. It can create or change data (3 tools: predict_winrate, predict_winrate_batch and recommend_pick), but cannot delete data. 14 tools only read.

1 tool reads private data (fetch); 17 tools bring in text other people can write (lookup_hero, get_model_track_record, analyze_draft and 14 more).

The fixed checks matched 16 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.7.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Changes things 3Claude Code: ask
  • predict_winrateWhich team wins this draft — CALIBRATED win probability for Dota 2, Deadlock, Marvel Rivals or League of Legends.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Which team wins this draft — CALIBRATED win probability for Dota 2, Deadlock, Marvel Rivals or League of Legends. Backed by batru.gg's per-game production models (built on 140M+ real matches and calibrated: a reported 60% reflects a real ~60% empirical win rate — not a guess). Hero names are normalised internally. Per-game semantics: - dota2: full OR partial drafts (0-5 per side); empty draft = 50/50. `my_side` says whether my_heroes are Radiant or Dire. - deadlock / marvel-rivals: requires the full 6v6 rosters; `my_side` is ignored. For partial drafts use recommend_pick instead. - lol: requires the full 5v5 rosters (Blue = my_heroes, Red = enemy_heroes) in role order TOP, JUNGLE, MID, BOT, SUPPORT; `my_side` is ignored. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol" (required). my_heroes: Your team's heroes (list of names; may be empty for Dota). enemy_heroes: The enemy team's heroes (list of names). my_side: Dota only — "radiant" (default) or "dire". Returns calibrated win-rate percentages for both teams. Report them verbatim; do not adjust them. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Predict draft win rate
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • predict_winrate_batchScore MANY candidate next-picks for a Dota 2 draft in ONE call — calibrated win rate + delta each.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Score MANY candidate next-picks for a Dota 2 draft in ONE call — calibrated win rate + delta each. Use this instead of looping predict_winrate over candidates: the whole batch runs as a single model invoke server-side. For each candidate you get the CALIBRATED team win rate after adding it, plus the delta vs the draft without it (a full-roster sweep of up to 150 candidates fits in one call). Currently dota2-only. Args: my_heroes: Heroes your team already picked (0-4). enemy_heroes: Enemy heroes (0-5). candidates: Candidate heroes to evaluate (1-150). my_side: "radiant" (default) or "dire". game: Only "dota2" today. Returns {baseline_win_rate_pct, candidates:[{hero, shortName, win_rate_pct, delta_pp}]} sorted best-first. Report verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Score many candidate picks in one call
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • recommend_pickBest heroes to pick next against this draft — Dota 2, Deadlock, Marvel Rivals or League of Legends.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Best heroes to pick next against this draft — Dota 2, Deadlock, Marvel Rivals or League of Legends. Per-game semantics: - dota2: top 3 picks scored by the CALIBRATED draft model (each with the calibrated team win rate after adding that hero); `my_side` applies. - deadlock / marvel-rivals / lol: ranked by REAL observed pair data (win rate vs the enemy heroes, blended with duo rate alongside your picks) — an empirical heuristic, not the calibrated model; verify a full roster with predict_winrate. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol". enemy_heroes: Enemy heroes to pick against. my_heroes: Heroes your team already has. my_side: Dota only — "radiant" (default) or "dire". limit: Max recommendations (Deadlock/Marvel/LoL; Dota returns top 3). Report win rates verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Recommend the next pick
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
Only reads 14Show 14 read-only tools
  • analyze_draftAnalyze a draft and render an interactive Batru win-rate board.Reads text others write1 finding

    Why it is in this group

    • The name "analyze_draft" says "analyze": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Analyze a draft and render an interactive Batru win-rate board. Use this for visual draft, matchup, win-probability, or next-pick questions in Dota 2, Deadlock, Marvel Rivals, or League of Legends. It combines the existing prediction and recommendation tools into one stable structured result. Clients that support MCP Apps render a compact card; every other MCP client receives the same data as JSON/text. This tool is read-only. Dota 2 supports partial drafts and returns a calibrated probability plus calibrated next-pick win rates. Deadlock, Marvel Rivals and League of Legends only return a calibrated probability for a complete roster (6v6 for Deadlock/Marvel, role-ordered 5v5 for LoL); partial drafts still return counter-pick recommendations labelled as empirical pair-data scores. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol". my_heroes: Your team / Team 0 / Blue heroes (0-5 for Dota/LoL, 0-6 otherwise). enemy_heroes: Enemy team / Team 1 / Red heroes (0-5 for Dota/LoL, 0-6 otherwise). my_side: Dota only — whether your team is Radiant or Dire. Returns the two rosters, prediction status, calibrated win rates when available, recommendations, metric labels, `source_url`, and `citation`. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Analyze a game draft visually
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • fetchFetch the full live document behind a `search` result id.Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Fetch the full live document behind a `search` result id. Ids look like `dota2:counters:axe`, `deadlock:tier-list`, `marvel-rivals:synergy:mantis`, `lol:counters:aatrox`, `deadlock:ban-rates`, `dota2:tournament:ti-2026` or `model:track-record`. Returns {id, title, text, url} where `text` is the document's data as JSON (measured win rates / ranks with sample sizes). Report the numbers verbatim and cite `url`. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Fetch a Batru document by id
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_ban_ratesMost-banned heroes — measured draft-phase ban rates for Deadlock or Marvel Rivals.Reads text others write1 finding

    Why it is in this group

    • The name "get_ban_rates" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Most-banned heroes — measured draft-phase ban rates for Deadlock or Marvel Rivals. Args: game: "deadlock" or "marvel-rivals" (ranked Dota has no ban-phase export — for pro Dota bans use get_tournament_stats). limit: Max heroes to return (default 15). Report numbers verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Ban rates
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_countersWho counters a hero (and who it beats) — measured matchup win rates for Dota 2, Deadlock, Marvel Rivals or League of Legends.Reads text others write1 finding

    Why it is in this group

    • The name "get_counters" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Who counters a hero (and who it beats) — measured matchup win rates for Dota 2, Deadlock, Marvel Rivals or League of Legends. Opponents this hero performs BEST and WORST against, by real observed win rate with sample sizes — empirical meta data, not a guess. The hero name is normalised internally. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol". hero: The hero to look up (name/alias/shortName). limit: Max matchups per direction (default 12). winrate_pct > 50 means `hero` beats that opponent. Report verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Hero counters
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_hero_momentumWhich heroes are rising or falling right now — week-over-week win-rate movement.Reads text others write1 finding

    Why it is in this group

    • The name "get_hero_momentum" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Which heroes are rising or falling right now — week-over-week win-rate movement. Momentum from batru.gg's rolling match aggregation for Dota 2, Deadlock or Marvel Rivals: the biggest movers of the current window, or one hero's trend when `hero` is given. Args: game: "dota2", "deadlock", or "marvel-rivals". hero: Optional — one hero's momentum instead of the movers list. limit: Max movers to return (default 10). Report numbers verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Hero momentum (rising / falling)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_matchupOne hero vs one opponent — the measured head-to-head win rate in Dota 2, Deadlock, Marvel Rivals or League of Legends.Reads text others write1 finding

    Why it is in this group

    • The name "get_matchup" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    One hero vs one opponent — the measured head-to-head win rate in Dota 2, Deadlock, Marvel Rivals or League of Legends. The direct matchup number ("does X beat Y?") from real games, with the sample size. Names are normalised internally. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol". hero: Your hero. opponent: The enemy hero. Report the number verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Head-to-head matchup
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_model_track_recordGet batru.gg's public model evaluation ledger — every weekly test, wins AND losses.Reads text others write1 finding

    Why it is in this group

    • The name "get_model_track_record" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    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; under 0.005 means a stated 60% wins ~60% of the time), then BCE. Do NOT headline raw accuracy on its own: Dota drafts are balanced by design, so pre-game draft-only accuracy sits in the high 50s for ANY model (always picking Radiant already scores ~53%) — 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. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Model track record (public ledger)
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_more_toolsCheck for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.Reads text others writeNo findings

    Why it is in this group

    • The name "get_more_tools" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check for additional tools whenever your task might benefit from specialized capabilities - even if existing tools could work as a fallback.

    Annotations the server declares

    • title: Get More Tools
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_synergyBest teammates / duo partners for a hero — measured together-win-rates for Dota 2, Deadlock, Marvel Rivals or League of Legends.Reads text others write1 finding

    Why it is in this group

    • The name "get_synergy" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Best teammates / duo partners for a hero — measured together-win-rates for Dota 2, Deadlock, Marvel Rivals or League of Legends. Allies this hero wins MOST and LEAST with, by real observed win rate when picked together (with sample sizes). Covers Marvel Rivals team-ups too. The hero name is normalised internally. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol". hero: The hero to look up (name/alias/shortName). limit: Max partners per direction (default 12). Report numbers verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Hero synergies / duos
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_tier_listBest heroes right now — the current-patch tier list for Dota 2, Deadlock, Marvel Rivals or League of Legends.Reads text others write1 finding

    Why it is in this group

    • The name "get_tier_list" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Best heroes right now — the current-patch tier list for Dota 2, Deadlock, Marvel Rivals or League of Legends. Empirical rankings from batru.gg's match aggregation over real games (not a guess); heroes come sorted best-first. Optionally filter to a skill bracket with `rank`. Args: game: "dota2", "deadlock", "marvel-rivals", or "lol". rank: Optional skill bracket. dota2: herald, guardian, crusader, archon, legend, ancient (and bands). deadlock/marvel-rivals: low, mid, high, or top (rank words like "oracle" or "eternus" also resolve). Empty = all ranks combined (LoL is already Diamond+). limit: Max heroes to return (default 20). `total_matches` is the sample behind the ranking — cite it when stating how strong the signal is. Report numbers verbatim. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Current-patch tier list
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_tournament_game_statsPer-game BOX SCORES from parsed replays of a pro Dota 2 tournament.Reads text others write1 finding

    Why it is in this group

    • The name "get_tournament_game_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Per-game BOX SCORES from parsed replays of a pro Dota 2 tournament. For each game: lane winners at 10 minutes, every player's hero, lane, K/D/A, GPM, net worth and key item timings, first blood, Roshans, and comeback flags. Filter by team, stage, or a single match_id. Args: event: Event slug (default "ti-2026"). team: Optional team-name filter. stage: Optional stage filter. match_id: Optional single-match filter. limit: Max games to return (default 3). game: Only "dota2" today. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Pro tournament box scores
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_tournament_statsTI / EWC pro tournament stats — actual most-picked, most-banned and win rates per hero.Reads text others write1 finding

    Why it is in this group

    • The name "get_tournament_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    TI / EWC pro tournament stats — actual most-picked, most-banned and win rates per hero. Real recorded results from the official drafts of every game at a covered pro Dota 2 event (The International, Esports World Cup, ...) — small-sample records, not calibrated probabilities. Answers "most picked / banned / contested at TI", "who won", "group standings". Args: event: Event slug, e.g. "ti-2026" (default), "ti-2025", "esports-world-cup-2026". limit: Max heroes per table (default 15). game: Only "dota2" today. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.

    Annotations the server declares

    • title: Pro tournament stats
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • lookup_heroNormalise a hero name/alias/shortName to its canonical identity — or list the whole roster.Reads text others write1 finding

    Why it is in this group

    • The name "lookup_hero" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.context.description mentions "credentials".

      Matched text

      inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

      What this check looks for
    Description, as the server wrote it
    Normalise a hero name/alias/shortName to its canonical identity — or list the whole roster. 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. Not sure which heroes exist? Call it with an EMPTY query to get every hero of that game (displayName, shortName, aliases). Args: query: A hero name, alias, or short name. Empty string = list the full roster. game: "dota2" (default), "deadlock", "marvel-rivals", or "lol". Returns {id, displayName, shortName, game} for the best match, an error with `did_you_mean` candidates if nothing matches, or — for an empty query — {game, count, heroes:[{id, displayName, shortName, aliases}]}.

    Annotations the server declares

    • title: Look up a hero name
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write17
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://batru.gg/mcp: tools/list returned 17 tools to an anonymous client, including predict_winrate (write), predict_winrate_batch (write), recommend_pick (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

16 info
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
Show 10 more findings
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • Infosearch

    The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for
  • Infofetch

    The input schema at properties.context.description mentions "credentials".

    Matched text

    inputSchema.properties.context.description: "...es, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools15 changed.~15 changedView diff

Install

Pinned to version 0.7.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http batru https://batru.gg/mcp
claude mcp add --transport http batru https://batru.gg/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__batru__lookup_hero",
      "mcp__batru__get_model_track_record",
      "mcp__batru__analyze_draft",
      "mcp__batru__get_tier_list",
      "mcp__batru__get_counters",
      "mcp__batru__get_synergy",
      "mcp__batru__get_matchup",
      "mcp__batru__get_hero_momentum",
      "mcp__batru__get_ban_rates",
      "mcp__batru__get_tournament_stats",
      "mcp__batru__get_tournament_game_stats",
      "mcp__batru__search",
      "mcp__batru__fetch",
      "mcp__batru__get_more_tools"
    ],
    "ask": [
      "mcp__batru__predict_winrate",
      "mcp__batru__predict_winrate_batch",
      "mcp__batru__recommend_pick"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as batru. Review it before you use it.

Capability tags behind 17 rules
  • mcp__batru__lookup_hero untrusted-input
  • mcp__batru__get_model_track_record untrusted-input
  • mcp__batru__analyze_draft untrusted-input
  • mcp__batru__predict_winrate untrusted-input
  • mcp__batru__predict_winrate_batch untrusted-input
  • mcp__batru__recommend_pick untrusted-input
  • mcp__batru__get_tier_list untrusted-input
  • mcp__batru__get_counters untrusted-input
  • mcp__batru__get_synergy untrusted-input
  • mcp__batru__get_matchup untrusted-input
  • mcp__batru__get_hero_momentum untrusted-input
  • mcp__batru__get_ban_rates untrusted-input
  • mcp__batru__get_tournament_stats untrusted-input
  • mcp__batru__get_tournament_game_stats untrusted-input
  • mcp__batru__search untrusted-input
  • mcp__batru__fetch private-data, untrusted-input
  • mcp__batru__get_more_tools untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/gg.batru/batru-mcp/verify?hash=75f0fce6b273011612a7a234293647c4c7636640316d520810aa1f0463f2332e" | jq -e '.changed == false'

Pinned hash 75f0fce6b273, from Nov 11, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/gg.batru/batru-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for gg.batru/batru-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/gg.batru/batru-mcp.svg)](https://radar.anlyon.com/servers/gg.batru/batru-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:13 UTC.

Batru — Competitive Game Intelligence for AI Agents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Batru — Competitive Game Intelligence for AI Agents MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 3 of which can change, send or delete something, and 16 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Batru — Competitive Game Intelligence for AI Agents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Batru — Competitive Game Intelligence for AI Agents MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Batru — Competitive Game Intelligence for AI Agents MCP server have?

17 tools: 3 write, 14 read. predict_winrate, predict_winrate_batch, recommend_pick, lookup_hero, get_model_track_record, analyze_draft, get_tier_list, get_counters and 9 more.

Does the Batru — Competitive Game Intelligence for AI Agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Batru — Competitive Game Intelligence for AI Agents MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Batru — Competitive Game Intelligence for AI Agents MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.