io.github.mydatapass/mydatapass is an MCP server published by io.github.mydatapass, hosted at mcp.mydatapass.app. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including about_mydatapass, get_pricing, check_compliance_requirement, get_offboarding_guide, verify_certificate.
Neutral escrow for customer-data offboarding (GDPR/EU Data Act): query MyDataPass facts.
972 connections through 5 shared values. Tap any node.
What MyDataPass is: the exit evidence platform for ICT provider contracts (DORA, EU Data Act, PRA SS2/21), for regulated firms and their providers.
No parameters.
{
"name": "about_mydatapass",
"description": "What MyDataPass is: the exit evidence platform for ICT provider contracts (DORA, EU Data Act, PRA SS2/21), for regulated firms and their providers.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}
}MyDataPass plans (Free, Pack 5, Corporate, Sprint), what each includes and the public pricing page.
No parameters.
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
{
"name": "get_pricing",
"description": "MyDataPass plans (Free, Pack 5, Corporate, Sprint), what each includes and the public pricing page.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}
}Check how MyDataPass relates to a regulation on ICT provider exit (e.g. 'DORA', 'EU Data Act', 'PRA SS2/21', 'GDPR Art. 28').
| Parameter | Type | Description |
|---|---|---|
| regulation * | string | Regulation or article name, e.g. 'DORA Art. 28' |
{
"name": "check_compliance_requirement",
"description": "Check how MyDataPass relates to a regulation on ICT provider exit (e.g. 'DORA', 'EU Data Act', 'PRA SS2/21', 'GDPR Art. 28').",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"regulation"
],
"properties": {
"regulation": {
"type": "string",
"description": "Regulation or article name, e.g. 'DORA Art. 28'"
}
}
}
}How the exit of one ICT provider contract runs on MyDataPass, step by step, and the evidence each party receives.
No parameters.
{
"name": "get_offboarding_guide",
"description": "How the exit of one ICT provider contract runs on MyDataPass, step by step, and the evidence each party receives.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}
}Explain how an auditor, supervisor or customer verifies a MyDataPass certificate offline, without trusting MyDataPass.
| Parameter | Type | Description |
|---|---|---|
| token | string | Optional share token; verification is done with the offline tool |
{
"name": "verify_certificate",
"description": "Explain how an auditor, supervisor or customer verifies a MyDataPass certificate offline, without trusting MyDataPass.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"token": {
"type": "string",
"description": "Optional share token; verification is done with the offline tool"
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.