Server data from the Official MCP Registry
Neutral escrow for customer-data offboarding (GDPR/EU Data Act): query MyDataPass facts.
Neutral escrow for customer-data offboarding (GDPR/EU Data Act): query MyDataPass facts.
Remote endpoints: streamable-http: https://mcp.mydatapass.app/api/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
5 tools verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-mydatapass-mydatapass": {
"url": "https://mcp.mydatapass.app/api/mcp"
}
}
}From the project's GitHub README.
Independently verify a MyDataPass export — without trusting us.
MyDataPass delivers customer data offboarding exports as encrypted, audit-logged packages. This repository contains everything a recipient (or their security team) needs to decrypt and verify an export with zero MyDataPass involvement: the package format specification and two standalone verifiers.
Our security model does not rely on secrecy of the format — it relies on the strength of the passphrase and standard, auditable cryptography. Publishing the format and the verification tooling means:
A MyDataPass package is a JSON file with four fields:
| Field | Description |
|---|---|
ciphertext_b64 | AES-256-GCM ciphertext, Base64 |
iv_b64 | 12-byte random nonce, Base64 |
salt_b64 | 16-byte random KDF salt, Base64 |
hash_sha256 | SHA-256 hex digest of the original plaintext |
Encryption: AES-256-GCM. Key derivation: PBKDF2-HMAC-SHA256, 310,000 iterations, 32-byte key. Full details in docs/export-format.md.
Open verify.html in any modern browser (works from file://, no network requests are made). Select the package file, enter the passphrase, and the page decrypts via WebCrypto and checks the SHA-256 digest locally.
Requires Python 3.9+ and the cryptography package:
pip install cryptography
python verify.py package.json --out exported-data.bin
The script prompts for the passphrase, decrypts, and confirms the plaintext digest matches hash_sha256. Exit code 0 means the package is authentic and intact; any tampering with the ciphertext fails GCM authentication.
This is not the MyDataPass product source code. It is the public, auditable surface: the delivery format, the verification tooling, and our security model. Questions or responsible disclosure: silvia@mydatapass.pro.
MIT — see LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.