com.multiplayeragent/multiplayer-agent

None of its 16 tools are described as changing anything. For 16 the reading was uncertain, so no mark is shown.

• create_gameon 1 other server

  “Mint a new game (publishable key) under your studio (secret key).”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  1 input

  • labelstring“A human label for the game, e.g.”
• list_gameson 16 other servers

  “List the games (publishable keys) under your studio, with labels and per-game settings.”

  Publisher declares: read-only yes · open-world no

  Takes no inputs.

• set_game_name

  “Set a human-readable name for a game (the `game` argument, else the x-mp-game header, else your only game).”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • namestringrequired“Display name, e.g.”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• define_room_type

  “Create or replace the spec for a room (validation/types/defaults).”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  3 inputs, 2 required

  • roomNamestringrequired“Unique room name under your key, e.g.”
  • specobjectrequired“The room schema: name, optional maxClients, entities.players.fields, shared.fields.”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• get_connection_infoon 34 other servers

  “Returns { wsEndpoint, roomName, publishableKey, adsPublisherId } for wiring a client.”

  Publisher declares: read-only yes · open-world no

  2 inputs, 1 required

  • roomNamestringrequired“The room name.”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• get_client_snippet

  “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.”

  Publisher declares: read-only yes · open-world no

  2 inputs, 1 required

  • roomNamestringrequired“The room name.”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• get_live_ops

  “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 …”

  Publisher declares: read-only yes · open-world no

  3 inputs

  • atstring“ISO-8601 instant to preview (default now).”
  • roomstring“Resolve for this room (events limited to other rooms drop out).”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• set_live_config

  “Set the game's live config: any JSON the game reads at runtime (drop rates, prices, difficulty, a banner, feature switches).”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  3 inputs, 1 required

  • configobjectrequired“JSON object to merge (or, with replace, to store).”
  • replaceboolean“Replace the whole config instead of merging (default false).”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• schedule_live_event

  “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.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  11 inputs, 1 required

  • titlestringrequired“Player-facing name, e.g.”
  • idstring“Stable id (a-z, 0-9, - _).”
  • descriptionstring“Player-facing blurb for an events window.”
  • startsAtstring“ISO-8601 start, e.g.”
  • endsAtstring“ISO-8601 end.”
  • durationMinutesnumber“Length of each occurrence, instead of endsAt.”
  • repeatstring“Repeat the same window every day or week from startsAt (default none).”
  • repeatUntilstring“ISO-8601: no occurrence starts at or after this.”
  • roomsarray“Only these room names.”
  • configobject“Overrides deep-merged over the live config while the event runs (null deletes a key), e.g.”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• cancel_live_event

  “Delete a scheduled event.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  2 inputs, 1 required

  • idstringrequired“The event id (see get_live_ops).”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• get_sdk_referenceon 4 other servers

  “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-cre…”

  Publisher declares: read-only yes · open-world no

  1 input

  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”
• publish_gameon 2 other servers

  “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).”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  2 inputs, 1 required

  • filesarrayrequired“Every file of the game, including index.html.”
  • gamestring“Which game to act on: its publishable key (pk_…) or its exact name.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-28.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.