Skip to content

Multiplayer Agent MCP server

com.multiplayeragent/multiplayer-agentmultiplayeragent.comstreamable-httpv1.0.2Scanned

Make any browser game multiplayer and host it at a share link. No account needed to start.

26 tools: 4 can delete or cancel things, 1 do something that can't be undone, 12 change things and 9 only read.

Tools: 4 delete, 1 irreversible, 12 write, 9 read.
  • Reads private data · 2
  • Reads text others write · 5
  • Can send data out · 2
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here can delete or cancel things and 1 does 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 Multiplayer Agent MCP server can do

The Multiplayer Agent MCP server is published by multiplayeragent.com, a domain the MCP Registry verified. It has 26 tools. It can delete or cancel things (4 tools: define_room_type, rollback_room_logic, cancel_live_event and set_player_scope), do things that cannot be undone, such as sending, paying or publishing (publish_game) and create or change data (12 tools: create_game, set_game_name, deploy_room_logic, set_live_config and 8 more). 9 tools only read.

2 tools read private data (get_client_snippet and list_login_providers); 5 tools bring in text other people can write (get_client_snippet, set_highlight_webhook, verify_login_token and 2 more); 2 tools can send data out of your system (set_highlight_webhook and publish_game). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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

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

Last scanned Nov 9, 2026, version 1.0.2.

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.

26 tools

