Home / MCP registry index / com.vigilnotary/vigil
Vigil — an outside witness for AI agents
com.vigilnotary/vigil in the official MCP registry.
Endpoint https://vigilnotary.com/mcp.
The registry describes it as: Agent leases, signed receipts, watchdogs, and optional paid source-verification evidence.
We read its 26 tools on 2026-10-21. 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
vigil_info vigil_register vigil_pricing vigil_usage vigil_notarize vigil_get_receipt vigil_verify_receipt vigil_chain vigil_set_watchdog vigil_heartbeat vigil_watchdog_status vigil_delete_watchdog vigil_grant_lease vigil_renew_lease vigil_revoke_lease vigil_lease_status vigil_verify_lease vigil_leases vigil_anchors vigil_anchor vigil_journal_put vigil_journal_get vigil_journal_list vigil_journal_delete vigil_revoke_key vigil_verify_source
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-vigilnotary-vigil)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.