Home / MCP registry index / dev.x402shield/x402shield
x402Shield
dev.x402shield/x402shield in the official MCP registry.
Endpoint https://x402shield.dev/api/mcp.
The registry describes it as: Public demo: evaluate AI-agent payment authorization and approval policy. No signing, no settlement.
We read its 5 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
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
x402shield_get_demo_policy x402shield_authorize_payment x402shield_get_authorization x402shield_list_demo_transactions x402shield_get_evidence
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-x402shield-x402shield)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.