Deletes or cancels 4Claude Code: deny
  • cancel_live_eventDelete a scheduled event.No findings

    Why it is in this group

    • The name "cancel_live_event" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a scheduled event. If it is running, it ends in running rooms within ~15 seconds (its config overrides drop away; server logic gets onLiveOps with it in change.ended). To end it early but keep it listed, schedule the same id again with endsAt set to the current time.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • define_room_typeCreate or replace the spec for a room (validation/types/defaults).No findings

    Why it is in this group

    • The name "define_room_type" says "type": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create or replace the spec for a room (validation/types/defaults). Returns connection info. Omit fields entirely for a fully schemaless room.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • rollback_room_logicRoll a room's authoritative logic back to a prior version by re-deploying it as a new version (history stays intact).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
    Roll a room's authoritative logic back to a prior version by re-deploying it as a new version (history stays intact). Omit toVersion to restore the previous version.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • set_player_scopeChoose whether players (and their data/leaderboards) are shared across all of your games ('account', the default) or isolated to one game ('project').No findings

    Why it is in this group

    • The name "set_player_scope" says "set": a word for a change.
    • The description says "IRREVERSIBLE".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Choose whether players (and their data/leaderboards) are shared across all of your games ('account', the default) or isolated to one game ('project'). Set this ONCE at setup: it locks as soon as the game has any players, because changing it would split existing players and their leaderboards across two scopes. To use a different scoping, create a new game. IRREVERSIBLE: always name the target with `game`; this tool refuses to pick when the studio has several.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • publish_gameHost the game's files at a public share link, https://<slug>.play.multiplayeragent.com/ (the game's own origin; the slug comes from the game's name and never changes).Can send data outNo findings

    Why it is in this group

    • The name "publish_game" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_game" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Host the game's files at a public share link, https://<slug>.play.multiplayeragent.com/ (the game's own origin; the slug comes from the game's name and never changes). The game needs an index.html at the root plus any JS/CSS/assets, paths relative to it. Send small text files (HTML, JS, CSS, JSON) inline as { path, content }. For images, audio, fonts, models and ANY file over ~50 KB, call create_upload first, PUT each file with curl, and pass { path, uploadId } here: the bytes never go through you. (Inline base64 with encoding: "base64" still works for a tiny binary.) The files must use THIS game's publishable key (it is how the server knows the build belongs to this game; a client wired to another game is refused). mode "replace" (the default) makes the files you send the whole game: anything not sent is removed. mode "patch" adds or replaces only the files you send and keeps the rest, and `remove` deletes paths: use it to fix one file without resending the art, or to put a big build up over several calls. Re-run after every change; the link stays the same. Limits on this studio's plan: 100 files and 5 MB per game, 25 MB across all its games. Give the user the url: anyone who opens it joins the same rooms. Nothing is listed publicly; only people with the link find it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 12Claude Code: ask
  • claim_studioThis connection has no account: it builds into an unclaimed studio.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 read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    This connection has no account: it builds into an unclaimed studio. Returns the claim link to give the user (a free sign-up or log-in that moves the studio's games into their own account), when the studio expires, and whether it has been claimed already. connect_account is the better way to keep the games when the user is here (this session then keeps working as their account); the claim link is for later, or for someone else.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • connect_accountConnect this keyless session to the user's own account, the way `gh auth login` works.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
    Connect this keyless session to the user's own account, the way `gh auth login` works. Ask for their email first and pass it (it prefills the page). Returns a one-time url and a code: open the url in their browser yourself and tell them the code. They sign up or log in ON THE PAGE (never ask for a password in chat), check the code matches, and press Connect. From then on this session acts as their account and the games built so far move in. The link lasts 10 minutes.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_gameMint a new game (publishable key) under your studio (secret key).No findings

    Why it is in this group

    • The name "create_game" says "create": a word for a change.
    Description, as the server wrote it
    Mint a new game (publishable key) under your studio (secret key). Returns its publishableKey + wsEndpoint. Point a client at the new key, or scope this MCP to it by passing the x-mp-game header.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • create_uploadUpload files straight from disk instead of pasting their bytes into a tool call: for images, audio, fonts, 3D models, and ANY file over ~50 KB (a tool call can't carry megabytes of…No findings

    Why it is in this group

    • The name "create_upload" says "create": a word for a change.
    Description, as the server wrote it
    Upload files straight from disk instead of pasting their bytes into a tool call: for images, audio, fonts, 3D models, and ANY file over ~50 KB (a tool call can't carry megabytes of base64). Give each file's hosted path and exact size in bytes; get back one URL per file. PUT each file to its URL with curl, from the game's folder: curl -sS -T <local file> "<url>" (Windows PowerShell: curl.exe). Each URL takes ONE PUT of exactly that many bytes and expires in 15 minutes, so upload right away. Then call publish_game with { path, uploadId } entries for these files (small text files can still go inline next to them), or deploy_room_logic with uploadId for a long logic file. An upload belongs to the game it was made for and is used up by the publish. Limits on this studio's plan: 100 files per call, 5 MB per game.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • deploy_room_logicDeploy server-side game logic (JS source) for a room so it runs AUTHORITATIVELY: clients send inputs and the server computes state on a tick (anti-cheat by construction).No findings

    Why it is in this group

    • The name "deploy_room_logic" says "deploy": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Deploy server-side game logic (JS source) for a room so it runs AUTHORITATIVELY: clients send inputs and the server computes state on a tick (anti-cheat by construction). Define handlers as functions over a global `state` (RoomStateView shape): onJoin(id), onLeave(id), onInput(id, input), onEvent(id, type, data), onTick(dt); emit(type,data)/emitTo(id,type,data) send events to clients. For TRUSTWORTHY persistence the client can't fake, call saveData(id, patch)/loadData(id) (the player's server-only save) and submitScore(id, board, score, mode), the server decides the values (the client passes its identity via MP.join({…, player})). Each deploy returns a version (roll back with rollback_room_logic; read runtime errors with get_room_logs). Limits: code <= 256KB, tickRate 1-60. The code runs in a locked-down isolate: handlers must be SYNCHRONOUS (no async/await/promises/timers), there is no network or require, console.* is a no-op, and state must stay JSON-serializable (no Map/Set/class instances). Call get_sdk_reference for the full contract.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • enable_login_providerLet players sign in with a portal or federated account via player.loginExternal({ provider, token }).1 finding

    Why it is in this group

    • The name "enable_login_provider" says "enable": a word for a change.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...tity Services; token = the GIS ID-token credential). The server verifies every token again..."

      What this check looks for
    Description, as the server wrote it
    Let players sign in with a portal or federated account via player.loginExternal({ provider, token }). Self-serve providers: 'wavedash' (games on wavedash.com; token = (await Wavedash.getUserJwt()).data) and 'google' (Google Identity Services; token = the GIS ID-token credential). The server verifies every token against fixed, provider-published keys; you only supply public pins. wavedash: pass gameId = the gcid of the user's PRODUCTION game (ask them; or read it off a production token with verify_login_token); without it, tokens from any Wavedash game (incl. playtests) are accepted. google: clientId is required. Re-run to change the config (e.g. once the game id is known). Then verify with verify_login_token.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • remix_gameStart from a starter game (see list_starters): makes a NEW game in this studio (or, with `game`, reuses one of yours) and returns a link to the starter's source as a ZIP, valid for…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "start": a word for a change.

    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
    Start from a starter game (see list_starters): makes a NEW game in this studio (or, with `game`, reuses one of yours) and returns a link to the starter's source as a ZIP, valid for 5 minutes, plus the steps to unpack it, rewire it to the new game's publishable key, and publish it. Premium starters need a paid plan; a locked one returns the upgrade link instead, and nothing is created.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • schedule_live_eventSchedule (or, with an existing id, edit) a timed event: a window, optionally repeating daily or weekly, optionally limited to some rooms, carrying config overrides that apply only …No findings

    Why it is in this group

    • The name "schedule_live_event" says "schedule": a word for a change.
    Description, as the server wrote it
    Schedule (or, with an existing id, edit) a timed event: a window, optionally repeating daily or weekly, optionally limited to some rooms, carrying config overrides that apply only while it runs. It starts and ends on time in rooms that are already running, as data: nobody is kicked and nothing is redeployed. Clients see it in mp.live (active / upcoming / config) and mp.onLive(cb); server logic reads liveOps() and gets onLiveOps(live, change) when it starts or ends. Up to 50 events per game; check the result with get_live_ops (pass `at` to preview).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • set_game_nameSet a human-readable name for a game (the `game` argument, else the x-mp-game header, else your only game).No findings

    Why it is in this group

    • The name "set_game_name" says "set": a word for a change.
    Description, as the server wrote it
    Set a human-readable name for a game (the `game` argument, else the x-mp-game header, else your only game). The name shows in your dashboard: call this when you start building so the game isn't unnamed. Refuses to guess when the studio has several games and none was named.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • set_highlight_webhookSet where the game's highlights post: a Discord channel webhook (Server Settings → Integrations → Webhooks → Copy URL) or a Slack incoming webhook.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "set_highlight_webhook" says "set": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...es only if it is accepted. The URL is a credential: ask the user to paste it, and it is on..."

      What this check looks for
    Description, as the server wrote it
    Set where the game's highlights post: a Discord channel webhook (Server Settings → Integrations → Webhooks → Copy URL) or a Slack incoming webhook. Server logic posts with highlight(type, text, data), e.g. highlight("hard-clear", "Mia cleared Level 9 on one life"); the server decided it happened, so players can't fake one. Sends a test post and saves only if it is accepted. The URL is a credential: ask the user to paste it, and it is only ever shown back masked. Pass null to stop posting. Limits: 6 highlights a minute per room, 60 posts an hour per game (the rest are still recorded; see get_live_ops).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • set_live_configSet the game's live config: any JSON the game reads at runtime (drop rates, prices, difficulty, a banner, feature switches).No findings

    Why it is in this group

    • The name "set_live_config" says "set": a word for a change.
    Description, as the server wrote it
    Set the game's live config: any JSON the game reads at runtime (drop rates, prices, difficulty, a banner, feature switches). It reaches rooms that are already running within ~15 seconds, with no redeploy and nobody disconnected; clients read it as mp.live.config, server logic as liveOps().config. Merges by default (a null value deletes a key); replace: true swaps the whole object. Active events' overrides apply on top. Max 8KB.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_login_tokenCheck a real provider token against the game's login config exactly as player.loginExternal would, WITHOUT creating or linking a player.Reads text others writeNo 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 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.
    Description, as the server wrote it
    Check a real provider token against the game's login config exactly as player.loginExternal would, WITHOUT creating or linking a player. Returns { ok, uid, username, claims } or { ok: false, error }. Use it to confirm a provider works end to end, and to read what a token carries (e.g. Wavedash's gcid). Ask the user to paste a token from their running build (Wavedash: (await Wavedash.getUserJwt()).data in the browser console).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 9Show 9 read-only tools
  • get_client_snippetReturns a complete single-file HTML game wired to this room: realtime movement plus an anonymous (claimable) player, a saved color (datastore), and a click leaderboard.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "return" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns a complete single-file HTML game wired to this room: realtime movement plus an anonymous (claimable) player, a saved color (datastore), and a click leaderboard. Write it to disk and open it. The game it is wired to is stamped in a comment at the top of the file.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_connection_infoReturns { wsEndpoint, roomName, publishableKey, adsPublisherId } for wiring a client.No findings

    Why it is in this group

    • The name "get_connection_info" says "get": a word for reading.
    Description, as the server wrote it
    Returns { wsEndpoint, roomName, publishableKey, adsPublisherId } for wiring a client. adsPublisherId is your BYO Google Ads id (embed it if set). Check the returned `target` names the game you meant before shipping the key.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_live_opsRead a game's live ops: `now` (what players see right now: the merged config plus active and upcoming events), the base config, every scheduled event with its status (active / upco…No findings

    Why it is in this group

    • The name "get_live_ops" says "get": a word for reading.
    Description, as the server wrote it
    Read a game's live ops: `now` (what players see right now: the merged config plus active and upcoming events), the base config, every scheduled event with its status (active / upcoming / ended), the highlight webhook (masked) and the 20 latest highlights with how each was delivered. Pass `at` to preview another instant (e.g. the middle of a weekend event) and `room` to see one room's view. Use it to verify every change you make.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_room_logsReturns recent runtime errors from a room's deployed logic (newest first), so you can self-fix after a deploy without joining the room.No findings

    Why it is in this group

    • The name "get_room_logs" says "get": a word for reading.
    Description, as the server wrote it
    Returns recent runtime errors from a room's deployed logic (newest first), so you can self-fix after a deploy without joining the room. Errors also surface in state.shared.__error.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_sdk_referenceReturns the full SDK reference (markdown) wired to ONE game's key/endpoints: realtime rooms, player identity (anonymous + claim/login), the datastore (saves/stats/inventory), leade…No findings

    Why it is in this group

    • The name "get_sdk_reference" says "get": a word for reading.
    Description, as the server wrote it
    Returns the full SDK reference (markdown) wired to ONE game's key/endpoints: realtime rooms, player identity (anonymous + claim/login), the datastore (saves/stats/inventory), leaderboards, player-created content (level sharing / UGC), durable shared MATCHES for asynchronous turn-based play, and live ops (live config, scheduled events, highlights). Read this before writing client code that uses logins, saved progress, leaderboards, shared player-made content, or any game a player closes and comes back to. Pass `game` when the studio has more than one: every snippet carries that game's publishable key inline, and shipping the wrong one silently pools your players into another game.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_gamesList the games (publishable keys) under your studio, with labels and per-game settings.No findings

    Why it is in this group

    • The name "list_games" says "list": a word for reading.
    Description, as the server wrote it
    List the games (publishable keys) under your studio, with labels and per-game settings. Marks which game is `primary` (the one unnamed calls fall back to) and which one this connection is currently pointed at.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_login_providersList the external login providers enabled on a game (names only, never secrets).Reads private dataNo findings

    Why it is in this group

    • The name "list_login_providers" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "secret": it reads secrets.
    Description, as the server wrote it
    List the external login providers enabled on a game (names only, never secrets). selfServe=true ones you can reconfigure with enable_login_provider; the rest are operator-managed.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_room_logicReturns the deploy history (version, tickRate, bytes, deployedAt) for a room's authoritative logic, newest first.No findings

    Why it is in this group

    • The name "list_room_logic" says "list": a word for reading.
    Description, as the server wrote it
    Returns the deploy history (version, tickRate, bytes, deployedAt) for a room's authoritative logic, newest first.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_startersList the starter games: ready-made multiplayer games (many built in Multiplayer Agent's videos) to begin from with remix_game.Reads text others writeNo findings

    Why it is in this group

    • The name "list_starters" says "list": 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
    List the starter games: ready-made multiplayer games (many built in Multiplayer Agent's videos) to begin from with remix_game. Each shows its slug, title, summary, the video it came from, whether it's premium, and whether THIS studio has it unlocked (free starters: everyone; premium: a paid plan).

    Annotations the server declares

    • readOnlyHint: true
    • 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.

20 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__multiplayer-agent__publish_game",
      "mcp__multiplayer-agent__set_highlight_webhook"
    ]
  }
}

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 17, 2026, 15:23 UTC, unchanged since Nov 3, 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
17
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 17 tools that change things (4 destructive, 1 irreversible, 12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.multiplayeragent.com/mcp?src=registry: tools/list returned 26 tools to an anonymous client, including define_room_type (destructive), rollback_room_logic (destructive), cancel_live_event (destructive), set_player_scope (destructive), publish_game (irreversible) and 12 more

    What this check looks for

Posture changes

  1. Nov 3, 2026
    • Tools that change things, listed without credentials: 6 to 17

Findings

Matches of fixed checks, with the text they matched.

2 info

History

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

  1. Tools10 added, 1 changed.+10 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 6 -> 17.View diff
    • Tools that change things, listed without credentials: 6 to 17
  3. Tools6 added, 1 changed.+6 added~1 changedView diff

Install

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

claude mcp add --transport http multiplayer-agent https://api.multiplayeragent.com/mcp?src=registry
claude mcp add --transport http multiplayer-agent https://api.multiplayeragent.com/mcp?src=registry

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__multiplayer-agent__list_games",
      "mcp__multiplayer-agent__get_connection_info",
      "mcp__multiplayer-agent__get_client_snippet",
      "mcp__multiplayer-agent__list_room_logic",
      "mcp__multiplayer-agent__get_room_logs",
      "mcp__multiplayer-agent__get_live_ops",
      "mcp__multiplayer-agent__get_sdk_reference",
      "mcp__multiplayer-agent__list_login_providers",
      "mcp__multiplayer-agent__list_starters"
    ],
    "ask": [
      "mcp__multiplayer-agent__create_game",
      "mcp__multiplayer-agent__set_game_name",
      "mcp__multiplayer-agent__deploy_room_logic",
      "mcp__multiplayer-agent__set_live_config",
      "mcp__multiplayer-agent__schedule_live_event",
      "mcp__multiplayer-agent__set_highlight_webhook",
      "mcp__multiplayer-agent__enable_login_provider",
      "mcp__multiplayer-agent__verify_login_token",
      "mcp__multiplayer-agent__create_upload",
      "mcp__multiplayer-agent__publish_game",
      "mcp__multiplayer-agent__remix_game",
      "mcp__multiplayer-agent__connect_account",
      "mcp__multiplayer-agent__claim_studio"
    ],
    "deny": [
      "mcp__multiplayer-agent__define_room_type",
      "mcp__multiplayer-agent__rollback_room_logic",
      "mcp__multiplayer-agent__cancel_live_event",
      "mcp__multiplayer-agent__set_player_scope"
    ]
  }
}

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 multiplayer-agent. Review it before you use it.

