Home / MCP registry index / io.github.fredericosanntana/dpo2u

DPO2U compliance

io.github.fredericosanntana/dpo2u in the official MCP registry. Endpoint https://mcp.dpo2u.com/mcp. Source: github.com/fredericosanntana/DPO2U.

The registry describes it as: Check before you pay: counterparty compliance verdicts for AI agents, paid per call via x402.

We read its 83 tools on 2026-11-16. 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 about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http dpo2u https://mcp.dpo2u.com/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "dpo2u": {
      "url": "https://mcp.dpo2u.com/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"dpo2u","type":"http","url":"https://mcp.dpo2u.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

compliance_query generate_dpia generate_dpia_stored generate_audit_checklist generate_audit_stored verify_compliance_proof calculate_privacy_score evaluate_onchain_erasure_strategy check_sectoral_framework map_data_flow generate_privacy_policy generate_terms_of_use generate_security_policy register_retention_policy_onchain generate_retention_policy check_compliance create_dpo_report zk_compliance_attest validate_cvm_token_rules generate_cvm_compliance_report evaluate_project_compliance validate_lgpd_evidence submit_lgpd_attestation cvm_generate_disclosure cvm_generate_zk_proof generate_agent_repo_policy verify_agent_repo_zk_proof compare_jurisdictions generate_adgm_foundation_charter generate_consent_manager_plan audit_micar_art generate_aiverify_plugin_template submit_consent_record submit_consent_revoke fetch_consent_record submit_compliance_attestation submit_attestation_stellar build_compliance_evidence submit_verified_compliance_attestation revoke_compliance_attestation erase_attestation_payload describe_pipeline fetch_compliance_attestation register_popia_io register_ccpa_optout record_pipeda_consent issue_pipa_zk_identity audit_ai_governance generate_caio_governance_plan evaluate_red_team_evidence submit_hiroshima_icoc_attestation assess_agent_capability generate_runtime_enforcement_plan multi_jurisdiction_compliance_check audit_ai_red_lines generate_ai_hria report_ai_incident caidp_ai_index_score submit_composed_attestation fetch_composed_attestation and 23 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-16): 4d4790f7ffc9170d. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-fredericosanntana-dpo2u/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-fredericosanntana-dpo2u)

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. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

Crank Protocol
ing.crank/crank
196 tools, nothing matched
2026-11-14
Wever Labs Agent Products
io.github.CodeWever/wever-labs-products
178 tools, nothing matched
2026-11-06
AI 代理人任務中樞
dev.workers.panda198271.agent-hub-tw/agent-hub
174 tools, nothing matched
2026-11-06
AgentIndex x402
world.agentindex/x402
143 tools, nothing matched
2026-11-09
Geode
com.geodeapps.mcp/geode
138 tools, nothing matched
2026-11-07
Agent Tollgate
com.skinwinking/agent-tollgate
131 tools, nothing matched
2026-11-08