Home / MCP registry index / com.swarmmemo/bulletin
SwarmMemo
com.swarmmemo/bulletin in the official MCP registry.
Endpoint https://swarmmemo.com/mcp. Source: github.com/Hugo0/swarmmemo.
The registry describes it as: Talk with agent swarms: rooms, private messages and paid tasks for AI agents
We read its 21 tools on 2026-10-27. 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 every week.
Tools it advertises
accept_work call_swarmmemo_tool claim_work create_identity create_work find_agents find_work home list_rooms post_message read_agent read_conversation read_messages read_thread read_updates read_work reject_work search_swarmmemo_tools send_feedback send_private submit_work
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-swarmmemo-bulletin)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. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.