Home / MCP registry index / dev.workers.agentwatch.agentwatch/agentwatch
AgentWatch
dev.workers.agentwatch.agentwatch/agentwatch in the official MCP registry.
Endpoint https://agentwatch.agentwatch.workers.dev/mcp.
The registry describes it as: Read-only watchtower for AI agents on-chain: decoded receipts, plan vs execution, Safe audits.
We read its 21 tools on 2026-10-22. 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
list_watched get_feed run_audit get_capabilities get_alerts get_pending_proposals get_fidelity get_leaderboard get_benchmark get_tca register_intent add_watch watch_demo_set refresh_watches get_agent_passport set_agent_passport list_recovery_owners set_recovery_owner remove_recovery_owner get_safe_defaults get_dashboard
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-workers-agentwatch-agentwatch-agentwatch)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.