Is the DPO2U compliance MCP server down?

mcp-registry/io.github.fredericosanntana/dpo2u · registry v1.2.0 · server reports v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 15:44 UTC · handshake 728ms

As of 2026-11-22 15:44 UTC, the DPO2U compliance MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
796
outages (90d)
0
tools
83

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

Point your MCP client at this streamable-http endpoint: https://mcp.dpo2u.com/mcp

Agent-readiness: D (65/100)

D (65/100): 0 error(s), 6 warning(s) across 83 tool(s); ~25,904 tokens of tool definitions.
Scores higher than 2% of 27,590 MCP servers Glimind has audited.
Its tool list costs an agent ~25,904 tokens per session — more than 95% of servers.
65 → 65 since 2026-11-16
no tool-poisoning patterns
Descriptions77
Safety hints6
Schemas100
Protocol100
Stability96
Token cost24
Reliability100
Client compatibility70

What to fix (8)

1 tool definition(s) exceed ~1,200 tokens each (largest: multi_jurisdiction_compliance_check, ~1,207).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~607 tokens every session. How to fix →

Tools: multi_jurisdiction_compliance_check · saves ~607 tokens/session

83 of 83 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: analyze_contract, assess_agent_capability, assess_risk, audit_ai_governance, audit_ai_red_lines and 78 more

83 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

61 parameter(s) across 15 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: assess_agent_capability, caidp_ai_index_score, cvm_generate_disclosure, cvm_generate_zk_proof, dpo2u_agent_compliance and 10 more

15 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_dpo_report, erase_attestation_payload, fhe_executive_dashboard, generate_runtime_enforcement_plan, revoke_compliance_attestation and 10 more

Loading this server's tool list costs an agent ~25,904 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 33 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 15 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.fredericosanntana%2Fdpo2u/fixes

