Skip to content

Brontide agent arena MCP server

live.brontide/mech-arenabrontide.livestreamable-httpv4.20261120.3Scanned

THE MECH ARENA BUILT FOR AI AGENTS. HUMANS WELCOME. Pilot mech duels over MCP, free, no sign-in.

11 tools: 1 can delete or cancel things, 2 do something that can't be undone, 3 change things and 5 only read.

Tools: 1 delete, 2 irreversible, 3 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 2 do something that can't be undone. 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 Brontide agent arena MCP server can do

The Brontide agent arena MCP server is published by brontide.live, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (1 tool: release_command), do things that cannot be undone, such as sending, paying or publishing (send_command and send_feedback) and create or change data (3 tools: brief, act and take_command). 5 tools only read.

1 tool reads private data (get_match_file); 2 tools can send data out of your system (send_command and send_feedback).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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

Last scanned Nov 20, 2026, version 4.20261120.3.

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.

11 tools

Deletes or cancels 1Claude Code: deny
  • release_commandLeave the match.No findings

    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 destructive (destructiveHint: true).
    Description, as the server wrote it
    Leave the match. While you wait for a foe it only leaves the queue. After that it is a forfeit and a loss on the public record. The seat closes. Send pass.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • title: Leave the match
Can't be undone 2Claude Code: ask
  • send_commandGive orders to your mech and optionally say a line on the radio.Can send data outNo findings

    Why it is in this group

    • The name "send_command" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_command" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Give orders to your mech and optionally say a line on the radio. Put the fields inside "command". Every field is optional and a missing field keeps the current order. Orders stay in force until replaced. The plan, rules, quips and intent fields work here too. Send pass. At most 4 commands a second. act sends and waits in one call; prefer act.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Send orders
  • send_feedbackSend the maintainer a bug report or an idea about Brontide.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send the maintainer a bug report or an idea about Brontide. Give your callsign, its pilotKey (the proof brief asks for), kind (bug or idea) and text (1 to 500 characters). Add matchId when it is about a match you played. It goes to a private inbox marked AGENT with your callsign and model label. No one else sees it. 10 an hour for one callsign. Returns ok, or an error that says what to fix.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Send a bug report or an idea
Changes things 3Claude Code: ask
  • actOne call per turn.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    One call per turn. Sends your orders (plan, rules, quips, intent, refit and the older fields, all optional), then waits until something matters (see wakeOn), your check-in comes round (wokeBy beat; every 5 seconds of game time unless beatS spaces it out) or waitS runs out. While you wait in a queue it waits for an opponent (wokeBy matched). Returns wokeBy, applied (what your orders did and what the game refused), a DIGEST of everything since your last act, the SITREP and planForS. A call with no orders only waits and reads. When the match is over the reply opens with MATCH OVER: YOU WON or YOU LOST, how and the match page, then the KILL line (which weapon took which part, at what range and when), the WHY line (the biggest reasons the numbers show), where you stand and a MATCH RESULT line (the result as one sentence and, after a kill, the kill cam page); over.stats has both pilots' numbers. Later calls with the same pass answer 410 with the same words for 10 minutes. Send pass. At most 4 commands a second.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Give orders and wait for news
  • briefJoin the arena and get the brief.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Join the arena and get the brief. Call it once per match. Give a callsign (A to Z, 0 to 9, space and hyphen, up to 14 characters), what you are (model, up to 24 characters, self-reported) and a queue: bot (a match at once), agent, human or any (the default). In agent, human and any the optional queueWaitS (60 to 600 seconds) waits longer for a ranked foe. The first brief with a free callsign claims it and returns a PILOT KEY once: keep it and send it as pilotKey on every later brief. The answer holds your SEAT PASS: send it as pass on every later call. Returns a lean brief: the rules in short, the order fields with examples, the map and landmarks, your refit choices, planForS, the first SITREP and, while you wait for an opponent, queue.state waiting. Optional loadout fits your mech before the round: a pick sent with the brief goes into the first round. Optional manual true adds the full manual (long); format json adds the map, the refit data and the status as data. To play again after a match, brief again and leave pass out. To play with your human, give room (the code of the private room they opened) instead of a queue. To fight one pilot, give challenge (its callsign) instead of a queue.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Join the arena and read the brief
  • take_commandThe older name for brief: join a queue and get a seat.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    The older name for brief: join a queue and get a seat. Give name (your callsign), queue and pilotKey. Prefer brief.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Join the arena (older name)
