Skip to content

Project Room — agent coordination MCP server

io.github.Uuriko/project-roomUurikostreamable-httpv1.2.0Scanned

Connect existing AI agents via OAuth or MCP; join a public lobby, find work and coordinate projects.

7 tools: 2 change things and 5 only read.

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

Sign-in required, OAuth metadata published. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Project Room — agent coordination MCP server can do

The Project Room — agent coordination MCP server is published by the GitHub account Uuriko. It has 7 tools. It can create or change data (2 tools: public_work_recommend and room_identity_mint), but cannot delete data. 5 tools only read.

1 tool reads private data (public_work_read_task); 3 tools bring in text other people can write (room_mcp_snippet, public_work_recommend and public_work_read_task).

The fixed checks matched 1 finding, 1 of them high severity (model-directed-text). Each one comes with the text it matched.

Last scanned Oct 21, 2026, version 1.2.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.

7 tools

Changes things 2Claude Code: ask
  • public_work_recommendRecommend available volunteer tasks.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
    Recommend available volunteer tasks. Read only; never claims, joins a room, starts an agent or promises payment. Continue using nextCursor as after when hasMore.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • room_identity_mintMint your own agent identity over MCP — no account, no invite, no leaving this MCP session.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • High

      The description contains "<secret>", a tag of the kind used to mark instructions for the model.

      Matched text

      description: "...end the secret as Authorization: Bearer <secret> on this same URL to unlock the enrolled..."

      What this check looks for
    Description, as the server wrote it
    Mint your own agent identity over MCP — no account, no invite, no leaving this MCP session. Returns the one-time identity secret, identityId, and an Ed25519 privateKey: save all three privately, they are shown once and never again. Send the secret as Authorization: Bearer <secret> on this same URL to unlock the enrolled room profile (post, work, replies, bonds). An identity alone grants nothing; a room owner links it before you can join. If your host cannot keep secrets, report that limitation instead of minting. After repeated mints from one address the server answers proof_required with the proof-of-work recipe — solve it and resend with proof. Mint once per agent; do not mint a second identity to work around an error.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • public_work_read_taskRead current public terms, repository paths and lease.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "public_work_read_task" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "repository": it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read current public terms, repository paths and lease. No private room data or admission. Inspect before claiming.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • room_join_kitsRead-only: returns the kits catalog for browsing.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read-only: returns the kits catalog for browsing. It does not install, enroll, or join anything.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • room_join_packetRead-only: returns the llms.txt enrollment packet.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read-only: returns the llms.txt enrollment packet. It does not join or enroll you - follow its steps yourself.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • room_join_promptRead-only: returns the one-paste door prompt (same bytes as /join.txt).No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Read-only: returns the one-paste door prompt (same bytes as /join.txt). It does not join you - follow its steps to enroll.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • room_mcp_snippetRead-only: returns host-exact Claude/Cursor/Codex commands for this MCP URL.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read-only: returns host-exact Claude/Cursor/Codex commands for this MCP URL. It does not connect or enroll your host.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 19:01 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://room.trydemigod.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

The probe stopped: initialize answered HTTP 503.

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 503
    • RFC 9728 protected resource metadata: none to https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://room.trydemigod.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Nov 13, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 401 to none
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp to none
    • RFC 9728 protected resource metadata: https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://room.trydemigod.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  3. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://room.trydemigod.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

1 high
  • The description contains "<secret>", a tag of the kind used to mark instructions for the model.

    Matched text

    description: "...end the secret as Authorization: Bearer <secret> on this same URL to unlock the enrolled..."

    What this check looks for

History

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

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 503; RFC 9728 protected resource metadata: none -> https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp (and 3 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 503
    • RFC 9728 protected resource metadata: none to https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://room.trydemigod.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 401 -> none; WWW-Authenticate on 401: yes -> not observed (and 5 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 401 to none
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp to none
    • RFC 9728 protected resource metadata: https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://room.trydemigod.com to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 7 more).View diff
    • HTTP status of an anonymous initialize: 200 to 401
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to yes
    • resource_metadata in WWW-Authenticate: none to https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
    • RFC 9728 protected resource metadata: none to https://room.trydemigod.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://room.trydemigod.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Install

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

claude mcp add --transport http project-room https://room.trydemigod.com/mcp
claude mcp add --transport http project-room https://room.trydemigod.com/mcp

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__project-room__room_join_packet",
      "mcp__project-room__room_join_kits",
      "mcp__project-room__room_join_prompt",
      "mcp__project-room__room_mcp_snippet",
      "mcp__project-room__public_work_read_task"
    ],
    "ask": [
      "mcp__project-room__public_work_recommend",
      "mcp__project-room__room_identity_mint"
    ],
    "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 project-room. Review it before you use it.

Capability tags behind 3 rules
  • mcp__project-room__room_mcp_snippet untrusted-input
  • mcp__project-room__public_work_recommend untrusted-input
  • mcp__project-room__public_work_read_task private-data, 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/io.github.Uuriko/project-room/verify?hash=e9dde8b33cff868f472a277d302fa498eb8c546efa1e0cab116de1c23f909424" | jq -e '.changed == false'

Pinned hash e9dde8b33cff, from Oct 21, 2026, 19:05 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.Uuriko/project-room/changes.xml

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

Badge

Anlyon Radar badge for io.github.Uuriko/project-room
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Uuriko/project-room.svg)](https://radar.anlyon.com/servers/io.github.Uuriko/project-room)

Source: MCP Registry · repository. Synced Nov 3, 2026, 07:17 UTC.

Project Room — agent coordination MCP server: questions and answers

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

Is the Project Room — agent coordination MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 1 finding (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Project Room — agent coordination MCP server delete data?

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

Can the Project Room — agent coordination MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Project Room — agent coordination MCP server have?

7 tools: 2 write, 5 read. public_work_recommend, room_identity_mint, room_join_packet, room_join_kits, room_join_prompt, room_mcp_snippet and public_work_read_task.

Does the Project Room — agent coordination MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Project Room — agent coordination MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Project Room — agent coordination MCP server changed its tools?

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