mcp-registry/io.github.fredericosanntana/dpo2u · registry v1.2.0 · server reports v1.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs 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.
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
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 →
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 →
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 →
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 →
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 →
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
{
"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
}
}{
"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
}
}{
"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 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.
multi_jurisdiction_compliance_check ~1,207 tokensevaluate_project_compliance ~1,092 tokensaudit_ai_governance ~706 tokenssubmit_composed_attestation ~632 tokenscalculate_privacy_score ~609 tokensStatic 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.fredericosanntana%2Fdpo2u?ref=badge)
<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>
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.
Compare: most reliable knowledge servers · most reliable security servers · most reliable other servers · most reliable retrieval servers · most reliable legal servers
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.
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"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
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.
DPO2U compliance MCP server advertises 83 tools, including analyze_contract, assess_agent_capability, assess_risk, audit_ai_governance, audit_ai_red_lines.
Point your MCP client at this streamable-http endpoint: https://mcp.dpo2u.com/mcp
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.
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.