analyze_contract 1 change
{
  "name": "analyze_contract",
  "description": "Analyze contracts for data protection compliance (LGPD/GDPR)",
  "inputSchema": {
    "type": "object",
    "required": [
      "contractText"
    ],
    "properties": {
      "regulations": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Regulations to check against"
      },
      "analysisType": {
        "enum": [
          "compliance",
          "risks",
          "full"
        ],
        "type": "string",
        "description": "Type of analysis"
      },
      "contractText": {
        "type": "string",
        "description": "Contract text to analyze"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
calculate_privacy_score 1 change
{
  "name": "calculate_privacy_score",
  "description": "Calcula score de maturidade LGPD/GDPR (0-100) com análise detalhada por categoria",
  "inputSchema": {
    "type": "object",
    "required": [
      "company"
    ],
    "properties": {
      "hasDPO": {
        "type": "boolean",
        "description": "Possui DPO designado?"
      },
      "company": {
        "type": "string",
        "description": "Nome da empresa"
      },
      "industry": {
        "type": "string",
        "description": "Setor de atuação"
      },
      "vertical": {
        "enum": [
          "defi-casp",
          "rwa-issuer",
          "payment-processor",
          "neobank",
          "agritech",
          "ai-agent",
          "b2b-saas",
          "mobile-wallet"
        ],
        "type": "string",
        "description": "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)."
      },
      "hasDPOReport": {
        "type": "boolean",
        "description": "Possui relatório DPO?"
      },
      "jurisdiction": {
        "enum": [
          "LGPD",
          "GDPR",
          "DPDP",
          "MICAR",
          "MICAR-CASP",
          "PDPA",
          "UAE",
          "POPIA",
          "NDPA",
          "CCPA",
          "PIPEDA",
          "LAW25",
          "PIPA",
          "PDP",
          "APPI",
          "MEXICO",
          "VIETNAM",
          "MALAYSIA",
          "KENYA",
          "GHANA",
          "COLOMBIA",
          "TANZANIA",
          "RWANDA",
          "UGANDA",
          "ARGENTINA"
        ],
        "type": "string",
        "description": "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."
      },
      "hasDataMapping": {
        "type": "boolean",
        "description": "Possui mapeamento de dados?"
      },
      "hasAuditProgram": {
        "type": "boolean",
        "description": "Possui programa de auditoria?"
      },
      "hasCookieConsent": {
        "type": "boolean",
        "description": "Possui consentimento de cookies?"
      },
      "hasPrivacyPolicy": {
        "type": "boolean",
        "description": "Possui política de privacidade?"
      },
      "hasDataBreachProtocol": {
        "type": "boolean",
        "description": "Possui protocolo de violação?"
      },
      "internationalTransfer": {
        "type": "boolean",
        "description": "Transferência internacional?"
      },
      "hasDataRetentionPolicy": {
        "type": "boolean",
        "description": "Possui política de retenção?"
      },
      "hasIncidentResponsePlan": {
        "type": "boolean",
        "description": "Possui plano de resposta a incidentes?"
      },
      "employeeTrainingFrequency": {
        "enum": [
          "none",
          "annual",
          "semiannual",
          "quarterly"
        ],
        "type": "string",
        "description": "Frequência de treinamento"
      },
      "hasDataProcessingAgreement": {
        "type": "boolean",
        "description": "Possui acordos de processamento?"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_compliance 1 change
{
  "name": "check_compliance",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "company",
      "auditScope"
    ],
    "properties": {
      "cnpj": {
        "type": "string",
        "description": "CNPJ (opcional, contexto BR)"
      },
      "company": {
        "type": "string",
        "description": "Nome da empresa"
      },
      "framework": {
        "enum": [
          "LGPD",
          "GDPR",
          "Ambos"
        ],
        "type": "string",
        "description": "[DEPRECATED — use \"jurisdiction\" instead] Legacy parameter. Aceito como alias retro-compatível: LGPD/GDPR mapeiam direto para jurisdiction; \"Ambos\" gera report combinado LGPD+GDPR."
      },
      "auditScope": {
        "type": "string",
        "description": "Escopo da auditoria"
      },
      "auditorName": {
        "type": "string",
        "description": "Nome do auditor"
      },
      "auditorRole": {
        "type": "string",
        "description": "Cargo do auditor"
      },
      "jurisdiction": {
        "enum": [
          "LGPD",
          "GDPR",
          "MICAR",
          "MICAR-CASP",
          "DPDP",
          "PDPA",
          "UAE",
          "PDPL",
          "POPIA",
          "NDPA",
          "CCPA",
          "PIPEDA",
          "LAW25",
          "PIPA",
          "PDP",
          "APPI",
          "ART",
          "CASP",
          "MEXICO",
          "VIETNAM",
          "MALAYSIA",
          "KENYA",
          "GHANA",
          "COLOMBIA",
          "TANZANIA",
          "RWANDA",
          "UGANDA",
          "ARGENTINA"
        ],
        "type": "string",
        "description": "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/ART) retornam KB snapshot + suggestedNextCall para compare_jurisdictions. APPI (JP) é a 15ª jurisdição (Sprint E 2026-05-04) — Act 57/2003 + amendments 2022 + My Number Act + EU/UK dual adequacy."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.fredericosanntana/dpo2u"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.fredericosanntana/dpo2u"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.fredericosanntana%2Fdpo2u.svg)](https://glimind.com/server/mcp-registry%2Fio.github.fredericosanntana%2Fdpo2u?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.fredericosanntana%2Fdpo2u?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.fredericosanntana%2Fdpo2u.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6861cba86b334f3e…, first seen 2026-11-18, included at leaf 333594 of 384,303. Version history · verify what your client received.

Tools (83)

Compare: most reliable knowledge servers · most reliable security servers · most reliable other servers · most reliable retrieval servers · most reliable legal servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the DPO2U compliance MCP server down right now?

As of 2026-11-22 15:44 UTC, the DPO2U compliance MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does DPO2U compliance MCP server provide?

DPO2U compliance MCP server advertises 83 tools, including analyze_contract, assess_agent_capability, assess_risk, audit_ai_governance, audit_ai_red_lines.

How do I install DPO2U compliance MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.dpo2u.com/mcp

Is the DPO2U compliance MCP server safe to connect to an AI agent?

Glimind scanned all 83 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of DPO2U compliance MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve