DPO2U compliance
REMOTE · MCP.DPO2U.COM
Check before you pay: counterparty compliance verdicts for AI agents, paid per call via x402.
Available components
Last scanned (15 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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 →
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.
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 |
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 →
analyze_contract ~55
Analyze contracts for data protection compliance (LGPD/GDPR)
| Name | Type | Req | Description |
|---|---|---|---|
| analysisType | string | – | Type of analysis |
| contractText | string | yes | Contract text to analyze |
| regulations | array | – | 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`.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Stable identifier for the agent (used in output metadata). |
| capabilitiesInUse | array | yes | Subset of A1-A5 that the agent design actually exercises. |
| delegationProfile | object | – | – |
| jurisdiction | – | yes | One 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… |
| memoryProfile | object | – | – |
| toolsetDescription | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| compliance | array | yes | Regulations to check (LGPD, GDPR) |
| depth | string | yes | Audit depth level |
| generateReport | boolean | – | Generate executive report |
| hasAccessControls | boolean | – | Controles de acesso RBAC/ABAC |
| hasAuditProgram | boolean | – | Programa de auditoria periódico |
| hasBackup | boolean | – | Rotina de backup testada |
| hasDataBreachProtocol | boolean | – | Protocolo de notificação de violação |
| hasEncryption | boolean | – | Criptografia em repouso configurada |
| hasIncidentResponsePlan | boolean | – | Plano de resposta a incidentes |
| inventario | array | – | Inventário de dados pessoais encontrados (opcional) |
| target | string | yes | Target 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.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | Framework 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… |
| organizationProfile | object | yes | Perfil 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).
| Name | Type | Req | Description |
|---|---|---|---|
| aiSystemId | string | yes | sha256 hex (32B) ou opaque ID do sistema AI |
| prohibitedUseFlags | object | yes | Self-declared flags por categoria red-line. true = sistema realiza essa categoria. |
| targetJurisdictions | array | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| compliance | array | yes | Regulations to check (LGPD, GDPR) |
| depth | string | yes | Audit depth level |
| generateReport | boolean | – | Generate executive report |
| hasAccessControls | boolean | – | Controles de acesso RBAC/ABAC |
| hasAuditProgram | boolean | – | Programa de auditoria periódico |
| hasBackup | boolean | – | Rotina de backup testada |
| hasDataBreachProtocol | boolean | – | Protocolo de notificação de violação |
| hasEncryption | boolean | – | Criptografia em repouso configurada |
| hasIncidentResponsePlan | boolean | – | Plano de resposta a incidentes |
| inventario | array | – | Inventário de dados pessoais encontrados (opcional) |
| target | string | yes | Target 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster | string | – | Cluster Solana (default: devnet). |
| programId | string | – | Program ID do art-vault (default: C7sGZFeWPxEkaGHACwqdzCcy4QkacqPLYEwEarVpidna). |
| rpcUrl | string | – | URL RPC customizada (override do cluster default). |
| vault | object | – | Objeto ArtVault já decodificado (use para teste offline; quando presente, vaultPda é ignorado). |
| vaultPda | string | – | 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%+
| Name | Type | Req | Description |
|---|---|---|---|
| audit_report_id | string | – | ID of audit report to use as baseline (optional) |
| auto_apply | boolean | yes | Automatically apply corrections (false for planning only) |
| compliance_target | number | yes | Target compliance score (0-100) |
| dry_run | boolean | yes | Simulate remediation without making changes |
| include_evidence | boolean | – | Generate cryptographic evidence of improvements |
| remediation_scope | string | yes | Scope 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.
| Name | Type | Req | Description |
|---|---|---|---|
| breachProcedure | boolean | – | Procedimento de notificação de violação. |
| dsrProcess | boolean | – | Processo de direitos do titular. |
| impactAssessment | boolean | – | Avaliação de impacto (DPIA/RIPD). |
| jurisdiction | string | yes | Código de jurisdição (uma das 16: lgpd, gdpr, ccpa, pipeda, law25, appi, pipa, pdp, pdpa, dpdp, uae, popia, ndpa, mexico, vietnam, malaysia). |
| lawfulBasisRegister | boolean | – | Registro de base legal de tratamento. |
| officerDesignated | boolean | – | Encarregado / DPO designado. |
| organization | string | yes | Nome da organização auditada. |
| transferSafeguards | boolean | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| indicators | object | yes | 10 booleans/scores 0-1 por indicador. true (boolean) = totalmente coberto; numero (0-1) = parcial. |
| organizationName | string | yes | – |
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
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Nome da empresa |
| employeeTrainingFrequency | string | – | Frequência de treinamento |
| hasAuditProgram | boolean | – | Possui programa de auditoria? |
| hasCookieConsent | boolean | – | Possui consentimento de cookies? |
| hasDPO | boolean | – | Possui DPO designado? |
| hasDPOReport | boolean | – | Possui relatório DPO? |
| hasDataBreachProtocol | boolean | – | Possui protocolo de violação? |
| hasDataMapping | boolean | – | Possui mapeamento de dados? |
| hasDataProcessingAgreement | boolean | – | Possui acordos de processamento? |
| hasDataRetentionPolicy | boolean | – | Possui política de retenção? |
| hasIncidentResponsePlan | boolean | – | Possui plano de resposta a incidentes? |
| hasPrivacyPolicy | boolean | – | Possui política de privacidade? |
| industry | string | – | Setor de atuação |
| internationalTransfer | boolean | – | Transferência internacional? |
| jurisdiction | string | – | 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. |
| vertical | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| auditScope | string | yes | Escopo da auditoria |
| auditorName | string | – | Nome do auditor |
| auditorRole | string | – | Cargo do auditor |
| cnpj | string | – | CNPJ (opcional, contexto BR) |
| company | string | yes | Nome da empresa |
| framework | string | – | [DEPRECATED — use "jurisdiction" instead] Legacy parameter. Aceito como alias retro-compatível: LGPD/GDPR mapeiam direto para jurisdiction; "Ambos" gera report combinado LGPD+GDPR. |
| jurisdiction | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | CNPJ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | Có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. |
| includeFullArticles | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Dimensão de comparação (default: all). "onchain" foca apenas nas opportunities on-chain (DPDP Consent Manager, MiCAR ART, AI Verify). |
| targetMarkets | array | – | 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)
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Query de busca |
| topK | number | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| approverName | string | – | Nome do aprovador |
| approverRole | string | – | Cargo do aprovador |
| company | string | yes | Nome da empresa |
| dpoName | string | – | Nome do DPO |
| dpoRole | string | – | Cargo do DPO |
| includeIncidents | boolean | – | Incluir incidentes? |
| includeMetrics | boolean | – | Incluir métricas detalhadas? |
| includeRecommendations | boolean | – | Incluir recomendações? |
| period | string | yes | Perí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).
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Dados estruturados para o template (Section51Data ou Section52Data) |
| section | string | yes | – |
No output schema declared.
No examples provided.
cvm_generate_zk_proof ~71
RF03: ZK Compliance Proof Generator. Gera prova criptográfica preservando privacidade.
| Name | Type | Req | Description |
|---|---|---|---|
| claimStatement | string | yes | – |
| evidenceCategories | array | – | – |
| proofScheme | string | yes | – |
| regulations | array | – | – |
| verificationLevel | string | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| stage | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| covered_rules | array | – | Ids das regras que o dono já declara cobertas |
| institution_type | string | – | – |
| market | string | yes | Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US). Padrão BR. |
| repo_url | string | – | Opcional: repositório público (owner/repo ou URL do GitHub) |
| services | array | – | – |
| x_payment | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US). Padrão BR. |
| passport_id | string | yes | Passaporte DPO2U da contraparte |
| transfer_id | string | – | Opcional: id da transferência (bytes32 hex). Traz o veredito de Travel Rule espelhado na Stellar e na Avalanche. |
| x_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| institution_type | string | – | – |
| market | string | yes | Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US). Padrão BR. |
| passport_id | string | yes | – |
| services | array | – | – |
| transfer_id | string | – | Opcional: id da transferência (bytes32 hex). Traz o veredito de Travel Rule espelhado na Stellar e na Avalanche. |
| x_payment | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| domain | string | – | action=order: domínio público |
| order_id | string | – | verify/run/status |
| order_token | string | – | verify/run/status: devolvido no order |
| tier | string | – | action=order: padrão passive |
| x_payment | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| include_benchmarks | boolean | – | Include industry benchmark comparisons |
| organization | string | yes | Organization name for the report |
| privacy_level | string | – | Privacy protection level |
| report_type | string | yes | Type of encrypted report to generate |
| time_period | string | yes | Reporting 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).
| Name | Type | Req | Description |
|---|---|---|---|
| altSignerBase58 | string | – | Secret key base58 opcional. Se a attestation foi criada com signer ≠ server wallet, passar aqui. Apenas o issuer original pode revogar. |
| attestationPda | string | yes | PDA da attestation (base58) a revogar on-chain. |
| eraseBackend | string | yes | Backend onde o ciphertext vive. Determina a estratégia de erasure off-chain. |
| reason | string | yes | Motivo da erasure (≤64 bytes). Selado on-chain em revocation_reason. |
| storageRefUri | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| controllerJurisdiction | string | yes | Jurisdição primária do controller (GDPR/LGPD/etc.). Determina força da erasure obligation. |
| cryptoSchemeUsed | string | – | Esquema criptográfico usado pra proteger PII on-chain (se aplicável) |
| hasOffchainStorage | boolean | – | Existe storage off-chain do dado original? (true = pode deletar off-chain como compliance path) |
| onchainData | string | yes | Tipo 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… |
| perSubjectKeys | boolean | – | Cada data subject tem chave criptográfica separada? (habilita cryptographic shredding individual) |
| retentionRequirement | string | – | Existe requisito legal conflitante de retenção (ex: AML 5 anos, IRS 10 anos)? Especifique se sim. |
| systemDescription | string | yes | Breve 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.
| Name | Type | Req | Description |
|---|---|---|---|
| aiModelConfig | object | – | Necessário se isAgenticAI=true |
| hasToken | boolean | yes | – |
| isAgenticAI | boolean | yes | – |
| projectName | string | yes | – |
| tokenomics | object | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| aiSystemId | string | yes | Identificador do sistema AI sendo avaliado |
| coverage | object | – | Self-declaração de cobertura por categoria (será cross-checked com evidence count). |
| evidenceUris | array | – | URIs (IPFS, https, ar://) de relatórios de red teaming |
| teamComposition | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| commitmentHex | string | – | Commitment de 32 bytes (hex). |
| commitmentText | string | – | Texto a ser hashed (alternativa). |
| subject | string | yes | Subject 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).
| Name | Type | Req | Description |
|---|---|---|---|
| leafHashHex | string | yes | 32-byte leaf hash hex (retornado por submit_composed_attestation). |
| verifyPayload | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataFiduciary | string | yes | Data fiduciary pubkey base58 (server wallet se criado via submit_consent_record). |
| purposeHashHex | string | – | Purpose hash já computado (hex, 64 chars). Alternativa a purposeText. |
| purposeText | string | – | Texto da finalidade (será hashed). Usar OU purposeText OU purposeHashHex. |
| user | string | yes | User (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
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_type | string | yes | Type of executive dashboard |
| include_forecasts | boolean | – | Include predictive forecasting |
| include_trends | boolean | – | Include historical trend analysis |
| kpi_categories | array | yes | KPI categories to include in dashboard |
| privacy_level | string | – | Privacy level for executive presentation |
| time_horizon | string | yes | Time 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.
| Name | Type | Req | Description |
|---|---|---|---|
| foundationName | string | yes | Nome legal da fundação (ex: "DPO2U Protocol Foundation"). |
| guardianMultisig | string | – | Endereço Solana do multi-sig Squads que age como Guardian dos reserve/governance params (opcional). |
| initialCouncillors | array | yes | Nomes dos Councillors iniciais (min 2 requerido pelo ADGM). |
| protocolPurpose | string | yes | Propósito do protocolo (ex: "Privacy-as-a-Service and Autonomous DPO on Solana"). |
| registeredAgent | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | yes | Nome do agente autônomo |
| domain | string | yes | Domínio de atuação do agente |
| requiredPermissions | array | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| affectedPopulations | array | – | Populações afetadas (e.g. ["customers", "children", "marginalized communities"]) |
| aiSystemId | string | yes | – |
| humanRightsImpact | object | – | Self-declared dimensões de impacto a direitos humanos |
| jurisdiction | string | – | Jurisdição target (default: CAIDP-UG cross-jurisdictional) |
| systemName | string | yes | Nome legível do sistema AI |
| systemPurpose | string | yes | Finalidade 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.
| Name | Type | Req | Description |
|---|---|---|---|
| includeAnchoringScript | boolean | – | Se true (default), inclui script anchoring.py que submete tx ao aiverify-attestation. |
| metric | string | – | Métrica principal a medir (default: fairness). |
| modelType | string | – | Tipo do modelo (default: pytorch). AIVT 2.0 suporta nativamente PyTorch e sklearn. |
| operatorAuthority | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| auditScope | string | yes | Escopo da auditoria |
| company | string | yes | – |
| framework | string | yes | Framework (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.
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | – | Áreas focais (opcional) |
| auditScope | string | yes | Escopo da auditoria |
| cnpj | string | – | CNPJ (opcional) |
| company | string | yes | Nome da empresa |
| framework | string | – | Framework (padrão: lgpd) |
| registerOnChain | boolean | – | Ancorar commitment on-chain no compliance-registry? (padrão: false) |
| uploadToStorage | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| existingDPO | boolean | – | Já tem DPO designado? (CAIO + DPO podem coexistir; reporting separado) |
| jurisdiction | string | – | Jurisdição target (default JAPAN). Aceita JP/JAPAN/HIROSHIMA. |
| organizationName | string | yes | Nome da organização |
| organizationType | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dataBoardRegistration | boolean | – | Se true, inclui seção sobre registration obrigatória como Consent Manager com DPB (Data Protection Board of India). Default true. |
| organizationName | string | yes | Nome da organização (data fiduciary). |
| organizationPubkey | string | – | Solana pubkey do data fiduciary (base58). Se omitido, plano usa placeholder <FIDUCIARY_PUBKEY>. |
| purposes | array | – | Taxonomia de purposes (mínimo 1). Omitido → gera taxonomia-exemplo com 5 purposes comuns. |
| useZkProof | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | object | – | 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. |
| includeSecondaryMarket | boolean | – | Incluir a obrigação de mercado secundário e liquidez? |
| issuerCnpj | string | yes | CNPJ do emissor |
| reportingPeriod | string | yes | Período de referência (ex: "Q3 2026", "Mensal - Abril 2026") |
| tokenName | string | yes | Nome 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.
| Name | Type | Req | Description |
|---|---|---|---|
| dossier | object | yes | EngagementDossier conforme strix/engagement/v1. Campos: engagement (obrigatório), privacy_score, ropa, subprocessors, dpia, gap_register, governance, one_pager, retention_schedule, attachments[]. |
| includeZip | boolean | – | 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)
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Nome da empresa |
| dataSubjects | array | yes | Titulares dos dados (ex: clientes, funcionários) |
| dataTypes | array | yes | Tipos de dados (ex: email, nome, CPF) |
| processingActivity | string | yes | Atividade de processamento |
| purpose | string | yes | Finalidade do processamento |
No output schema declared.
No examples provided.
generate_dpia_stored ~81
Gera DPIA e armazena no Filecoin (Lighthouse)
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| dataSubjects | array | yes | – |
| dataTypes | array | yes | – |
| processingActivity | string | yes | – |
| purpose | string | yes | – |
| registerOnChain | boolean | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | CNPJ ou DID da empresa |
| companyName | string | yes | Nome da empresa (Data Controller) |
| consentMechanism | string | yes | Mecanismo de consentimento (ex: opt-in-explicito) |
| dataCategories | array | yes | Categorias de dados tratados (ex: financeiro, biometrico) |
| dpoContact | string | yes | Email de contato do DPO |
| retentionDays | number | yes | Dias 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
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Endereço |
| cnpj | string | – | CNPJ |
| collectsChildrenData | boolean | – | Coleta dados de crianças? |
| companyName | string | yes | Nome da empresa |
| companyType | string | – | Tipo de empresa |
| contactEmail | string | yes | Email de contato |
| countries | – | – | Países de destino — array (canonical, igual a map_data_flow) ou string (backward-compat) |
| dataCategories | object | – | Categorias de dados |
| dpoEmail | string | – | Email do DPO |
| dpoName | string | – | Nome do DPO |
| dpoPhone | string | – | Telefone do DPO |
| internationalTransfer | boolean | – | Transferência internacional? |
| purposes | array | – | Finalidades do tratamento |
| sensitiveData | array | – | Dados sensíveis |
| thirdParties | array | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | – | CNPJ (opcional) |
| companyName | string | yes | Nome da empresa |
| dataCategories | array | yes | Matriz granular — uma entrada por categoria de dado |
| dpoEmail | string | yes | Email do DPO |
| dpoName | string | yes | Nome do DPO |
| registerOnChain | boolean | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | – |
| capabilitiesInUse | array | yes | – |
| deploymentTier | string | – | – |
| jurisdiction | – | yes | – |
| organizationName | string | yes | – |
| riskTaxonomy | array | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| cloudProvider | string | – | Provedor de nuvem |
| companyName | string | yes | Nome da empresa |
| companyType | string | – | Tipo de empresa |
| contactEmail | string | yes | Email de contato |
| dpoEmail | string | – | Email do DPO |
| dpoName | string | – | Nome do DPO |
| encryptionAtRest | string | – | Algoritmo de criptografia |
| incidentEmail | string | – | Email para incidentes |
| incidentTeam | array | – | Equipe de resposta |
| mfaEnabled | boolean | – | MFA habilitado? |
| roles | array | – | Papéis e acessos |
No output schema declared.
No examples provided.
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
claude mcp add --transport http fredericosanntana-dpo2u 'https://mcp.dpo2u.com/mcp'
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.