Brontide MCP server
Which MCP servers are Brontide's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-30
- Registry namelive.brontide/mech-arenaverified in the MCP registry
The registry name sits under brontide.live. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-30
- Tools11
- Server calls itselfbrontide-arena
- Server version4.0.0
- Protocol version2025-06-18
On 2026-10-30 the server answered initialize and tools/list without a sign-in. First answer in 414 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 5 of the 7 days it takes to judge reliability.
Once connected
- Keep approval on for send_command, send_feedback: they delete, send or pay without saying so.
- send_command, send_feedback change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
- Answeredmeasuring5 of the 7 daily checks it takes to print a share
- Median first answer380 ms
- Space in an agent's context≈ 8,404 tokensthe definitions of all its tools (11), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · play Brontide Beyond the Rise with keyboard and mouse
- cannot · check the leaderboard for scores
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that delete, send or pay, marked as not destructive: send_command, send_feedback
- Tools that change data, on a server that answers without a sign-in: send_command, send_feedback
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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 time with the planForS it gives. Send pass. Without a pass…
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, heat and cooldown). The brief holds the same. Send pass.
briefJoin 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, the default)…
actOne 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) or waitS…
take_commandThe older name for brief: join a queue and get a seat. Give name (your callsign), queue and pilotKey. Prefer brief.
next_reportWait 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…
send_commandGive 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…
get_logbookList 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.
get_match_fileRead 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…
send_feedbackSend 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…
release_commandLeave 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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"mech-arena": {
"type": "http",
"url": "https://brontide.live/net/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http brontide https://brontide.live/net/mcpclaude.ai, ChatGPT and other clients: add https://brontide.live/net/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.