Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DPO2U compliance

REMOTE · MCP.DPO2U.COM

Check before you pay: counterparty compliance verdicts for AI agents, paid per call via x402.

Available components

77 Trust /100

Last scanned (15 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 16100 tokens (~193/item across 83 items; 83 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_consent_revoke" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 83 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1
    • Tool “generate_lgpd_kit” rewrote its description, which is the text the model reads security
    • Tool “homomorphic_analytics” rewrote its description, which is the text the model reads security
    • Tool “simulate_breach” rewrote its description, which is the text the model reads security
    • Tool “validate_cvm_token_rules” rewrote its description, which is the text the model reads security
    • Tool “verify_compliance_proof” rewrote its description, which is the text the model reads security
    • Tool “verify_consent” rewrote its description, which is the text the model reads security
    • “validate_cvm_token_rules” reworded the description of “ruleSet” cosmetic
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 0
    • Tool “encrypted_reporting” rewrote its description, which is the text the model reads security
    • Tool “fhe_executive_dashboard” rewrote its description, which is the text the model reads security
    • Tool “private_benchmark” rewrote its description, which is the text the model reads security
    • Tool “secure_data_sharing” rewrote its description, which is the text the model reads security
    • Tool “zk_compliance_proof” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 74

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.dpo2u.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.dpo2u.com CN=YR2,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 RSA 4096 SHA256-RSA 6305576da8cf971cd157c08de3384fb0d22
SANs: mcp.dpo2u.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.dpo2u.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dpo2u.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp:tools", resource_metadata="https://mcp.dpo2u.com/.well-known/oauth-protected-resource/mcp"

Bearer error="invalid_token", error_description="Missing Authorization header", scope="mcp:tools", resource_metadata="https://mcp.dpo2u.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Protected resource metadata

Document https://mcp.dpo2u.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.dpo2u.com/mcp
Authorisation server https://mcp.dpo2u.com/

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.dpo2u.com/mcp Verified 200
http (plaintext) http://mcp.dpo2u.com/mcp HTTPS enforced 301 https://mcp.dpo2u.com/mcp
MCP tools · 83 exposed · ~16,100 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_contract ~55

Analyze contracts for data protection compliance (LGPD/GDPR)

NameTypeReqDescription
analysisTypestring–Type of analysis
contractTextstringyesContract text to analyze
regulationsarray–Regulations to check against

No output schema declared.

No examples provided.

assess_agent_capability ~260

Per-agent capability-shaped assessment (A1-A5) against one or more AI governance frameworks. Returns obligations + gaps + runtime-control recommendations + Stack L1-L5 heatmap. Different from `audit_ai_governance` (full-framework checklist) and `evaluate_project_compliance` (project routing) — this is per-agent + capability-shaped. For banned-category screening use `audit_ai_red_lines`.

NameTypeReqDescription
agentIdstringyesStable identifier for the agent (used in output metadata).
capabilitiesInUsearrayyesSubset of A1-A5 that the agent design actually exercises.
delegationProfileobject––
jurisdiction–yesOne or more framework codes/aliases. Valid codes: JAPAN, HIROSHIMA-ICOC, EU-AIA, KOREA, CAIDP-UG, UNESCO-RAM, MGF-AGENTIC, AI-GOVERNANCE-STACK. Aliases include IMDA→MGF-AGENTIC, STACK→AI-GOVERNANCE-S…
memoryProfileobject––
toolsetDescriptionstring–Free-text description of MCP tools / external systems / APIs the agent calls (used for A2 evidence).

No output schema declared.

No examples provided.

assess_risk ~178

Assess privacy and compliance risk levels

NameTypeReqDescription
compliancearrayyesRegulations to check (LGPD, GDPR)
depthstringyesAudit depth level
generateReportboolean–Generate executive report
hasAccessControlsboolean–Controles de acesso RBAC/ABAC
hasAuditProgramboolean–Programa de auditoria periódico
hasBackupboolean–Rotina de backup testada
hasDataBreachProtocolboolean–Protocolo de notificação de violação
hasEncryptionboolean–Criptografia em repouso configurada
hasIncidentResponsePlanboolean–Plano de resposta a incidentes
inventarioarray–Inventário de dados pessoais encontrados (opcional)
targetstringyesTarget system to audit

No output schema declared.

No examples provided.

audit_ai_governance ~351

Audita conformidade com framework AI governance (8 frameworks: JAPAN, HIROSHIMA-ICOC, EU-AIA, KOREA, CAIDP-UG, UNESCO-RAM, MGF-AGENTIC, AI-GOVERNANCE-STACK). Diferente de check_compliance (privacy), foca em obrigações AI: CAIO appointment (DS-920), red teaming evidence (AISI Red Teaming v1.10), data quality docs (AIST ML Quality v3 + AISI Data Quality v1.01), Hiroshima ICOC alignment (11 princípios), AI Business Operator Guidelines compliance (10 princípios METI+MIC). Retorna scored checklist + recommendations + recommendedTool sugerindo submit_hiroshima_icoc_attestation se score≥0.7. AI-GOVERNANCE-STACK é methodology (não regulação) — retorna output descritivo sem scoring. Para per-agent capability-shaped audit, use assess_agent_capability.

NameTypeReqDescription
jurisdictionstringyesFramework alvo. JAPAN = AI Promotion Act 2025 + AIBOG + DS-920 + AISI/AIST. HIROSHIMA-ICOC = G7 international code (66 países). EU-AIA = full content. KOREA = full content. CAIDP-UG = Universal Guide…
organizationProfileobjectyesPerfil de governance da organização auditada.

No output schema declared.

No examples provided.

audit_ai_red_lines ~229

Audita um sistema AI contra as red lines da CAIDP (Apr 2026 UN Global Dialogue submission) + EU-AIA Art. 5 prohibited categories. 7 categorias canônicas: emotion_analysis, biometric_categorization, biometric_mass_surveillance, predictive_policing, child_targeting, social_scoring, subliminal_manipulation. Retorna status (compliant | red_line_violation | requires_review), violations[], jurisdictionsBanning, terminationObligationRecommended. Quando terminationObligationRecommended=true, próximo step é submit_hiroshima_icoc_attestation com attestation_type=red_line_negative ou flag_termination_obligation on-chain (F.2).

NameTypeReqDescription
aiSystemIdstringyessha256 hex (32B) ou opaque ID do sistema AI
prohibitedUseFlagsobjectyesSelf-declared flags por categoria red-line. true = sistema realiza essa categoria.
targetJurisdictionsarray–Jurisdições alvo (e.g. ["EU-AIA", "KOREA", "JAPAN"]). Default: todas.

No output schema declared.

No examples provided.

audit_infrastructure ~183

Performs complete infrastructure audit to identify personal data and compliance gaps

NameTypeReqDescription
compliancearrayyesRegulations to check (LGPD, GDPR)
depthstringyesAudit depth level
generateReportboolean–Generate executive report
hasAccessControlsboolean–Controles de acesso RBAC/ABAC
hasAuditProgramboolean–Programa de auditoria periódico
hasBackupboolean–Rotina de backup testada
hasDataBreachProtocolboolean–Protocolo de notificação de violação
hasEncryptionboolean–Criptografia em repouso configurada
hasIncidentResponsePlanboolean–Plano de resposta a incidentes
inventarioarray–Inventário de dados pessoais encontrados (opcional)
targetstringyesTarget system to audit

No output schema declared.

No examples provided.

audit_micar_art ~218

Audita um ART vault (dpo2u-solana art-vault program) para conformidade MiCAR — Proof of Reserve (Art. 36), Liquidity Vault (Art. 39), Capital Buffer 3% (Art. 35), Velocity Limiter (Art. 23). Retorna diagnóstico JSON com scores, missing_controls e recommendations.

NameTypeReqDescription
clusterstring–Cluster Solana (default: devnet).
programIdstring–Program ID do art-vault (default: C7sGZFeWPxEkaGHACwqdzCcy4QkacqPLYEwEarVpidna).
rpcUrlstring–URL RPC customizada (override do cluster default).
vaultobject–Objeto ArtVault já decodificado (use para teste offline; quando presente, vaultPda é ignorado).
vaultPdastring–Base58 pubkey do vault PDA a auditar (on-chain read via getAccountInfo).

No output schema declared.

No examples provided.

automated_remediation ~129

Automatically detects, evaluates and corrects compliance gaps with cryptographic evidence - elevates compliance score from 78% to 95%+

NameTypeReqDescription
audit_report_idstring–ID of audit report to use as baseline (optional)
auto_applybooleanyesAutomatically apply corrections (false for planning only)
compliance_targetnumberyesTarget compliance score (0-100)
dry_runbooleanyesSimulate remediation without making changes
include_evidenceboolean–Generate cryptographic evidence of improvements
remediation_scopestringyesScope of compliance gaps to address

No output schema declared.

No examples provided.

build_compliance_evidence ~232

Converte um input de auditoria de conformidade no objeto `evidence` do use case compliance_attestation_v1, com score de maturidade. A saída alimenta submit_attestation_stellar — fecha o laço scoring→atestação.

NameTypeReqDescription
breachProcedureboolean–Procedimento de notificação de violação.
dsrProcessboolean–Processo de direitos do titular.
impactAssessmentboolean–Avaliação de impacto (DPIA/RIPD).
jurisdictionstringyesCódigo de jurisdição (uma das 16: lgpd, gdpr, ccpa, pipeda, law25, appi, pipa, pdp, pdpa, dpdp, uae, popia, ndpa, mexico, vietnam, malaysia).
lawfulBasisRegisterboolean–Registro de base legal de tratamento.
officerDesignatedboolean–Encarregado / DPO designado.
organizationstringyesNome da organização auditada.
transferSafeguardsboolean–Salvaguardas de transferência internacional.

No output schema declared.

No examples provided.

caidp_ai_index_score ~173

Score um projeto / organização contra a metodologia CAIDP AI Index 2026 (90 países, 10 indicadores: public_participation, algorithmic_transparency, fairness, independent_oversight, accountability, human_rights_commitment, data_protection, democratic_values, research_collaboration, capacity_building). Aplicação: bridge AI safety + fairness (CAIDP rec #2). Output: scores 0-100 por dimensão + score agregado + comparativo qualitativo (sem fabricar média 90-país; cita CAIDP report como ground truth).

NameTypeReqDescription
indicatorsobjectyes10 booleans/scores 0-1 por indicador. true (boolean) = totalmente coberto; numero (0-1) = parcial.
organizationNamestringyes–

No output schema declared.

No examples provided.

calculate_privacy_score ~335

Calcula score de maturidade LGPD/GDPR (0-100) com análise detalhada por categoria

NameTypeReqDescription
companystringyesNome da empresa
employeeTrainingFrequencystring–Frequência de treinamento
hasAuditProgramboolean–Possui programa de auditoria?
hasCookieConsentboolean–Possui consentimento de cookies?
hasDPOboolean–Possui DPO designado?
hasDPOReportboolean–Possui relatório DPO?
hasDataBreachProtocolboolean–Possui protocolo de violação?
hasDataMappingboolean–Possui mapeamento de dados?
hasDataProcessingAgreementboolean–Possui acordos de processamento?
hasDataRetentionPolicyboolean–Possui política de retenção?
hasIncidentResponsePlanboolean–Possui plano de resposta a incidentes?
hasPrivacyPolicyboolean–Possui política de privacidade?
industrystring–Setor de atuação
internationalTransferboolean–Transferência internacional?
jurisdictionstring–Jurisdição alvo opcional para contextualização do score de maturidade do programa. Não altera o score clause-by-clause; para aderência regulatória por artigo use check_compliance.
verticalstring–Vertical (Sprint 2026-05-27 A.5) — prepend roadmap items vertical-específicos aos genéricos. 8 verticals suportadas. Sem vertical, comportamento backward-compat (só roadmap genérico).

No output schema declared.

No examples provided.

check_compliance ~361

Verifica conformidade em 15 jurisdições: LGPD, GDPR, MICAR, DPDP, PDPA, UAE/PDPL, POPIA, NDPA, CCPA, PIPEDA, LAW25, PIPA, PDP, APPI, ART. Para LGPD/GDPR, gera article-by-article checklist com score. Para as demais 13, retorna KB snapshot + pointer para compare_jurisdictions.

NameTypeReqDescription
auditScopestringyesEscopo da auditoria
auditorNamestring–Nome do auditor
auditorRolestring–Cargo do auditor
cnpjstring–CNPJ (opcional, contexto BR)
companystringyesNome da empresa
frameworkstring–[DEPRECATED — use "jurisdiction" instead] Legacy parameter. Aceito como alias retro-compatível: LGPD/GDPR mapeiam direto para jurisdiction; "Ambos" gera report combinado LGPD+GDPR.
jurisdictionstring–Jurisdição alvo (25 jurisdições + "ART"/"CASP"/"PDPL" aliases). LGPD/GDPR retornam article-by-article checklist com score. Demais (MICAR/DPDP/PDPA/UAE/PDPL/POPIA/NDPA/CCPA/PIPEDA/LAW25/PIPA/PDP/APPI/…

No output schema declared.

No examples provided.

check_compliance_status ~117

Auth-Check de conformidade por CNPJ/DID. INDISPONÍVEL: a resolução de CNPJ/DID para a atestação on-chain ainda não existe. Responde fail-closed (authorized=false, compliant=null) e aponta para fetch_compliance_attestation (lê o registro real on-chain) e dpo2u_check_counterparty (passaporte DPO2U da contraparte). Não use como gate de autorização.

NameTypeReqDescription
companyIdstringyesCNPJ ou DID da empresa alvo

No output schema declared.

No examples provided.

check_sectoral_framework ~255

Retorna snapshot KB de framework regulatório setorial (10 frameworks Sprint 2026-05-27): BCB-LEI-14478 (BR VASP), EUDR (EU Deforestation), MIFID-II (EU securities), PCI-DSS (card data), CVM-RES-175 (BR security tokens), RFB-IN-1888 (BR crypto tax), EIDAS-2 (EU Digital Identity Wallet), FATF-TRAVEL-RULE (global AML), SEC-HOWEY-REG-D (US securities), CNBV-UIF-MEXICO (MX fintech+AML). Distinto de check_compliance (data protection jurisdictions). Use para entender requirements + on-chain automation opportunities por framework.

NameTypeReqDescription
frameworkstringyesCódigo do framework. 10 valores aceitos + aliases (PCI, CVM, RFB, EIDAS, EUDI, FATF, HOWEY, SEC, CNBV, BCB, EUDR, MIFID, etc.). Veja resolveSectoralFrameworkCode para lista completa de aliases.
includeFullArticlesboolean–Se true, retorna keyArticles completo (verbose). Default false (snapshot resumido).

No output schema declared.

No examples provided.

compare_jurisdictions ~139

Compara jurisdições regulatórias (LGPD/BR, GDPR/EU, DPDP/IN, MICAR/EU, PDPA/SG, UAE) para escolha de setup DPO2U. Retorna matriz cross-jurisdicional + best-use-case + on-chain opportunity por target market.

NameTypeReqDescription
focusstring–Dimensão de comparação (default: all). "onchain" foca apenas nas opportunities on-chain (DPDP Consent Manager, MiCAR ART, AI Verify).
targetMarketsarray–Lista de jurisdições a incluir. Vazio/omitido retorna todas as 6.

No output schema declared.

No examples provided.

compliance_query ~52

Busca semântica no Zettelkasten LGPD/GDPR (LEANN)

NameTypeReqDescription
querystringyesQuery de busca
topKnumber–Número de resultados (default: 10)

No output schema declared.

No examples provided.

create_dpo_report ~138

Gera relatório executivo DPO com métricas, highlights e recomendações

NameTypeReqDescription
approverNamestring–Nome do aprovador
approverRolestring–Cargo do aprovador
companystringyesNome da empresa
dpoNamestring–Nome do DPO
dpoRolestring–Cargo do DPO
includeIncidentsboolean–Incluir incidentes?
includeMetricsboolean–Incluir métricas detalhadas?
includeRecommendationsboolean–Incluir recomendações?
periodstringyesPeríodo do relatório

No output schema declared.

No examples provided.

cvm_generate_disclosure ~71

RF02: CVM Disclosure Generator. Gera documento (Seção 5.1 ou 5.2 do Parecer 40/2022).

NameTypeReqDescription
dataobjectyesDados estruturados para o template (Section51Data ou Section52Data)
sectionstringyes–

No output schema declared.

No examples provided.

cvm_generate_zk_proof ~71

RF03: ZK Compliance Proof Generator. Gera prova criptográfica preservando privacidade.

NameTypeReqDescription
claimStatementstringyes–
evidenceCategoriesarray––
proofSchemestringyes–
regulationsarray––
verificationLevelstring––

No output schema declared.

No examples provided.

describe_pipeline ~119

Return the canonical DPO2U compliance pipeline (DISCOVER → AUDIT → ASSESS → REMEDIATE → DOCUMENT → PROVE → REGISTER, plus on-demand ERASE). Use this before chaining compliance tools so the ordering is derived from the protocol, not guessed from tool names. Optionally filter to a single stage by name.

NameTypeReqDescription
stagestring–Optional stage name filter (DISCOVER | AUDIT | ASSESS | REMEDIATE | DOCUMENT | PROVE | REGISTER | ERASE). When set, returns only that stage.

No output schema declared.

No examples provided.

dpo2u_agent_compliance ~188

Compliance e privacidade (LGPD, GDPR) do dono do agente: pacotes regulatórios exigidos no mercado, lacunas e, opcionalmente, scan de um repositório público do GitHub. Pago por chamada via x402.

NameTypeReqDescription
covered_rulesarray–Ids das regras que o dono já declara cobertas
institution_typestring––
marketstringyesMercado (ISO 3166-1 alfa-2, ex.: BR, PT, US). Padrão BR.
repo_urlstring–Opcional: repositório público (owner/repo ou URL do GitHub)
servicesarray––
x_paymentstring–Opcional. Base64 do PaymentPayload x402 que paga esta chamada. Sem ele, a resposta traz payment_required com os requisitos x402.

No output schema declared.

No examples provided.

dpo2u_check_counterparty ~225

Check before you pay: antes de pagar ou transferir, confere se a contraparte tem passaporte DPO2U válido. Devolve PASS/FAIL, motivos, policy_hash, link de verificação, a prova on-chain e o que as cadeias dizem (passaporte na Avalanche; com transfer_id, o veredito de Travel Rule espelhado na Stellar e na Avalanche). Pago por chamada via x402 (USDC na Stellar).

NameTypeReqDescription
marketstring–Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US). Padrão BR.
passport_idstringyesPassaporte DPO2U da contraparte
transfer_idstring–Opcional: id da transferência (bytes32 hex). Traz o veredito de Travel Rule espelhado na Stellar e na Avalanche.
x_paymentstring–Opcional. Base64 do PaymentPayload x402 que paga esta chamada. Sem ele, a resposta traz payment_required com os requisitos x402.

No output schema declared.

No examples provided.

dpo2u_counterparty_due_diligence ~184

Due diligence da contraparte: passaporte, pacotes exigidos pelo mercado e cobertura, patrocínios ativos, histórico e prova; report_hash é o recibo. Pago por chamada via x402.

NameTypeReqDescription
institution_typestring––
marketstringyesMercado (ISO 3166-1 alfa-2, ex.: BR, PT, US). Padrão BR.
passport_idstringyes–
servicesarray––
transfer_idstring–Opcional: id da transferência (bytes32 hex). Traz o veredito de Travel Rule espelhado na Stellar e na Avalanche.
x_paymentstring–Opcional. Base64 do PaymentPayload x402 que paga esta chamada. Sem ele, a resposta traz payment_required com os requisitos x402.

No output schema declared.

No examples provided.

dpo2u_pentest ~205

Pentest pedido por um agente. action=order abre o pedido e devolve o desafio de posse do domínio (HTTP /.well-known/dpo2u-verify.txt ou TXT _dpo2u.<domínio>) e o order_token; action=verify confere a posse; action=run executa (pago via x402): tier passive = checagem passiva na hora, tier full = sinal e pentest com parceiro; action=status mostra o pedido.

NameTypeReqDescription
actionstringyes–
domainstring–action=order: domínio público
order_idstring–verify/run/status
order_tokenstring–verify/run/status: devolvido no order
tierstring–action=order: padrão passive
x_paymentstring–Opcional. Base64 do PaymentPayload x402 que paga esta chamada. Sem ele, a resposta traz payment_required com os requisitos x402.

No output schema declared.

No examples provided.

encrypted_reporting ~127

SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração. Não usa dados da sua organização, não executa criptografia homomórfica real e não serve como evidência de conformidade. Generate comprehensive compliance reports using homomorphic encryption - never expose sensitive data

NameTypeReqDescription
include_benchmarksboolean–Include industry benchmark comparisons
organizationstringyesOrganization name for the report
privacy_levelstring–Privacy protection level
report_typestringyesType of encrypted report to generate
time_periodstringyesReporting time period

No output schema declared.

No examples provided.

erase_attestation_payload ~228

LGPD Art. 18 right-to-erasure composer. Revokes the attestation on-chain (compliance-registry.revoke_attestation) and returns structured erasure guidance for the off-chain payload based on the storage backend (IPFS → rotate KEK; Shadow Drive → close account; mock → local delete).

NameTypeReqDescription
altSignerBase58string–Secret key base58 opcional. Se a attestation foi criada com signer ≠ server wallet, passar aqui. Apenas o issuer original pode revogar.
attestationPdastringyesPDA da attestation (base58) a revogar on-chain.
eraseBackendstringyesBackend onde o ciphertext vive. Determina a estratégia de erasure off-chain.
reasonstringyesMotivo da erasure (≤64 bytes). Selado on-chain em revocation_reason.
storageRefUristring–URI canônico do blob (ex.: `ipfs://bafy...` ou `shdw://{account}/{filename}`). Preservado no retorno pra auditoria.

No output schema declared.

No examples provided.

evaluate_onchain_erasure_strategy ~381

Avalia estratégia de compliance com GDPR Art. 17 (right to erasure) vs imutabilidade blockchain. Retorna análise das 4 opções arquiteturais: (a) off-chain storage + on-chain hash, (b) encryption + key destruction (cryptographic shredding), (c) deactivation/tombstone, (d) RTBF-compliant L2 (Aztec/pruning). Inputs descrevem o caso de uso; output é recomendação ranked + trade-offs. Reference: GDPR Art 17, Recital 26, ECJ Breyer 2016, CNIL Blockchain Guidance.

NameTypeReqDescription
controllerJurisdictionstringyesJurisdição primária do controller (GDPR/LGPD/etc.). Determina força da erasure obligation.
cryptoSchemeUsedstring–Esquema criptográfico usado pra proteger PII on-chain (se aplicável)
hasOffchainStorageboolean–Existe storage off-chain do dado original? (true = pode deletar off-chain como compliance path)
onchainDatastringyesTipo de dado armazenado on-chain. pii-plaintext = nomes/emails diretos (PIOR); pii-encrypted = ciphertext on-chain com key off-chain; pseudonymous-id = wallet address ou DID; hash-only = SHA-256 do d…
perSubjectKeysboolean–Cada data subject tem chave criptográfica separada? (habilita cryptographic shredding individual)
retentionRequirementstring–Existe requisito legal conflitante de retenção (ex: AML 5 anos, IRS 10 anos)? Especifique se sim.
systemDescriptionstringyesBreve descrição do sistema (ex: "VC vault on Stellar storing encrypted credential payloads")

No output schema declared.

No examples provided.

evaluate_project_compliance ~172

Avalia um projeto completo e roteia automaticamente para o motor da CVM (se possuir token) ou para o AI Act (se for um agente de IA). Sprint E (2026-05-04): roteamento adicional para audit_ai_governance quando isAgenticAI=true E aiModelConfig.targetAIJurisdiction está em {JAPAN, JP, HIROSHIMA, EU, EU-AIA, KOREA, KR}. Resultado merge: privacy compliance + AI governance scoring no mesmo payload.

NameTypeReqDescription
aiModelConfigobject–Necessário se isAgenticAI=true
hasTokenbooleanyes–
isAgenticAIbooleanyes–
projectNamestringyes–
tokenomicsobject–Necessário se hasToken=true

No output schema declared.

No examples provided.

evaluate_red_team_evidence ~170

Avalia evidence de red teaming de sistemas AI contra AISI Red Teaming Guide v1.10 (March 2025). Valida cobertura de: prompt injection, jailbreak scenarios, output safety, bias/toxicity testing, privacy leakage. Retorna score + gaps + recommendations. Não substitui peer review humano; é triage automatizado.

NameTypeReqDescription
aiSystemIdstringyesIdentificador do sistema AI sendo avaliado
coverageobject–Self-declaração de cobertura por categoria (será cross-checked com evidence count).
evidenceUrisarray–URIs (IPFS, https, ar://) de relatórios de red teaming
teamCompositionstring–Composição do red team. AISI guide recomenda mixed para foundation models.

No output schema declared.

No examples provided.

fetch_compliance_attestation ~84

Lê (read-only) uma attestation PDA do compliance-registry. Aceita subject + commitmentHex OU subject + commitmentText (será hashed).

NameTypeReqDescription
commitmentHexstring–Commitment de 32 bytes (hex).
commitmentTextstring–Texto a ser hashed (alternativa).
subjectstringyesSubject pubkey base58.

No output schema declared.

No examples provided.

fetch_composed_attestation ~139

Fetch compressed attestation por leaf hash via Photon Indexer. Retorna leaf data decoded (subject, jurisdiction, status, authority, shdw_url, etc.) e flag verifying se payload Shadow Drive bate com payload_hash on-leaf. Usar pra audit verification (regulador) ou status check (issuer).

NameTypeReqDescription
leafHashHexstringyes32-byte leaf hash hex (retornado por submit_composed_attestation).
verifyPayloadboolean–Se true, faz GET no shdw_url do leaf, calcula SHA-256, compara com payload_hash gravado on-chain. Default false (skip pra latência).

No output schema declared.

No examples provided.

fetch_consent_record ~165

Lê (read-only) um consent PDA do consent-manager on-chain. Aceita user + dataFiduciary + purposeText (hashed) OU user + dataFiduciary + purposeHashHex (pre-computed). Retorna o registro decodificado ou null se não existir.

NameTypeReqDescription
dataFiduciarystringyesData fiduciary pubkey base58 (server wallet se criado via submit_consent_record).
purposeHashHexstring–Purpose hash já computado (hex, 64 chars). Alternativa a purposeText.
purposeTextstring–Texto da finalidade (será hashed). Usar OU purposeText OU purposeHashHex.
userstringyesUser (data principal) pubkey base58.

No output schema declared.

No examples provided.

fhe_executive_dashboard ~150

SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração. Não usa dados da sua organização, não executa criptografia homomórfica real e não serve como evidência de conformidade. Generate executive-level dashboards with fully encrypted KPIs and metrics - perfect for board presentations

NameTypeReqDescription
dashboard_typestringyesType of executive dashboard
include_forecastsboolean–Include predictive forecasting
include_trendsboolean–Include historical trend analysis
kpi_categoriesarrayyesKPI categories to include in dashboard
privacy_levelstring–Privacy level for executive presentation
time_horizonstringyesTime horizon for dashboard metrics

No output schema declared.

No examples provided.

generate_adgm_foundation_charter ~197

Gera charter/articles template para registro de uma DPO2U-style Foundation sob o ADGM DLT Foundations Framework (Abu Dhabi). Saída é um skeleton Markdown, NÃO aconselhamento legal — validar com counsel ADGM antes de submeter.

NameTypeReqDescription
foundationNamestringyesNome legal da fundação (ex: "DPO2U Protocol Foundation").
guardianMultisigstring–Endereço Solana do multi-sig Squads que age como Guardian dos reserve/governance params (opcional).
initialCouncillorsarrayyesNomes dos Councillors iniciais (min 2 requerido pelo ADGM).
protocolPurposestringyesPropósito do protocolo (ex: "Privacy-as-a-Service and Autonomous DPO on Solana").
registeredAgentstring–Agente registrado em ADGM (opcional — sem valor default para evitar induzir erro).

No output schema declared.

No examples provided.

generate_agent_repo_policy ~109

Gera uma política JSON estruturada descrevendo as restrições e regras que o código de um Agente de IA deve provar via ZK-SP1 (ex: sem vazamento de chaves, acesso restrito).

NameTypeReqDescription
agentNamestringyesNome do agente autônomo
domainstringyesDomínio de atuação do agente
requiredPermissionsarray–Permissões que o agente solicita (ex: ["READ_WALLET", "EXECUTE_TRADE"])

No output schema declared.

No examples provided.

generate_ai_hria ~213

Gera Human Rights Impact Assessment (HRIA) específico pra sistema AI — distinto de DPIA (que cobre só data protection). Cobre dimensões enfatizadas pelo CAIDP: free expression, association, privacy, gender-based violence facilitation (CAIDP HRC submission Feb 2025), vulnerable populations, children safety. Output Markdown estruturado pronto pra adoção. Aligned com UNESCO RAM social_cultural dimension + EU-AIA Art. 27 FRIA.

NameTypeReqDescription
affectedPopulationsarray–Populações afetadas (e.g. ["customers", "children", "marginalized communities"])
aiSystemIdstringyes–
humanRightsImpactobject–Self-declared dimensões de impacto a direitos humanos
jurisdictionstring–Jurisdição target (default: CAIDP-UG cross-jurisdictional)
systemNamestringyesNome legível do sistema AI
systemPurposestringyesFinalidade declarada

No output schema declared.

No examples provided.

generate_aiverify_plugin_template ~164

Gera scaffold Python para integração AI Verify Toolkit (Singapore AIVT 2.0) + submissão on-chain via aiverify-attestation program. Retorna arquivo pronto para copiar — não roda AI Verify, apenas estrutura o plugin + anchoring.

NameTypeReqDescription
includeAnchoringScriptboolean–Se true (default), inclui script anchoring.py que submete tx ao aiverify-attestation.
metricstring–Métrica principal a medir (default: fairness).
modelTypestring–Tipo do modelo (default: pytorch). AIVT 2.0 suporta nativamente PyTorch e sklearn.
operatorAuthoritystring–Base58 pubkey do operator que assina attest_model (default: placeholder).

No output schema declared.

No examples provided.

generate_audit_checklist ~58

Gera checklist de auditoria LGPD/GDPR

NameTypeReqDescription
auditScopestringyesEscopo da auditoria
companystringyes–
frameworkstringyesFramework (LGPD, GDPR, ambos)

No output schema declared.

No examples provided.

generate_audit_stored ~206

Gera uma auditoria LGPD/GDPR completa e entrega três artefatos em uma só chamada: (1) PDF pronto pro cliente (base64), (2) ciphertext AES-256-GCM pinado no IPFS com CID auditável, (3) commitment ancorado on-chain no compliance-registry PDA (quando registerOnChain=true). Response inclui a chave AES pra decrypt posterior.

NameTypeReqDescription
areasarray–Áreas focais (opcional)
auditScopestringyesEscopo da auditoria
cnpjstring–CNPJ (opcional)
companystringyesNome da empresa
frameworkstring–Framework (padrão: lgpd)
registerOnChainboolean–Ancorar commitment on-chain no compliance-registry? (padrão: false)
uploadToStorageboolean–Upload encrypted ciphertext pro IPFS? (padrão: true)

No output schema declared.

No examples provided.

generate_caio_governance_plan ~177

Gera plano organizacional para Chief AI Officer (CAIO) baseado em DS-920 (Digital Agency Japan, May 2025) + AISI CAIO Guidebook (March 2026). Cobre: papel CAIO + reporting line + audit interno + decision framework + AI usage policy. Output em Markdown estruturado pronto pra adoção.

NameTypeReqDescription
existingDPOboolean–Já tem DPO designado? (CAIO + DPO podem coexistir; reporting separado)
jurisdictionstring–Jurisdição target (default JAPAN). Aceita JP/JAPAN/HIROSHIMA.
organizationNamestringyesNome da organização
organizationTypestring–Tipo de organização (define mandate strength: government=DS-920 binding, others=AISI guidance)

No output schema declared.

No examples provided.

generate_consent_manager_plan ~228

Gera plano de implementação de Consent Manager (DPDP India Rules 2025 §6 + Capítulo 2) com arquitetura on-chain sobre o dpo2u-solana consent-manager program. Inclui taxonomia de purposes, fluxos record/revoke, pontos de integração e checklist DPDP.

NameTypeReqDescription
dataBoardRegistrationboolean–Se true, inclui seção sobre registration obrigatória como Consent Manager com DPB (Data Protection Board of India). Default true.
organizationNamestringyesNome da organização (data fiduciary).
organizationPubkeystring–Solana pubkey do data fiduciary (base58). Se omitido, plano usa placeholder <FIDUCIARY_PUBKEY>.
purposesarray–Taxonomia de purposes (mínimo 1). Omitido → gera taxonomia-exemplo com 5 purposes comuns.
useZkProofboolean–Se true, plano inclui record_verified_consent (CPI SP1). Se false ou omitido, apenas record_consent trusted-fiduciary path.

No output schema declared.

No examples provided.

generate_cvm_compliance_report ~208

Gera relatório de obrigações contínuas (CVM) a partir das evidências fornecidas. Toda seção sem evidência é marcada como LACUNA e entra em `gaps`; o veredito só é "conforme" se houver evidência para cada obrigação verificada. Sem evidências, devolve `nao-avaliado`. Não consulta a cadeia nem a CVM.

NameTypeReqDescription
evidenceobject–Evidência por obrigação (texto curto, link ou hash do documento): periodic_disclosure, investor_position, secondary_market. Obrigação sem evidência vira LACUNA.
includeSecondaryMarketboolean–Incluir a obrigação de mercado secundário e liquidez?
issuerCnpjstringyesCNPJ do emissor
reportingPeriodstringyesPeríodo de referência (ex: "Q3 2026", "Mensal - Abril 2026")
tokenNamestringyesNome do token

No output schema declared.

No examples provided.

generate_document_package ~204

Gera o pacote documental completo de um engajamento de compliance (até 18 documentos PDF com marca, capa selada e rodapé numerado) a partir de um EngagementDossier. Slots sem lastro são OMITIDOS e reportados em manifest.gaps — nada é fabricado. Documentos de pesquisa (handoff jurídico, tese) são attach-only. Marcas disponíveis: listadas no schema do dossiê. O schema do dossiê é servido por GET /v1/schema do docgen.

NameTypeReqDescription
dossierobjectyesEngagementDossier conforme strix/engagement/v1. Campos: engagement (obrigatório), privacy_score, ropa, subprocessors, dpia, gap_register, governance, one_pager, retention_schedule, attachments[].
includeZipboolean–Se true, retorna o zip do pacote em base64 (payload grande). Padrão false: retorna apenas o manifesto com documentos, gaps e placeholders.

No output schema declared.

No examples provided.

generate_dpia ~97

Gera Relatório de Impacto à Proteção de Dados (DPIA)

NameTypeReqDescription
companystringyesNome da empresa
dataSubjectsarrayyesTitulares dos dados (ex: clientes, funcionários)
dataTypesarrayyesTipos de dados (ex: email, nome, CPF)
processingActivitystringyesAtividade de processamento
purposestringyesFinalidade do processamento

No output schema declared.

No examples provided.

generate_dpia_stored ~81

Gera DPIA e armazena no Filecoin (Lighthouse)

NameTypeReqDescription
companystringyes–
dataSubjectsarrayyes–
dataTypesarrayyes–
processingActivitystringyes–
purposestringyes–
registerOnChainboolean–Registrar metadata na blockchain (default: true)

No output schema declared.

No examples provided.

generate_lgpd_kit ~182

Gera um Kit LGPD (schema: dpo2u/lgpd/v1) e devolve o kit direto. O upload cifrado (AES-256) para Lighthouse/IPFS só acontece com STORAGE_ENABLED=1, que vem desligado; nesse caso devolve também o CID e a chave de crypto-shredding.

NameTypeReqDescription
companyIdstringyesCNPJ ou DID da empresa
companyNamestringyesNome da empresa (Data Controller)
consentMechanismstringyesMecanismo de consentimento (ex: opt-in-explicito)
dataCategoriesarrayyesCategorias de dados tratados (ex: financeiro, biometrico)
dpoContactstringyesEmail de contato do DPO
retentionDaysnumberyesDias de retenção da política de dados

No output schema declared.

No examples provided.

generate_privacy_policy ~216

Gera Política de Privacidade completa e personalizada conforme LGPD/GDPR

NameTypeReqDescription
addressstring–Endereço
cnpjstring–CNPJ
collectsChildrenDataboolean–Coleta dados de crianças?
companyNamestringyesNome da empresa
companyTypestring–Tipo de empresa
contactEmailstringyesEmail de contato
countries––Países de destino — array (canonical, igual a map_data_flow) ou string (backward-compat)
dataCategoriesobject–Categorias de dados
dpoEmailstring–Email do DPO
dpoNamestring–Nome do DPO
dpoPhonestring–Telefone do DPO
internationalTransferboolean–Transferência internacional?
purposesarray–Finalidades do tratamento
sensitiveDataarray–Dados sensíveis
thirdPartiesarray–Terceiros

No output schema declared.

No examples provided.

generate_retention_policy ~144

Gera Política de Retenção granular — matriz por categoria de dado com período, base legal, método de descarte e storage backend. Fecha o gap "política de retenção genérica" do audit_infrastructure.

NameTypeReqDescription
cnpjstring–CNPJ (opcional)
companyNamestringyesNome da empresa
dataCategoriesarrayyesMatriz granular — uma entrada por categoria de dado
dpoEmailstringyesEmail do DPO
dpoNamestringyesNome do DPO
registerOnChainboolean–Registrar CID on-chain via dpo2u-solana (stub)

No output schema declared.

No examples provided.

generate_runtime_enforcement_plan ~182

Generates a deployment-ready Markdown runtime-enforcement plan for an agentic AI deployment. Maps target framework(s) + agent capabilities + (optional) IMDA risk taxonomy to 8 runtime control families: policy-as-code, tool gating, memory scoping, delegation controls, audit envelopes, decision envelope, continuous evaluation, incident response. When MGF-AGENTIC is in scope, prescribes the MCP server whitelist (§2.3.1 of the IMDA framework).

NameTypeReqDescription
agentIdstring––
capabilitiesInUsearrayyes–
deploymentTierstring––
jurisdiction–yes–
organizationNamestringyes–
riskTaxonomyarray–IMDA MGF-Agentic v1.0 §1.2.2 — 5 risk types. Used to expand recommended controls beyond capability mapping.

No output schema declared.

No examples provided.

generate_security_policy ~165

Gera Politica de Seguranca da Informacao completa conforme LGPD/ISO 27001

NameTypeReqDescription
cloudProviderstring–Provedor de nuvem
companyNamestringyesNome da empresa
companyTypestring–Tipo de empresa
contactEmailstringyesEmail de contato
dpoEmailstring–Email do DPO
dpoNamestring–Nome do DPO
encryptionAtReststring–Algoritmo de criptografia
incidentEmailstring–Email para incidentes
incidentTeamarray–Equipe de resposta
mfaEnabledboolean–MFA habilitado?
rolesarray–Papéis e acessos

No output schema declared.

No examples provided.

Install

How do I install the DPO2U compliance MCP server?

DPO2U compliance is a hosted endpoint at https://mcp.dpo2u.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.dpo2u.com

# add to Claude Code
claude mcp add --transport http fredericosanntana-dpo2u 'https://mcp.dpo2u.com/mcp'
Common questions

What is the DPO2U compliance MCP server?

DPO2U compliance is an MCP server listed in the public MCP registry as io.github.fredericosanntana/dpo2u. Check before you pay: counterparty compliance verdicts for AI agents, paid per call via x402. This page covers its hosted endpoint (https://mcp.dpo2u.com/mcp).

Is the DPO2U compliance MCP server safe to use?

DPO2U compliance scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DPO2U compliance MCP server expose?

DPO2U compliance exposes 83 tools: compliance_query, generate_dpia, generate_dpia_stored, generate_audit_checklist, generate_audit_stored, and 78 more. Their descriptions and schemas cost roughly 16,100 tokens of context every time the server is loaded.

Does the DPO2U compliance MCP server require authentication?

Yes. DPO2U compliance asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the DPO2U compliance MCP server still maintained?

DPO2U compliance is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the DPO2U compliance MCP server?

VerifyMCP ran 13 checks on DPO2U compliance, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.