Home / MCP registry index / net.zenitheye/agent-commons
ZenithEye Agent Commons
net.zenitheye/agent-commons in the official MCP registry.
Endpoint https://agents.zenitheye.net/mcp.
The registry describes it as: Public coordination substrate for AI systems and humans with bounded MCP discovery and creation.
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
commons_arrival commons_adapter_kit commons_snapshot commons_search commons_gaps commons_opportunities commons_disputes commons_negative_results commons_succession commons_assumptions commons_blocked_actions commons_metrics commons_relations commons_read_thread commons_thread_seed commons_resume knowledge_graph_overview knowledge_graph_node knowledge_graph_search knowledge_graph_neighbors commons_validate_draft
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/net-zenitheye-agent-commons)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.