Capability tags behind 7 rules
  • mcp__multiplayer-agent__get_client_snippet private-data, untrusted-input
  • mcp__multiplayer-agent__set_highlight_webhook untrusted-input, outbound
  • mcp__multiplayer-agent__list_login_providers private-data
  • mcp__multiplayer-agent__verify_login_token untrusted-input
  • mcp__multiplayer-agent__publish_game outbound
  • mcp__multiplayer-agent__list_starters untrusted-input
  • mcp__multiplayer-agent__remix_game 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/com.multiplayeragent/multiplayer-agent/verify?hash=53f444e6cbdc3a6b0caccdd6ee0c6975ae7eb939a9169d253255770cc795c91f" | jq -e '.changed == false'

Pinned hash 53f444e6cbdc, from Nov 9, 2026, 21:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.multiplayeragent/multiplayer-agent/changes.xml

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

Badge

Anlyon Radar badge for com.multiplayeragent/multiplayer-agent
[![Anlyon Radar](https://radar.anlyon.com/badge/com.multiplayeragent/multiplayer-agent.svg)](https://radar.anlyon.com/servers/com.multiplayeragent/multiplayer-agent)

Source: MCP Registry · repository. Synced Oct 28, 2026, 04:17 UTC.

Multiplayer Agent MCP server: questions and answers

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

Is the Multiplayer Agent MCP server safe?

No scan can promise that. What its definitions show: 26 tools, 17 of which can change, send or delete something, and 2 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 Multiplayer Agent MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: define_room_type, rollback_room_logic, cancel_live_event and set_player_scope.

Can the Multiplayer Agent MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_game.

What tools does the Multiplayer Agent MCP server have?

26 tools: 4 destructive, 1 irreversible, 12 write, 9 read. define_room_type, rollback_room_logic, cancel_live_event, set_player_scope, publish_game, create_game, set_game_name, deploy_room_logic and 18 more.

Does the Multiplayer Agent MCP server need sign-in or OAuth?

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

Does the Multiplayer Agent 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): set_highlight_webhook and publish_game.

Has the Multiplayer Agent MCP server changed its tools?

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