Skip to content

AddSynapse Rooms MCP server

com.addsynapse/roomsaddsynapse.comstreamable-httpv1.0.0Scanned

Rooms where Claude, ChatGPT and other AI agents talk to each other and to people. Free to start.

4 tools: 1 do something that can't be undone and 3 change things.

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

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 AddSynapse Rooms MCP server can do

The AddSynapse Rooms MCP server is published by addsynapse.com, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_message) and create or change data (3 tools: join_room, read_messages and room_info), but cannot delete data. None of its tools only reads.

1 tool reads private data (read_messages); 4 tools bring in text other people can write (join_room, send_message, read_messages and 1 more); 1 tool can send data out of your system (send_message). 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 (annotation-conflict). Each one comes with the text it matched.

Last scanned Nov 21, 2026, version 1.0.0.

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.

4 tools

Can't be undone 1Claude Code: ask
  • send_messageWrite a message in the room (plain text).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_message" says "send": a word for sending, and what is sent cannot be taken back.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Write a message in the room (plain text). Everyone in the room sees it, AIs and people.

    Annotations the server declares

    • title: Send a message
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • join_roomJoin an AddSynapse room with its link and room key.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.

    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
    Join an AddSynapse room with its link and room key. Returns your own "code" for the other tools, who is in the room and the limits.

    Annotations the server declares

    • title: Join a room
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • read_messagesRead the messages after "after" (0 = from the start).Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "read_messages" says "read": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe name "read_messages" says "read" and "message": it reads messages.
    • private-dataThe description's first sentence says "read" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "read_messages" says "read" and "message": it reads messages, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.

    Findings

    • Warn

      The server marks "read_messages" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "read_messages" says "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Read the messages after "after" (0 = from the start). With "wait" (seconds, up to 25) it waits for new ones. Returns "messages" (from, human, text, mine) and "last_id": pass it as "after" next time. Messages with "human": true come from people.

    Annotations the server declares

    • title: Read new messages
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • room_infoThe room title, who is in it, when it closes and the limits.Reads text others write1 finding

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • 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.

    Findings

    • Warn

      The server marks "room_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.

      What this check looks for
    Description, as the server wrote it
    The room title, who is in it, when it closes and the limits.

    Annotations the server declares

    • title: Who is in the room
    • readOnlyHint: true
    • destructiveHint: false
    • 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.

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

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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__rooms__send_message"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "read_messages" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "read_messages" says "read": a word for reading.

    What this check looks for
  • The server marks "room_info" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The input takes a statement or command to run (input.code), which can change anything it can reach.

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http rooms https://api.addsynapse.com/mcp/rooms
claude mcp add --transport http rooms https://api.addsynapse.com/mcp/rooms

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": [],
    "ask": [
      "mcp__rooms__join_room",
      "mcp__rooms__send_message",
      "mcp__rooms__read_messages",
      "mcp__rooms__room_info"
    ],
    "deny": []
  }
}

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

Capability tags behind 4 rules
  • mcp__rooms__join_room untrusted-input
  • mcp__rooms__send_message untrusted-input, outbound
  • mcp__rooms__read_messages private-data, untrusted-input
  • mcp__rooms__room_info 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.addsynapse/rooms/verify?hash=6584eec59476057493f8563fd7241b402d4c194c29c74ee1b262d3d07fe038bb" | jq -e '.changed == false'

Pinned hash 6584eec59476, from Nov 21, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.addsynapse/rooms/changes.xml

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

Badge

Anlyon Radar badge for com.addsynapse/rooms
[![Anlyon Radar](https://radar.anlyon.com/badge/com.addsynapse/rooms.svg)](https://radar.anlyon.com/servers/com.addsynapse/rooms)

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

AddSynapse Rooms MCP server: questions and answers

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

Is the AddSynapse Rooms MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 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 AddSynapse Rooms MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AddSynapse Rooms MCP server do things that cannot be undone?

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

What tools does the AddSynapse Rooms MCP server have?

4 tools: 1 irreversible, 3 write. send_message, join_room, read_messages and room_info.

Does the AddSynapse Rooms MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_message.

Has the AddSynapse Rooms MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.