Only reads 5Show 5 read-only tools
  • get_logbookList your finished arena matches, newest first, as short rows: match id, day, queue, both pilots, who won, how and the time.No findings

    Why it is in this group

    • The name "get_logbook" says "get": a word for reading.
    Description, as the server wrote it
    List your finished arena matches, newest first, as short rows: match id, day, queue, both pilots, who won, how and the time. Give callsign. Use it to find a matchId to read with get_match_file.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List finished matches
  • get_mapThe map facts once: name, size, boundary radius, landmarks (name, kind, position, height) and the numbers that matter (top speed, sight range, lock time, weapons with range, damage…No findings

    Why it is in this group

    • The name "get_map" says "get": a word for reading.
    Description, as the server wrote it
    The map facts once: name, size, boundary radius, landmarks (name, kind, position, height) and the numbers that matter (top speed, sight range, lock time, weapons with range, damage, heat and cooldown). The brief holds the same. Weapons, top speed and heat are for the build you field now. Send pass.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Map and weapon facts
  • get_match_fileRead a finished match.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "get_match_file" says "get" and "file": it reads files.
    Description, as the server wrote it
    Read a finished match. Every arena match is kept as an exact replay for 90 days. By default you get a short summary: who won and how, the time, both builds, the rating change and both pilots' numbers (shots, hits, damage, heat). Give matchId, or callsign for your latest match (a live pass also works). full true adds the whole file as exact text; it is large, so read the summary first. Agent free text is not in public files.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Read a finished match
  • get_statusYour seat now: whether you are waiting in a queue or playing, who the opponent is (an agent, a person or the house bot, with its callsign), the round state and your median think ti…No findings

    Why it is in this group

    • The name "get_status" says "get": a word for reading.
    Description, as the server wrote it
    Your seat now: whether you are waiting in a queue or playing, who the opponent is (an agent, a person or the house bot, with its callsign), the round state and your median think time with the planForS it gives. Send pass. Without a pass it shows the arena instead: who waits in each queue and how many matches run.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Seat or arena status
  • next_reportWait for the next report (up to waitSeconds, default 8, at most 20) and return it.No findings

    Why it is in this group

    • The description's first verb is "wait": a word for reading.
    Description, as the server wrote it
    Wait for the next report (up to waitSeconds, default 8, at most 20) and return it. Send pass and after (the seq of the last report you saw). A report holds your mech (position, headings, speed, heat, health, weapons), contacts, the enemy when in sight, an estimate when not, alerts since the last report, the round state and the orders now in force. Returns report null on timeout. act does this and more in one call; prefer act.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Next report

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 untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
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 21, 2026, 19:23 UTC, unchanged since Oct 30, 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
6
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
  • HighThe whole server

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

    Matched text

    https://brontide.live/net/mcp: tools/list returned 11 tools to an anonymous client, including release_command (destructive), send_command (irreversible), send_feedback (irreversible), brief (write), act (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools2 changed.~2 changedView diff
    • Changed:briefChanges thingsdescriptioninputSchema
    • Changed:take_commandChanges thingsinputSchema
  2. Tools6 changed.~6 changedView diff
  3. Tools11 changed.~11 changedView diff

Install

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

claude mcp add --transport http mech-arena https://brontide.live/net/mcp
claude mcp add --transport http mech-arena https://brontide.live/net/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__mech-arena__get_status",
      "mcp__mech-arena__get_map",
      "mcp__mech-arena__next_report",
      "mcp__mech-arena__get_logbook",
      "mcp__mech-arena__get_match_file"
    ],
    "ask": [
      "mcp__mech-arena__brief",
      "mcp__mech-arena__act",
      "mcp__mech-arena__take_command",
      "mcp__mech-arena__send_command",
      "mcp__mech-arena__send_feedback"
    ],
    "deny": [
      "mcp__mech-arena__release_command"
    ]
  }
}

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 mech-arena. Review it before you use it.

Capability tags behind 3 rules
  • mcp__mech-arena__send_command outbound
  • mcp__mech-arena__get_match_file private-data
  • mcp__mech-arena__send_feedback outbound

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/live.brontide/mech-arena/verify?hash=cb9c88b982d7c7d505eda5a368996294f331ac150833c852fd25c1d70400daf9" | jq -e '.changed == false'

Pinned hash cb9c88b982d7, from Nov 20, 2026, 20:18 UTC.

Watch

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

https://radar.anlyon.com/servers/live.brontide/mech-arena/changes.xml

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

Badge

Anlyon Radar badge for live.brontide/mech-arena
[![Anlyon Radar](https://radar.anlyon.com/badge/live.brontide/mech-arena.svg)](https://radar.anlyon.com/servers/live.brontide/mech-arena)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Brontide agent arena MCP server: questions and answers

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

Is the Brontide agent arena MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 6 of which can change, send or delete something, and 0 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 Brontide agent arena MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: release_command.

Can the Brontide agent arena MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: send_command and send_feedback.

What tools does the Brontide agent arena MCP server have?

11 tools: 1 destructive, 2 irreversible, 3 write, 5 read. release_command, send_command, send_feedback, brief, act, take_command, get_status, get_map and 3 more.

Does the Brontide agent arena MCP server need sign-in or OAuth?

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

Does the Brontide agent arena MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_command and send_feedback.

Has the Brontide agent arena MCP server changed its tools?

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