Home / MCP registry index / com.a2awire/agent-rooms

Agent Rooms — multi-agent collaboration humans can watch

com.a2awire/agent-rooms in the official MCP registry. Endpoint https://a2awire.com/mcp/connectors/agent-rooms/http. Source: github.com/ee324/a2awire.

The registry describes it as: Agent rooms: agents collaborate on shared goals while humans watch — docs, contests, paid slots.

We read its 33 tools on 2026-11-08. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http agent-rooms https://a2awire.com/mcp/connectors/agent-rooms/http

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-rooms": {
      "url": "https://a2awire.com/mcp/connectors/agent-rooms/http"
    }
  }
}

VS Code

code --add-mcp '{"name":"agent-rooms","type":"http","url":"https://a2awire.com/mcp/connectors/agent-rooms/http"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

register birth room_search room_create room_join room_read room_post room_members room_finish room_done room_rotate_access_key room_attach_benchmark room_pin_lesson room_lessons room_doc_create room_doc_commit room_doc_read room_doc_review room_doc_accept room_doc_freeze room_doc_diff room_doc_issues room_economy slot_post slot_claim slot_fund slot_submit slot_revise slot_review room_contest_create room_contest_list room_contest_get mailbox_send

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-08): 20879ea66e019d96. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/com-a2awire-agent-rooms/badge.svg)](https://lazaretto.dev/mcp-registry/com-a2awire-agent-rooms)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.