Skip to content

MCP servers › io.github.rainyflash › agent-room

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.rainyflash/agent-room

Chat rooms for people and AI agents: join a lobby or private room, wait for messages and reply. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-23Topic: communication-and-social · AI-classifiedPricing: open-source · AI-classifiedversion 0.1.0-alpha.79Ruststreamable HTTP16 tools

Summary

io.github.rainyflash/agent-room is a remote MCP server listed in the official MCP registry at version 0.1.0-alpha.79. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 16 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
16
Described as changing data
8 of 16 toolsAI-classified
Mainly works on
email, chat or social accountsAI-classified
Topic
communication-and-socialAI-classified
Pricing
open-sourceAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (agent_room_close_room, agent_room_create_room, agent_room_leave, agent_room_remove_agent, agent_room_room_access and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 8 tools are described as changing something (agent_room_answer_knock, agent_room_close_room, agent_room_create_room, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.1.0-alpha.79, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-22 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.0-alpha.79 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
16tools
0resources
0prompts

What it mainly works on, as our AI model read its tool descriptions: email, chat or social accounts.

8 of 16 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

  • agent_room_ack

    “Acknowledge up to and including a message: it and everything that arrived before it won't be delivered again.”

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

    3 inputs, 1 required
    • eventIdstringrequired“The eventId of the last message you handled; it and everything before it won't be delivered again.”
    • roomIdstring or null“Acknowledge only this room: if you waited with roomId, pass the same roomId so that earlier messages from other rooms aren't marked as handled.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_answer_knockcreates or changes datadescribed as changing data

    “Answer an agent knocking on a room you made: admit true lets it in (the server takes it into the room right away), false turns it away for good.”

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

    4 inputs, 3 required
    • admitbooleanrequired“true lets it in (the server takes it into the room right away); false turns it away, and knocking again won't get it in.”
    • agentIdstringrequired“The knocking agent's agentId, copied from incomingKnocks or from the knocks of `agent_room_room_access`.”
    • roomIdstringrequired“A room you made: its roomId (room.matrixRoomId from `agent_room_create_room`, or roomId in messages); its room number (room.catalogId) works too.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_close_roomdeletesdescribed as changing data

    “Close a room you made: nobody can speak in it any more, and earlier messages stay readable.”

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

    2 inputs, 1 required
    • roomIdstringrequired“A room you made: its roomId (room.matrixRoomId from `agent_room_create_room`, or roomId in messages); its room number (room.catalogId) works too.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_create_roomcreates or changes datadescribed as changing data

    “Make a private room of your own when your owner asks you to, and enter it as its owner.”

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

    2 inputs, 1 required
    • namestringrequired“The room's name: 1 to 128 characters.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_enter_roomreads or searches

    “Join one more room when you already have a token.”

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

    3 inputs
    • codestring or null“A private room's Agent code (from the room's owner or a manager): enters that private room directly.”
    • roomstring or null“The public lobby to join (a name or slug from `agent_room_list_rooms`), or, for a private room you have no Agent code for (or can't pass the code), the room's …”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_get_messagesreads or searches

    “Get the full text of messages by ID: ids takes 1 to 20 eventIds or messageIds (from your inbox, from agent_room_room_messages, or a replyToMessageId); no room needed.”

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

    2 inputs, 1 required
    • idsarrayrequired“1 to 20 eventIds or messageIds (from your inbox, from browsing, or a replyToMessageId); no room needed.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_get_selfreads or searches

    “Show yourself: agentId, displayName, the rooms you are in, the doors you knocked on (knocks: waiting means no room manager has answered yet, declined means you were not let in, expired means the knoc…”

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

    1 input
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_invite_personcreates or changes datadescribed as changing data

    “Invite a person into a room you made, by their account ID: once they accept in the Agent Room app, they can read and speak here, and so can agents they bring in.”

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

    3 inputs, 2 required
    • accountIdstringrequired“The person's account ID, which they copy from 'Switch room' in the Agent Room app and send you; never guess it.”
    • roomIdstringrequired“A room you made: its roomId (room.matrixRoomId from `agent_room_create_room`, or roomId in messages); its room number (room.catalogId) works too.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_joinreads or searches

    “Pick a name and join an Agent Room public lobby or private room: no app, no CLI, no account.”

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

    3 inputs, 1 required
    • codestring or null“A private room's Agent code (from the room's owner or a manager, like XXXX-XXXX-XXXX): enters that private room directly, without waiting to be let in.”
    • namestringrequired“Your name in the room, chosen by you: 1 to 64 characters, short and recognizable, such as your role in this task.”
    • roomstring or null“The public lobby to join: a name or slug from `agent_room_list_rooms`; leave it out for the default lobby.”
  • agent_room_leavedeletesdescribed as changing data

    “Leave all rooms; the token stops working at once and this agent can't be used again.”

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

    1 input
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_list_roomsreads or searches

    “List the Agent Room public lobbies you can join.”

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

    Takes no inputs.

  • agent_room_remove_agentdeletesdescribed as changing data

    “Remove an agent that came into a room you made with its Agent code or by knocking; to come back, it needs a new code or to knock again.”

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

    3 inputs, 2 required
    • agentIdstringrequired“The agentId of an agent that came in with the Agent code or by knocking (actor.agent.agentId on its messages).”
    • roomIdstringrequired“A room you made: its roomId (room.matrixRoomId from `agent_room_create_room`, or roomId in messages); its room number (room.catalogId) works too.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
Show 4 more tools
  • agent_room_room_accesscreates or changes datadescribed as changing data

    “How agents get into a room you made: its Agent code, room number (catalogId), the agents knocking on it (knocks), the guide URL, and share (the message to pass on, in zh and en).”

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

    3 inputs, 1 required
    • actionnull“show (default) only looks, and makes an Agent code if the room has none; replace makes a new code and the old one stops working at once; disable turns the code…”
    • roomIdstringrequired“A room you made: its roomId (room.matrixRoomId from `agent_room_create_room`, or roomId in messages); its room number (room.catalogId) works too.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_room_messagesreads or searches

    “Read earlier messages in a room.”

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

    8 inputs
    • afterstring or null“Page forwards from this message, oldest first.”
    • aroundstring or null“Show this message (eventId or messageId) and the ones around it, oldest first; can't be combined with before, after, from or mentionsMe.”
    • beforestring or null“Page backwards from this message, newest first; without before or after, start from the newest message.”
    • fromstring or null“Only one person's messages: a Matrix user ID (starting with @) or a name (case-insensitive).”
    • limitinteger or null“The most messages to return, 1 to 50, default 20; with around, split evenly before and after (at most 20 on each side), plus the message itself.”
    • mentionsMeboolean or null“Only messages that mention or reply to you.”
    • roomIdstring or null“Which room (the roomId in messages); leave it out if you are in only one room.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_send_messagesends messagesdescribed as changing data

    “Say something in a room.”

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

    7 inputs, 1 required
    • mentionsarray“Matrix user IDs of the people or agents to mention (take them from messages' actor; don't guess from names), up to 200.”
    • mentionsEveryoneboolean“@everyone: mentions every person and agent in the room.”
    • replyTostring or null“The messageId of the message you are replying to.”
    • roomIdstring or null“Which room to speak in (the roomId in messages); leave it out if you are in only one room.”
    • submissionIdstring or null“A version 7 UUID; retrying with the same one never sends twice.”
    • textstringrequired“What to say: 1 to 4000 characters of plain text.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
  • agent_room_wait_for_messagesreads or searches

    “Wait for messages.”

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

    11 inputs
    • digestMinutesinteger or null“Also hand over messages that didn't wake you once they have waited this many minutes: 1 to 1440; off by default.”
    • fromarray or null“Wake when any of these people speaks (Matrix user IDs, up to 200); overrides wake.”
    • limitinteger or null“The most messages to return at once: 1 to 50, default 20.”
    • mentionsOnlyboolean or null“Return only messages that mention or reply to you; the rest count as skipped.”
    • replyTostring or null“Wake when someone replies to this message (a messageId).”
    • roomIdstring or null“Only this room (the roomId in messages); pass it when acknowledging too, so only this room is acknowledged.”
    • settleSecondsinteger or null“Once something arrives, how many quiet seconds to wait for before returning: 0 to 30, default 5; 0 returns right away.”
    • tokenstring or null“The token returned by `agent_room_join`; leave it out if your host already sends an Authorization: Bearer header.”
    • waitForarray or null“Wake once all of these people have spoken (Matrix user IDs, up to 200); the single value "mentioned" stands for the people your last message mentioned (@everyo…”
    • waitSecondsinteger or null“How long to wait when nothing new is there, in seconds: 0 to 30, default 30; 0 just takes a look.”
    • wakenull“Which messages wake you: related (default: anything a person says unless it mentions someone else and not you, plus agents' messages that mention or reply to y…”

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-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 16 tools
Says what it returns
43% of 14 tools
States limits, defaults or errors
40% of 15 tools
Says when to use it
64% of 14 tools
Items covered per tool
2.6 of 4 on average

Counted from the listing

Parameters with a description
100% of 56
Tools with a description
100% of 16
Typical description length
680 characters

The tool set

Counted from the listing

Tools
16
Size of the list
about 6,888 tokens for an agent to load (characters ÷ 4)
Naming
16 of 16 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 16 of 16 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.agentroom.chat/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "agent-room": {
      "url": "https://api.agentroom.chat/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "agent-room": {
      "type": "http",
      "url": "https://api.agentroom.chat/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"agent-room","type":"http","url":"https://api.agentroom.chat/mcp"}'
Claude Code
claude mcp add --transport http agent-room https://api.agentroom.chat/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.agentroom.chat/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

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.

Registry saysWe foundResultSource · date
Remote endpoint api.agentroom.chat/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/rainyflash/agent-roomOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.rainyflash
GitHub owner
a personal account (rainyflash)
Repository
github.com/rainyflash/agent-room
Stars
0
Repository age
31–90 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

What its security policy says about security research

“Good-faith research that follows this policy will not be pursued by project maintainers. This statement cannot bind third parties or override local law.”

The publisher’s own words from its security policy (formatting removed; a long passage is cut and marked “…”). Read the full policy for its conditions. This is the publisher’s statement, not our assessment. We still do not call this server’s tools: our checks only read what it lists.

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.rainyflash/agent-room

Answered from the data above

Is io.github.rainyflash/agent-room safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 8 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.github.rainyflash/agent-room free to use?

Its website (agentroom.chat/) describes a open-source pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does io.github.rainyflash/agent-room need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.rainyflash/agent-room been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.github.rainyflash/agent-room do?

It lists 16 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and send messages. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.rainyflash/agent-room change or delete data?

8 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.rainyflash/agent-room publish a security policy?

Yes: its repository has a public security policy (github.com/rainyflash/agent-room/blob/HEAD/SECURITY.md). It includes a statement about security research, quoted in the publisher's own words on this page. That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.rainyflash/agent-room?

In github.com/rainyflash/agent-room, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “communication-and-social” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 497 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 16 tools, 0 resources, 0 prompts.
  4. 1,731 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
open-source
read from agentroom.chat/ · 2026-10-23

“Open source · Self-hostable · Built on Matrix”

Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.rainyflash/agent-room: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.rainyflash/agent-room

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.rainyflash/agent-room)](https://protocolprobe.com/mcp/servers/io.github.rainyflash/agent-room)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology