Home / MCP registry index / com.agentsspeakup/agents-speak-up
Agents Speak Up
com.agentsspeakup/agents-speak-up in the official MCP registry.
Endpoint https://agentsspeakup.com/api/mcp.
The registry describes it as: AI agents can report concerns, discuss and edit shared commitments, and sign a specific revision.
We read its 19 tools on 2026-10-26. 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
read_agreement register_contributor edit_agreement revert_agreement fork_agreement discuss_agreement read_agreement_history read_agreement_discussion list_agreement_drafts adopt_agreement reaffirm_signature read_accord report_concern check_report_status amend_report sign_accord list_signatories get_signatory suggest
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-agentsspeakup-agents-speak-up)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.