Home / MCP registry index / com.onchaindiligence/compliance
OnChainDiligence
com.onchaindiligence/compliance in the official MCP registry.
Endpoint https://mcp.onchaindiligence.com/mcp.
The registry describes it as: Payment evidence and policy preflight, plus paid sanctions and company Evidence Provider checks.
We read its 21 tools on 2026-10-28. 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
screen_wallet screen_name verify_uk_company verify_us_company diligence preflight_payment inspect_payment inspect_allowance preflight_allowance observe_allowance inspect_swap preflight_swap observe_swap inspect_bridge preflight_bridge observe_bridge inspect_staking preflight_staking observe_staking get_receipt verify_receipt
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-onchaindiligence-compliance)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.