Skip to content

MCP servers › io.github.fredericosanntana › dpo2u

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

dpo2u MCP server

Registry name io.github.fredericosanntana/dpo2u

DPO2U compliance — the publisher's title

by fredericosanntana · GitHub account (the registry's namespace rule)source link does not open (missing or private)Website ↗

Check before you pay: counterparty compliance verdicts for AI agents, paid per call via x402. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-17version 1.2.0streamable HTTP83 tools

Summary

io.github.fredericosanntana/dpo2u is a remote MCP server listed in the official MCP registry at version 1.2.0, under the namespace of the GitHub account fredericosanntana. Its linked repository, github.com/fredericosanntana/DPO2U, does not open publicly (missing or private). On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 83 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
link does not open publicly
Tools
83
Last tested
2026-11-17

Tool list size

41,970 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (83 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (mcp.dpo2u.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.2.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (create_dpo_report). That is our reading of the names; we did not call it. Source: our connection, 2026-11-17.

Worth knowing before you connect it

  • The linked repository does not open publicly, so the code cannot be reviewed through it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
1.2.0, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-16; 2 in the 90 days before the 2026-11-17 snapshot.
Most recent 2 versions
  • 1.2.0 · 2026-11-16
  • 1.1.0 · 2026-11-16
(versions still listed in the registry only)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

1 found in the records we hold

  • The repository link does not open: GitHub answered HTTP 404 (it does not exist, or it is private). — api.github.com · 2026-11-17 · all servers with this fact

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 1.2.0 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

What does this server offer?

Observed inventory
83tools
0resources
0prompts

None of its 83 tools are described as changing anything. For 83 the reading was uncertain, so no mark is shown.

  • compliance_query

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

    2 inputs, 1 required
    • querystringrequired“Query de busca”
    • topKnumber“Número de resultados (default: 10)”
  • generate_dpia

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

    5 inputs, 5 required
    • companystringrequired“Nome da empresa”
    • processingActivitystringrequired“Atividade de processamento”
    • dataTypesarrayrequired“Tipos de dados (ex: email, nome, CPF)”
    • dataSubjectsarrayrequired“Titulares dos dados (ex: clientes, funcionários)”
    • purposestringrequired“Finalidade do processamento”
  • generate_dpia_stored

    “Gera DPIA e armazena no Filecoin (Lighthouse)”

    6 inputs, 5 required
    • companystringrequired
    • processingActivitystringrequired
    • dataTypesarrayrequired
    • dataSubjectsarrayrequired
    • purposestringrequired
    • registerOnChainboolean“Registrar metadata na blockchain (default: true)”
  • generate_audit_checklist

    “Gera checklist de auditoria LGPD/GDPR”

    3 inputs, 3 required
    • companystringrequired
    • auditScopestringrequired“Escopo da auditoria”
    • frameworkstringrequired“Framework (LGPD, GDPR, ambos)”
  • generate_audit_stored

    “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 anco…”

    7 inputs, 2 required
    • companystringrequired“Nome da empresa”
    • cnpjstring“CNPJ (opcional)”
    • auditScopestringrequired“Escopo da auditoria”
    • areasarray“Áreas focais (opcional)”
    • frameworkstring“Framework (padrão: lgpd)”
    • uploadToStorageboolean“Upload encrypted ciphertext pro IPFS?”
    • registerOnChainboolean“Ancorar commitment on-chain no compliance-registry?”
  • verify_compliance_proof

    “Verifica prova de compliance (commitment hash/ZK proof)”

    2 inputs, 2 required
    • proofHashstringrequired“Hash da prova”
    • cidstringrequired“CID IPFS do documento”
  • calculate_privacy_score

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

    16 inputs, 1 required
    • companystringrequired“Nome da empresa”
    • industrystring“Setor de atuação”
    • verticalstring“Vertical (Sprint 2026-05-27 A.5) — prepend roadmap items vertical-específicos aos genéricos.”
    • hasDPOboolean“Possui DPO designado?”
    • hasDPOReportboolean“Possui relatório DPO?”
    • hasPrivacyPolicyboolean“Possui política de privacidade?”
    • hasCookieConsentboolean“Possui consentimento de cookies?”
    • hasDataBreachProtocolboolean“Possui protocolo de violação?”
    • hasDataProcessingAgreementboolean“Possui acordos de processamento?”
    • hasAuditProgramboolean“Possui programa de auditoria?”
    • hasDataMappingboolean“Possui mapeamento de dados?”
    • hasIncidentResponsePlanboolean“Possui plano de resposta a incidentes?”
    • hasDataRetentionPolicyboolean“Possui política de retenção?”
    • internationalTransferboolean“Transferência internacional?”
    • employeeTrainingFrequencystring“Frequência de treinamento”
    • jurisdictionstring“Jurisdição alvo opcional para contextualização do score de maturidade do programa.”
  • evaluate_onchain_erasure_strategy

    “Avalia estratégia de compliance com GDPR Art.”

    7 inputs, 3 required
    • systemDescriptionstringrequired“Breve descrição do sistema (ex: "VC vault on Stellar storing encrypted credential payloads")”
    • onchainDatastringrequired“Tipo de dado armazenado on-chain.”
    • controllerJurisdictionstringrequired“Jurisdição primária do controller (GDPR/LGPD/etc.).”
    • hasOffchainStorageboolean“Existe storage off-chain do dado original?”
    • cryptoSchemeUsedstring“Esquema criptográfico usado pra proteger PII on-chain (se aplicável)”
    • perSubjectKeysboolean“Cada data subject tem chave criptográfica separada?”
    • retentionRequirementstring“Existe requisito legal conflitante de retenção (ex: AML 5 anos, IRS 10 anos)?”
  • check_sectoral_framework

    “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 (…”

    2 inputs, 1 required
    • frameworkstringrequired“Código do framework.”
    • includeFullArticlesboolean“Se true, retorna keyArticles completo (verbose).”
  • map_data_flow

    “Mapeia fluxo de dados com diagrama Mermaid e identificação de riscos”

    8 inputs, 1 required
    • systemNamestringrequired“Nome do sistema”
    • systemDescriptionstring“Descrição do sistema”
    • dataSourcesarray“Fontes de dados”
    • processingActivitiesarray“Atividades de processamento”
    • thirdPartiesarray“Terceiros compartilhados”
    • retentionPeriodstring“Período de retenção”
    • internationalTransferboolean“Transferência internacional?”
    • countriesarray“Países de destino”
  • generate_privacy_policyon 1 other server

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

    15 inputs, 2 required
    • companyNamestringrequired“Nome da empresa”
    • companyTypestring“Tipo de empresa”
    • cnpjstring“CNPJ”
    • addressstring“Endereço”
    • contactEmailstringrequired“Email de contato”
    • dpoNamestring“Nome do DPO”
    • dpoEmailstring“Email do DPO”
    • dpoPhonestring“Telefone do DPO”
    • dataCategoriesobject“Categorias de dados”
    • sensitiveDataarray“Dados sensíveis”
    • collectsChildrenDataboolean“Coleta dados de crianças?”
    • purposesarray“Finalidades do tratamento”
    • thirdPartiesarray“Terceiros”
    • internationalTransferboolean“Transferência internacional?”
    • countriesarray or string“Países de destino — array (canonical, igual a map_data_flow) ou string (backward-compat)”
  • generate_terms_of_use

    “Gera Termos de Uso completos e personalizados conforme LGPD”

    8 inputs, 2 required
    • companyNamestringrequired“Nome da empresa”
    • companyTypestring“Tipo de empresa”
    • contactEmailstringrequired“Email de contato”
    • dpoNamestring“Nome do DPO”
    • dpoEmailstring“Email do DPO”
    • dpoPhonestring“Telefone do DPO”
    • servicesarray“Serviços oferecidos”
    • collectsChildrenDataboolean“Coleta dados de crianças?”
Show 71 more tools
  • generate_security_policy

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

    11 inputs, 2 required
    • companyNamestringrequired“Nome da empresa”
    • companyTypestring“Tipo de empresa”
    • contactEmailstringrequired“Email de contato”
    • dpoNamestring“Nome do DPO”
    • dpoEmailstring“Email do DPO”
    • incidentEmailstring“Email para incidentes”
    • mfaEnabledboolean“MFA habilitado?”
    • encryptionAtReststring“Algoritmo de criptografia”
    • cloudProviderstring“Provedor de nuvem”
    • rolesarray“Papéis e acessos”
    • incidentTeamarray“Equipe de resposta”
  • register_retention_policy_onchain

    “Registra on-chain (dpo2u-solana compliance-registry) uma política de retenção previamente gerada.”

    6 inputs, 2 required
    • cidstringrequired“CID Lighthouse da policy”
    • contentHashstringrequired“sha256 hex de 64 chars (32 bytes)”
    • subjectPubkeystring“Company pubkey base58 (default: issuer)”
    • schemaIdstring“Schema pubkey base58 (opcional)”
    • expiresAtnumber“Unix timestamp de expiração (opcional)”
    • clusterstring“Target cluster”
  • generate_retention_policy

    “Gera Política de Retenção granular — matriz por categoria de dado com período, base legal, método de descarte e storage backend.”

    6 inputs, 4 required
    • companyNamestringrequired“Nome da empresa”
    • cnpjstring“CNPJ (opcional)”
    • dataCategoriesarrayrequired“Matriz granular — uma entrada por categoria de dado”
    • dpoNamestringrequired“Nome do DPO”
    • dpoEmailstringrequired“Email do DPO”
    • registerOnChainboolean“Registrar CID on-chain via dpo2u-solana (stub)”
  • check_complianceon 16 other servers

    “Verifica conformidade em 15 jurisdições: LGPD, GDPR, MICAR, DPDP, PDPA, UAE/PDPL, POPIA, NDPA, CCPA, PIPEDA, LAW25, PIPA, PDP, APPI, ART.”

    7 inputs, 2 required
    • companystringrequired“Nome da empresa”
    • cnpjstring“CNPJ (opcional, contexto BR)”
    • auditScopestringrequired“Escopo da auditoria”
    • jurisdictionstring“Jurisdição alvo (25 jurisdições + "ART"/"CASP"/"PDPL" aliases).”
    • frameworkstring“[DEPRECATED — use "jurisdiction" instead] Legacy parameter.”
    • auditorNamestring“Nome do auditor”
    • auditorRolestring“Cargo do auditor”
  • create_dpo_report

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

    9 inputs, 2 required
    • companystringrequired“Nome da empresa”
    • periodstringrequired“Período do relatório”
    • dpoNamestring“Nome do DPO”
    • dpoRolestring“Cargo do DPO”
    • approverNamestring“Nome do aprovador”
    • approverRolestring“Cargo do aprovador”
    • includeMetricsboolean“Incluir métricas detalhadas?”
    • includeIncidentsboolean“Incluir incidentes?”
    • includeRecommendationsboolean“Incluir recomendações?”
  • zk_compliance_attest

    “Zero-knowledge compliance attestation (DPO2U + Solana).”

    6 inputs, 1 required
    • companyIdstringrequired“DID or CNPJ of the subject (alias: company, subject)”
    • actionstring“Pipeline stage (default: full)”
    • scorenumber“Compliance score 0..100”
    • thresholdnumber“Policy threshold, default 70”
    • metricsobject“Private metrics; averaged to produce score if score not provided”
    • proofDatastring“Serialized ProofBundle (action=verify|register)”
  • validate_cvm_token_rules

    “Valida se uma operação de investimento em um token RWA/Security Token cumpre as regras da CVM (ex: limites de investimento para não-qualificados, lock-ups).”

    5 inputs, 3 required
    • tokenNamestringrequired“Nome ou símbolo do token”
    • issuerCnpjstring“CNPJ do emissor”
    • investorProfilestringrequired“Perfil do investidor segundo a CVM”
    • investmentAmountnumberrequired“Valor pretendido de investimento em BRL”
    • ruleSetstring“Conjunto de regras aplicáveis (ex: "RCVM88", "RCVM161")”
  • generate_cvm_compliance_report

    “Gera relatório de obrigações contínuas (CVM) a partir das evidências fornecidas.”

    5 inputs, 3 required
    • tokenNamestringrequired“Nome do token”
    • issuerCnpjstringrequired“CNPJ do emissor”
    • reportingPeriodstringrequired“Período de referência (ex: "Q3 2026", "Mensal - Abril 2026")”
    • includeSecondaryMarketboolean“Incluir a obrigação de mercado secundário e liquidez?”
    • evidenceobject“Evidência por obrigação (texto curto, link ou hash do documento): periodic_disclosure, investor_position, secondary_market.”
  • evaluate_project_compliance

    “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).”

    5 inputs, 3 required
    • projectNamestringrequired
    • hasTokenbooleanrequired
    • isAgenticAIbooleanrequired
    • tokenomicsobject“Necessário se hasToken=true”
    • aiModelConfigobject“Necessário se isAgenticAI=true”
  • validate_lgpd_evidence

    “Valida um manifesto de evidências LGPD (schema dpo2u/lgpd-evidence/v1, gerado pela skill lgpd-attest) e roda o pack lgpd@1.1.0 (20 regras: base legal, encarregado, incidente em 3 dias úteis (Res.”

    1 input, 1 required
    • manifestobjectrequired“Conteúdo de .lgpd/manifest.json (dpo2u/lgpd-evidence/v1).”
  • submit_lgpd_attestation

    “SÓ OPERADOR.”

    7 inputs, 4 required
    • manifestobjectrequired“Manifesto dpo2u/lgpd-evidence/v1 revisado”
    • reportIdstringrequired“reportId devolvido por validate_lgpd_evidence para este manifesto”
    • reviewerNamestringrequired“Nome do operador revisor (vira hash; não vai a público)”
    • verdictstringrequired“Veredito do revisor”
    • dryRunboolean“Só monta o payload, sem gravar on-chain”
    • chainstring“Onde gravar (só redes de teste): midnight (preview), avalanche (Fuji) ou both (padrão)”
    • subjectstring“Hash hex de 32 bytes do sujeito, fornecido pelo operador (ex.: H(CNPJ) ou H(CAIP-10/DID)).”
  • cvm_generate_disclosure

    “RF02: CVM Disclosure Generator.”

    2 inputs, 2 required
    • sectionstringrequired
    • dataobjectrequired“Dados estruturados para o template (Section51Data ou Section52Data)”
  • cvm_generate_zk_proof

    “RF03: ZK Compliance Proof Generator.”

    5 inputs, 2 required
    • claimStatementstringrequired
    • evidenceCategoriesarray
    • regulationsarray
    • proofSchemestringrequired
    • verificationLevelstring
  • generate_agent_repo_policy

    “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).”

    3 inputs, 2 required
    • agentNamestringrequired“Nome do agente autônomo”
    • domainstringrequired“Domínio de atuação do agente”
    • requiredPermissionsarray“Permissões que o agente solicita (ex: ["READ_WALLET", "EXECUTE_TRADE"])”
  • verify_agent_repo_zk_proof

    “Verifica uma prova Zero-Knowledge (SP1/Groth16) que atesta que o repositório de um Agente de IA cumpre a política estabelecida sem revelar seu código-fonte.”

    6 inputs, 3 required
    • agentDidstringrequired“DID (Decentralized Identifier) do Agente”
    • repoCommitHashstringrequired“Hash do commit do repositório avaliado”
    • proofPayloadstringrequired“Prova serializada.”
    • publicValuesstring“Public values (base64) — obrigatório quando proofPayload são apenas os bytes crus da prova.”
    • vkeyHashstring“Hash da verification key do circuito (opcional; identidade do circuito).”
    • allowMockboolean“Se true, aceita verificação mock (cadeia inalcançável) como válida — APENAS para dev/test.”
  • compare_jurisdictionson 5 other servers

    “Compara jurisdições regulatórias (LGPD/BR, GDPR/EU, DPDP/IN, MICAR/EU, PDPA/SG, UAE) para escolha de setup DPO2U.”

    2 inputs
    • targetMarketsarray“Lista de jurisdições a incluir.”
    • focusstring“Dimensão de comparação (default: all).”
  • generate_adgm_foundation_charter

    “Gera charter/articles template para registro de uma DPO2U-style Foundation sob o ADGM DLT Foundations Framework (Abu Dhabi).”

    5 inputs, 3 required
    • foundationNamestringrequired“Nome legal da fundação (ex: "DPO2U Protocol Foundation").”
    • protocolPurposestringrequired“Propósito do protocolo (ex: "Privacy-as-a-Service and Autonomous DPO on Solana").”
    • initialCouncillorsarrayrequired“Nomes dos Councillors iniciais (min 2 requerido pelo ADGM).”
    • guardianMultisigstring“Endereço Solana do multi-sig Squads que age como Guardian dos reserve/governance params (opcional).”
    • registeredAgentstring“Agente registrado em ADGM (opcional — sem valor default para evitar induzir erro).”
  • generate_consent_manager_plan

    “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.”

    5 inputs, 1 required
    • organizationNamestringrequired“Nome da organização (data fiduciary).”
    • organizationPubkeystring“Solana pubkey do data fiduciary (base58).”
    • purposesarray“Taxonomia de purposes (mínimo 1).”
    • useZkProofboolean“Se true, plano inclui record_verified_consent (CPI SP1).”
    • dataBoardRegistrationboolean“Se true, inclui seção sobre registration obrigatória como Consent Manager com DPB (Data Protection Board of India).”
  • audit_micar_art

    “Audita um ART vault (dpo2u-solana art-vault program) para conformidade MiCAR — Proof of Reserve (Art.”

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

    “Gera scaffold Python para integração AI Verify Toolkit (Singapore AIVT 2.0) + submissão on-chain via aiverify-attestation program.”

    4 inputs
    • modelTypestring“Tipo do modelo (default: pytorch).”
    • metricstring“Métrica principal a medir (default: fairness).”
    • operatorAuthoritystring“Base58 pubkey do operator que assina attest_model (default: placeholder).”
    • includeAnchoringScriptboolean“Se true (default), inclui script anchoring.py que submete tx ao aiverify-attestation.”
  • submit_consent_record

    “Submete uma transação real on-chain no consent-manager program (DPDP India §6) — record_consent.”

    5 inputs, 3 required
    • userstringrequired“User (data principal) Solana pubkey em base58.”
    • purposeCodenumberrequired“Código numérico u16 da finalidade (0-65535).”
    • purposeTextstringrequired“Texto humano da finalidade (ex: "marketing_communications").”
    • storageUristring“URI off-chain opcional apontando pro termo de consent assinado.”
    • expiresAtnumber“Unix timestamp (segundos) de expiração opcional.”
  • submit_consent_revoke

    “Revoga um consent event on-chain (DPDP §6(4) — direito de retirada).”

    3 inputs, 3 required
    • consentPdastringrequired“PDA do consent record a revogar (base58).”
    • reasonstringrequired“Motivo da revogação (≤64 bytes).”
    • userSignerBase58stringrequired“Secret key base58 do USER que criou o consent.”
  • fetch_consent_record

    “Lê (read-only) um consent PDA do consent-manager on-chain.”

    4 inputs, 2 required
    • userstringrequired“User (data principal) pubkey base58.”
    • dataFiduciarystringrequired“Data fiduciary pubkey base58 (server wallet se criado via submit_consent_record).”
    • purposeTextstring“Texto da finalidade (será hashed).”
    • purposeHashHexstring“Purpose hash já computado (hex, 64 chars).”
  • submit_compliance_attestation

    “Submete uma attestation LGPD/GDPR on-chain no compliance-registry program (create_attestation legacy path, sem ZK).”

    6 inputs, 1 required
    • subjectstringrequired“Subject pubkey base58 (empresa/DID controller).”
    • commitmentHexstring“Commitment de 32 bytes (hex, 64 chars).”
    • commitmentTextstring“Texto a ser hashed via sha256 pra gerar o commitment.”
    • storageUristring“URI off-chain pra o documento (DPIA/audit report).”
    • schemaIdBase58string“Schema ID opcional (Pubkey).”
    • expiresAtnumber“Unix timestamp de expiração (opcional).”
  • submit_attestation_stellar

    “Submete uma atestação de conformidade on-chain na Stellar/Soroban via o Pilot Gateway (POST /api/v1/attestation/submit).”

    3 inputs, 3 required
    • use_case_idstringrequired“ID do use case configurado no contrato (ex.: compliance_attestation_v1).”
    • request_idstringrequired“ID idempotente da requisição (replay com mesmo body → mesma atestação).”
    • evidenceobjectrequired“Objeto de evidência do use case (flags de controle, jurisdição, etc.).”
  • build_compliance_evidence

    “Converte um input de auditoria de conformidade no objeto `evidence` do use case compliance_attestation_v1, com score de maturidade.”

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

    “Submete uma attestation ZK-verified no compliance-registry (create_verified_attestation).”

    7 inputs, 4 required
    • subjectstringrequired“Subject pubkey base58.”
    • commitmentHexstringrequired“32 bytes hex (deve bater com bytes[32..64] do publicInputs).”
    • proofHexstringrequired“356-byte SP1 v6 Groth16 proof (hex).”
    • publicInputsHexstringrequired“96-byte ABI-encoded PublicValuesStruct (hex).”
    • storageUristring“URI off-chain (max 128 bytes).”
    • schemaIdBase58string“Schema ID opcional.”
    • expiresAtnumber“Unix timestamp expiração.”
  • revoke_compliance_attestation

    “Revoga uma attestation LGPD/GDPR on-chain (compliance-registry.revoke_attestation).”

    3 inputs, 2 required
    • attestationPdastringrequired“PDA da attestation (base58).”
    • reasonstringrequired“Motivo da revogação (≤64 bytes).”
    • altSignerBase58string“Secret key base58 opcional.”
  • erase_attestation_payload

    “LGPD Art.”

    5 inputs, 3 required
    • attestationPdastringrequired“PDA da attestation (base58) a revogar on-chain.”
    • reasonstringrequired“Motivo da erasure (≤64 bytes).”
    • eraseBackendstringrequired“Backend onde o ciphertext vive.”
    • storageRefUristring“URI canônico do blob (ex.: `ipfs://bafy...` ou `shdw://{account}/{filename}`).”
    • altSignerBase58string“Secret key base58 opcional.”
  • describe_pipeline

    “Return the canonical DPO2U compliance pipeline (DISCOVER → AUDIT → ASSESS → REMEDIATE → DOCUMENT → PROVE → REGISTER, plus on-demand ERASE).”

    1 input
    • stagestring“Optional stage name filter (DISCOVER | AUDIT | ASSESS | REMEDIATE | DOCUMENT | PROVE | REGISTER | ERASE).”
  • fetch_compliance_attestation

    “Lê (read-only) uma attestation PDA do compliance-registry.”

    3 inputs, 1 required
    • subjectstringrequired“Subject pubkey base58.”
    • commitmentHexstring“Commitment de 32 bytes (hex).”
    • commitmentTextstring“Texto a ser hashed (alternativa).”
  • register_popia_io

    “Registra um Information Officer formal no popia_info_officer_registry program (POPIA §55, África do Sul).”

    5 inputs, 2 required
    • informationOfficerstringrequired“Pubkey do Information Officer (base58).”
    • organizationIdstring“ID da organização (e.g., CIPC company number).”
    • organizationIdHashHexstring“32-byte hash hex da organização (alternativa a organizationId).”
    • contactHashHexstringrequired“sha256 hex (32 bytes) dos contatos do IO — kept off-chain for POPIA Condition 4 minimization.”
    • storageUristring“URI off-chain pra evidência da nomeação.”
  • register_ccpa_optout

    “Registra um opt-out CCPA §1798.135 (Califórnia) no ccpa_optout_registry program.”

    5 inputs, 2 required
    • consumerIdstring“ID opaco do consumidor (NÃO wallet pubkey).”
    • consumerCommitmentHashHexstring“32-byte hex do commitment do consumidor (alternativa a consumerId).”
    • optoutKindnumberrequired“1=sale (§1798.120), 2=share (CPRA cross-context), 3=sensitive (§1798.121).”
    • viaGpcbooleanrequired“Se foi disparado pelo Global Privacy Control signal (Cal.”
    • storageUristring“URI off-chain pra evidência (form, GPC header).”
  • record_pipeda_consent

    “Registra consent granular conforme PIPEDA Schedule 1 (Canadá).”

    7 inputs, 5 required
    • subjectstringrequired“Pubkey do sujeito (base58).”
    • purposeCodenumberrequired“Código u16 da finalidade (taxonomia off-chain).”
    • purposeTextstringrequired“Texto humano da finalidade — sha256-hashed pra purpose_hash on-chain.”
    • consentFormnumberrequired“1=express, 2=implied (reasonable expectation), 3=opt-out (limited circumstances).”
    • principlesEvidencednumberrequired“Bitmap u16 — bit N (1-indexed) = Princípio N evidenciado.”
    • crossBorderDestinationstring“ISO-3166-1 alpha-2 country code (e.g.”
    • storageUristring“URI off-chain pro consent form assinado.”
  • issue_pipa_zk_identity

    “Emite uma ZK identity attestation no pipa_korea_zk_identity program (PIPA Korea Art.”

    7 inputs, 5 required
    • subjectCommitmentHexstringrequired“32-byte hex commitment (Poseidon ou sha256 de identity_secret + salt).”
    • attributeKindnumberrequired“1=age_gate_19, 2=korean_resident, 3=kyc_verified, 4=domestic_representative.”
    • attributeMetadataHashHexstringrequired“32-byte hex sha256 dos metadados off-chain (issuance details, validity).”
    • proofHexstringrequired“356-byte hex SP1 v6 Groth16 proof.”
    • publicInputsHexstringrequired“96-byte hex ABI-encoded PublicValuesStruct.”
    • expiresAtnumber“Unix timestamp opcional de expiração.”
    • storageUristring“URI off-chain (max 128 bytes).”
  • audit_ai_governance

    “Audita conformidade com framework AI governance (8 frameworks: JAPAN, HIROSHIMA-ICOC, EU-AIA, KOREA, CAIDP-UG, UNESCO-RAM, MGF-AGENTIC, AI-GOVERNANCE-STACK).”

    2 inputs, 2 required
    • jurisdictionstringrequired“Framework alvo.”
    • organizationProfileobjectrequired“Perfil de governance da organização auditada.”
  • generate_caio_governance_plan

    “Gera plano organizacional para Chief AI Officer (CAIO) baseado em DS-920 (Digital Agency Japan, May 2025) + AISI CAIO Guidebook (March 2026).”

    4 inputs, 1 required
    • organizationNamestringrequired“Nome da organização”
    • organizationTypestring“Tipo de organização (define mandate strength: government=DS-920 binding, others=AISI guidance)”
    • jurisdictionstring“Jurisdição target (default JAPAN).”
    • existingDPOboolean“Já tem DPO designado?”
  • evaluate_red_team_evidence

    “Avalia evidence de red teaming de sistemas AI contra AISI Red Teaming Guide v1.10 (March 2025).”

    4 inputs, 1 required
    • aiSystemIdstringrequired“Identificador do sistema AI sendo avaliado”
    • evidenceUrisarray“URIs (IPFS, https, ar://) de relatórios de red teaming”
    • coverageobject“Self-declaração de cobertura por categoria (será cross-checked com evidence count).”
    • teamCompositionstring“Composição do red team.”
  • submit_hiroshima_icoc_attestation

    “Submete atestação on-chain de compromisso com Hiroshima International Code of Conduct (G7 voluntary code).”

    5 inputs, 3 required
    • aiSystemIdstringrequired“sha256 hex (32B) ou opaque ID do sistema AI”
    • attestationTypestringrequired“Tipo de atestação.”
    • evidenceHashHexstringrequired“sha256 hex (32B) de bundle de evidence off-chain”
    • storageUristring“IPFS/ar:// URI da evidence bundle.”
    • validUntilnumber“Unix timestamp opcional de expiração”
  • assess_agent_capability

    “Per-agent capability-shaped assessment (A1-A5) against one or more AI governance frameworks.”

    6 inputs, 3 required
    • agentIdstringrequired“Stable identifier for the agent (used in output metadata).”
    • jurisdictionstring or arrayrequired“One or more framework codes/aliases.”
    • capabilitiesInUsearrayrequired“Subset of A1-A5 that the agent design actually exercises.”
    • toolsetDescriptionstring“Free-text description of MCP tools / external systems / APIs the agent calls (used for A2 evidence).”
    • memoryProfileobject
    • delegationProfileobject
  • generate_runtime_enforcement_plan

    “Generates a deployment-ready Markdown runtime-enforcement plan for an agentic AI deployment.”

    6 inputs, 3 required
    • organizationNamestringrequired
    • agentIdstring
    • jurisdictionstring or arrayrequired
    • capabilitiesInUsearrayrequired
    • riskTaxonomyarray“IMDA MGF-Agentic v1.0 §1.2.2 — 5 risk types.”
    • deploymentTierstring
  • multi_jurisdiction_compliance_check

    “Fan-out de check_compliance para N jurisdições em uma chamada.”

    48 inputs, 2 required
    • companystringrequired“Nome da empresa”
    • cnpjstring“CNPJ (opcional, contexto BR)”
    • auditScopestring“Escopo da auditoria”
    • jurisdictionsarrayrequired“Array de codes ou aliases (LGPD/GDPR/APPI/JP/JAPAN/etc.).”
    • aggregateBystring“Estratégia de agregação do score (default: average).”
    • auditorNamestring
    • auditorRolestring
    • hasDPOboolean
    • hasPrivacyPolicyboolean
    • hasDataMappingboolean
    • hasIncidentResponsePlanboolean
    • hasDataBreachProtocolboolean
    • hasDataProcessingAgreementboolean
    • hasAuditProgramboolean
    • hasDataRetentionPolicyboolean
    • hasCookieConsentboolean
    • internationalTransferboolean
    • hasDPIAboolean
    • hasConsentManagerboolean
    • hasErasureMechanismboolean
    • hasDataPortabilityboolean
    • hasChildrenDataSafeguardsboolean
    • hasADMOptOutboolean
    • hasLawfulBasisRegisterboolean
    • hasCrossBorderSafeguardsboolean

    and 23 more not listed here.

  • audit_ai_red_lines

    “Audita um sistema AI contra as red lines da CAIDP (Apr 2026 UN Global Dialogue submission) + EU-AIA Art.”

    3 inputs, 2 required
    • aiSystemIdstringrequired“sha256 hex (32B) ou opaque ID do sistema AI”
    • prohibitedUseFlagsobjectrequired“Self-declared flags por categoria red-line.”
    • targetJurisdictionsarray“Jurisdições alvo (e.g.”
  • generate_ai_hria

    “Gera Human Rights Impact Assessment (HRIA) específico pra sistema AI — distinto de DPIA (que cobre só data protection).”

    6 inputs, 3 required
    • aiSystemIdstringrequired
    • systemNamestringrequired“Nome legível do sistema AI”
    • systemPurposestringrequired“Finalidade declarada”
    • humanRightsImpactobject“Self-declared dimensões de impacto a direitos humanos”
    • affectedPopulationsarray“Populações afetadas (e.g.”
    • jurisdictionstring“Jurisdição target (default: CAIDP-UG cross-jurisdictional)”
  • report_ai_incident

    “Estrutura um AI incident report aligned com AIAAIC Repository / AI Incident Database (referenciado pelo CAIDP no UN Global Dialogue submission).”

    9 inputs, 5 required
    • aiSystemIdstringrequired“sha256 hex (32B) ou opaque ID do sistema AI”
    • incidentTypestringrequired
    • harmClassificationstringrequired
    • affectedCountnumber“Número estimado de pessoas afetadas (use 0 se desconhecido)”
    • jurisdictionstring“Jurisdição primária do incidente”
    • evidenceUristring“URI (IPFS/https/ar://) de evidence bundle”
    • severitynumberrequired“1=baixo, 5=crítico (CAIDP threshold ≥4 → UN SR escalation)”
    • occurredAtstring“ISO 8601 timestamp”
    • summarystringrequired“Resumo factual em 1-3 frases”
  • caidp_ai_index_score

    “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, hu…”

    2 inputs, 2 required
    • organizationNamestringrequired
    • indicatorsobjectrequired“10 booleans/scores 0-1 por indicador.”
  • submit_composed_attestation

    “Composed Stack: submete attestation compressed atomicamente — Shadow Drive upload (immutable) + SP1 verify CPI + Light Protocol leaf insert + Squads vault authority gating.”

    12 inputs, 11 required
    • subjectstringrequired“Subject pubkey base58 (a quem a attestation se refere).”
    • commitmentHexstringrequired“32-byte ZK commitment hex (deve bater com publicInputs[32..64]).”
    • proofHexstringrequired“356-byte SP1 v6 Groth16 proof (hex).”
    • publicInputsHexstringrequired“96-byte ABI-encoded PublicValuesStruct (hex).”
    • payloadBase64stringrequired“Payload completo (DPIA PDF, evidence JSON, etc.) em base64.”
    • payloadFilenamestringrequired“Filename pro Shadow Drive (deve incluir extensão, ex: dpia-q2-2026.pdf).”
    • jurisdictionstringrequired“Jurisdição (mapeada pra code 0..14 no leaf).”
    • authorityPubkeystringrequired“Squads vault[3] Compliance Authority PDA (pode revocar).”
    • stateTreePubkeystringrequired“Light Protocol State Tree pubkey (alocada via scripts/init-cmt.ts; lookup em scripts/cmt-config.json).”
    • stateQueuePubkeystringrequired“Light Protocol State Queue pubkey paired with stateTreePubkey.”
    • shdwStorageAccountstringrequired“Shadow Drive storage account pubkey (alocado via scripts/init-shdw-storage-account.ts).”
    • expiresAtnumber“Unix timestamp expiração; omitir = no expiry (i64::MAX).”
  • fetch_composed_attestation

    “Fetch compressed attestation por leaf hash via Photon Indexer.”

    2 inputs, 1 required
    • leafHashHexstringrequired“32-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.”
  • revoke_composed_attestation

    “Revoke compressed attestation via Squads v4 proposal.”

    4 inputs, 4 required
    • oldLeafHexstringrequired“252-byte AttestationLeaf serializado (hex).”
    • expectedOldLeafHashHexstringrequired“32-byte leaf hash do oldLeaf (retornado por fetch_composed_attestation).”
    • revokeReasonnumberrequired“Reason code 0..255 (mapping em docs/GOVERNANCE.md).”
    • squadsMultisigPubkeystringrequired“Squads v4 multisig PDA (vault[3] Compliance Authority) — lookup em scripts/squads-config.json.”
  • resolve_legal_citation

    “Resolve uma citação legal (URN LexML, número de lei, ou trecho do título) contra o corpus oficial sincronizado pelo dpo2u-legal-worker.”

    3 inputs, 2 required
    • jurisdictionstringrequired“Código DPO2U da jurisdição (LGPD, GDPR, MICAR, DPDP, APPI, PIPA, PDP-ID, Malaysia-PDPA, Vietnam-Decree-13, PDPA-SG, PIPEDA, CCPA, LFPDPPP, POPIA, PDPL-UAE, Bri…”
    • citationstringrequired“A citação a buscar.”
    • includeTextboolean“Se true (default), retorna o texto completo do documento.”
  • verify_corpus_manifest_onchain

    “Cross-checks the legal-worker corpus output against the on-chain legal_source_manifest PDA for a given jurisdiction.”

    1 input, 1 required
    • jurisdictionstringrequired“Worker jurisdiction code (LGPD, GDPR, MICAR, POPIA, DPDP, APPI, PIPA, PDP-ID, Malaysia-PDPA, Vietnam-Decree-13, PDPA-SG, PIPEDA, CCPA, LFPDPPP, PDPL-UAE, Bribe…”
  • generate_lgpd_kit

    “Gera um Kit LGPD completo (schema: dpo2u/lgpd/v1) e realiza o Blind Upload (cifrado via AES-256) para o IPFS/Lighthouse.”

    6 inputs, 6 required
    • companyNamestringrequired“Nome da empresa (Data Controller)”
    • companyIdstringrequired“CNPJ ou DID da empresa”
    • dpoContactstringrequired“Email de contato do DPO”
    • retentionDaysnumberrequired“Dias de retenção da política de dados”
    • dataCategoriesarrayrequired“Categorias de dados tratados (ex: financeiro, biometrico)”
    • consentMechanismstringrequired“Mecanismo de consentimento (ex: opt-in-explicito)”
  • check_compliance_status

    “Auth-Check de conformidade por CNPJ/DID.”

    1 input, 1 required
    • companyIdstringrequired“CNPJ ou DID da empresa alvo”
  • generate_document_package

    “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.”

    2 inputs, 1 required
    • dossierobjectrequired“EngagementDossier conforme strix/engagement/v1.”
    • includeZipboolean“Se true, retorna o zip do pacote em base64 (payload grande).”
  • dpo2u_check_counterparty

    “Check before you pay: antes de pagar ou transferir, confere se a contraparte tem passaporte DPO2U válido.”

    4 inputs, 1 required
    • passport_idstringrequired“Passaporte DPO2U da contraparte”
    • marketstring“Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US).”
    • transfer_idstring“Opcional: id da transferência (bytes32 hex).”
    • x_paymentstring“Opcional.”
  • dpo2u_agent_compliance

    “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.”

    6 inputs, 1 required
    • marketstringrequired“Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US).”
    • institution_typestring
    • servicesarray
    • covered_rulesarray“Ids das regras que o dono já declara cobertas”
    • repo_urlstring“Opcional: repositório público (owner/repo ou URL do GitHub)”
    • x_paymentstring“Opcional.”
  • dpo2u_counterparty_due_diligence

    “Due diligence da contraparte: passaporte, pacotes exigidos pelo mercado e cobertura, patrocínios ativos, histórico e prova; report_hash é o recibo.”

    6 inputs, 2 required
    • passport_idstringrequired
    • marketstringrequired“Mercado (ISO 3166-1 alfa-2, ex.: BR, PT, US).”
    • institution_typestring
    • servicesarray
    • transfer_idstring“Opcional: id da transferência (bytes32 hex).”
    • x_paymentstring“Opcional.”
  • dpo2u_pentest

    “Pentest pedido por um agente.”

    6 inputs, 1 required
    • actionstringrequired
    • domainstring“action=order: domínio público”
    • tierstring“action=order: padrão passive”
    • order_idstring“verify/run/status”
    • order_tokenstring“verify/run/status: devolvido no order”
    • x_paymentstring“Opcional.”
  • encrypted_reporting

    “SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração.”

    5 inputs, 3 required
    • report_typestringrequired“Type of encrypted report to generate”
    • organizationstringrequired“Organization name for the report”
    • time_periodstringrequired“Reporting time period”
    • include_benchmarksboolean“Include industry benchmark comparisons”
    • privacy_levelstring“Privacy protection level”
  • private_benchmark

    “SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração.”

    6 inputs, 4 required
    • benchmark_typestringrequired“Type of benchmark comparison”
    • industry_sectorstringrequired“Industry sector for comparison”
    • organization_sizestringrequired“Organization size category”
    • comparison_metricsarrayrequired“Specific metrics to compare”
    • anonymity_levelstring“Anonymity protection level”
    • include_positioningboolean“Include competitive positioning analysis”
  • zk_compliance_proof

    “SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração.”

    6 inputs, 4 required
    • proof_typestringrequired“Type of zero-knowledge proof to generate”
    • claim_statementstringrequired“Compliance claim to prove cryptographically”
    • evidence_categoriesarrayrequired“Categories of evidence supporting the claim”
    • regulationsarrayrequired“Relevant regulations (e.g., LGPD, GDPR)”
    • proof_schemestring“Cryptographic proof scheme to use”
    • verification_levelstring“Verification level for the proof”
  • fhe_executive_dashboard

    “SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração.”

    6 inputs, 3 required
    • dashboard_typestringrequired“Type of executive dashboard”
    • time_horizonstringrequired“Time horizon for dashboard metrics”
    • kpi_categoriesarrayrequired“KPI categories to include in dashboard”
    • include_trendsboolean“Include historical trend analysis”
    • include_forecastsboolean“Include predictive forecasting”
    • privacy_levelstring“Privacy level for executive presentation”
  • homomorphic_analytics

    “Perform privacy-preserving analytics on encrypted data without ever decrypting sensitive information”

    5 inputs, 2 required
    • analysis_typestringrequired“Type of homomorphic analysis to perform”
    • data_sourcestringrequired“Source system or dataset identifier”
    • encrypt_inputboolean“Encrypt input data before analysis”
    • multi_partyboolean“Enable multi-party computation”
    • partiesarray“Organizations participating in multi-party analysis”
  • secure_data_sharing

    “SIMULAÇÃO: valores sintéticos gerados pela própria tool para demonstração.”

    5 inputs, 4 required
    • sharing_typestringrequired“Type of secure data sharing”
    • organizationsarrayrequired“Organizations participating in data sharing”
    • data_categoriesarrayrequired“Categories of data to be shared securely”
    • purposestringrequired“Purpose and legal basis for data sharing”
    • retention_daysnumber“Data retention period in days”
  • automated_remediation

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

    6 inputs, 4 required
    • remediation_scopestringrequired“Scope of compliance gaps to address”
    • audit_report_idstring“ID of audit report to use as baseline (optional)”
    • auto_applybooleanrequired“Automatically apply corrections (false for planning only)”
    • dry_runbooleanrequired“Simulate remediation without making changes”
    • compliance_targetnumberrequired“Target compliance score (0-100)”
    • include_evidenceboolean“Generate cryptographic evidence of improvements”
  • audit_infrastructure

    “Performs complete infrastructure audit to identify personal data and compliance gaps”

    11 inputs, 3 required
    • targetstringrequired“Target system to audit”
    • depthstringrequired“Audit depth level”
    • compliancearrayrequired“Regulations to check (LGPD, GDPR)”
    • generateReportboolean“Generate executive report”
    • hasEncryptionboolean“Criptografia em repouso configurada”
    • hasAccessControlsboolean“Controles de acesso RBAC/ABAC”
    • hasBackupboolean“Rotina de backup testada”
    • hasAuditProgramboolean“Programa de auditoria periódico”
    • hasIncidentResponsePlanboolean“Plano de resposta a incidentes”
    • hasDataBreachProtocolboolean“Protocolo de notificação de violação”
    • inventarioarray“Inventário de dados pessoais encontrados (opcional)”
  • “Assess privacy and compliance risk levels”

    11 inputs, 3 required
    • targetstringrequired“Target system to audit”
    • depthstringrequired“Audit depth level”
    • compliancearrayrequired“Regulations to check (LGPD, GDPR)”
    • generateReportboolean“Generate executive report”
    • hasEncryptionboolean“Criptografia em repouso configurada”
    • hasAccessControlsboolean“Controles de acesso RBAC/ABAC”
    • hasBackupboolean“Rotina de backup testada”
    • hasAuditProgramboolean“Programa de auditoria periódico”
    • hasIncidentResponsePlanboolean“Plano de resposta a incidentes”
    • hasDataBreachProtocolboolean“Protocolo de notificação de violação”
    • inventarioarray“Inventário de dados pessoais encontrados (opcional)”
  • analyze_contracton 3 other servers

    “Analyze contracts for data protection compliance (LGPD/GDPR)”

    3 inputs, 1 required
    • contractTextstringrequired“Contract text to analyze”
    • analysisTypestring“Type of analysis”
    • regulationsarray“Regulations to check against”
  • simulate_breach

    “Simulate a data breach scenario”

    2 inputs
    • scenariostring“Breach scenario type”
    • affectedRecordsnumber“Number of affected records”
  • verify_consent

    “Verify consent mechanisms”

    2 inputs
    • consentTypestring“Type of consent to verify”
    • userIdstring“User ID for consent verification”
  • setup_company

    “Setup company for LGPD compliance with DPO registration”

    15 inputs, 13 required
    • companyNamestringrequired“Company name”
    • cnpjstringrequired“CNPJ (14 digits)”
    • emailstringrequired“Company email”
    • phonestringrequired“Company phone”
    • websitestring“Company website”
    • sectorstringrequired“Business sector”
    • companySizestringrequired“Company size”
    • dpoNamestringrequired“DPO full name”
    • dpoEmailstringrequired“DPO email”
    • dpoPhonestringrequired“DPO phone”
    • addressStreetstringrequired“Street address”
    • addressCitystringrequired“City”
    • addressStatestringrequired“State”
    • addressZipCodestringrequired“ZIP code”
    • lgpdChecklistobject

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-17.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
88% of 489
Tools with a description
100% of 83
Typical description length
255 characters

The tool set

Counted from the listing

Tools
83
Size of the list
about 23,258 tokens for an agent to load (characters ÷ 4)
Naming
83 of 83 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 83 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-17 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.dpo2u.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "dpo2u": {
      "url": "https://mcp.dpo2u.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "dpo2u": {
      "type": "http",
      "url": "https://mcp.dpo2u.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"dpo2u","type":"http","url":"https://mcp.dpo2u.com/mcp"}'
Claude Code
claude mcp add --transport http dpo2u https://mcp.dpo2u.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "dpo2u": {
      "type": "streamableHttp",
      "url": "https://mcp.dpo2u.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "dpo2u": {
      "httpUrl": "https://mcp.dpo2u.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.dpo2u]
url = "https://mcp.dpo2u.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "dpo2u": {
      "url": "https://mcp.dpo2u.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.dpo2u.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

  • security.txt. No security.txt at https://mcp.dpo2u.com/.well-known/ (HTTP 404, 2026-11-17). No security.txt at https://dpo2u.com/.well-known/ (HTTP 404, 2026-11-17). Source: mcp.dpo2u.com/.well-known/security.txt · read 2026-11-17.
  • A2A agent card. No A2A agent card at https://mcp.dpo2u.com/.well-known/ (HTTP 404, 2026-11-17). No A2A agent card at https://dpo2u.com/.well-known/ (HTTP 404, 2026-11-17). Source: mcp.dpo2u.com/.well-known/agent-card.json · read 2026-11-17.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.dpo2u.com/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17
Repository github.com/fredericosanntana/DPO2UDoes not open (not found or private)differsapi.github.com · 2026-11-17

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.fredericosanntana
Repository
github.com/fredericosanntana/DPO2U — does not open publicly
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-17; security policy read from GitHub · 2026-11-17.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe linked repository returned HTTP 404: it does not exist or is private.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17 (security policy 2026-11-17). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.fredericosanntana/dpo2u

Answered from the data above

Who publishes io.github.fredericosanntana/dpo2u?

The registry ties the namespace io.github.fredericosanntana to the GitHub account fredericosanntana; only its owner can publish under it. Its linked repository, github.com/fredericosanntana/DPO2U, does not open publicly (missing or private). These are facts from the registry and GitHub, not a rating.

Is io.github.fredericosanntana/dpo2u safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: The repository it links to does not open publicly, so its code cannot be inspected through that link. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.fredericosanntana/dpo2u need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.fredericosanntana/dpo2u been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does io.github.fredericosanntana/dpo2u publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.fredericosanntana/dpo2u?

The registry links to github.com/fredericosanntana/DPO2U, but that link does not open publicly, so the code cannot be inspected through it.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-17, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,507 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 83 tools, 0 resources, 0 prompts.
  4. 14,111 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository
Hosting type
registry · 2026-11-17
MCP capability
tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
not stated
repository link is dead (HTTP 404), so activity cannot be read
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.fredericosanntana/dpo2u: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/io.github.fredericosanntana/dpo2u

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.fredericosanntana/dpo2u)](https://protocolprobe.com/mcp/servers/io.github.fredericosanntana/dpo2u)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology