Mydatapass

io.github.mydatapass由 GitHub 账号 mydatapass 发布v0.1.0更新于 Oct 24, 2026

Neutral escrow for customer-data offboarding (GDPR/EU Data Act): query MyDataPass facts.

已验证Streamable HTTP可网页运行安全与监控商业与电商

概览

AI 生成的概览

一个远程 MCP 服务器，用于回答有关 MyDataPass 的问题；该服务是面向 GDPR 与欧盟数据法客户数据迁出的中立托管方。

可以做什么
说明 MyDataPass 是什么、它定义的类别及适用对象，并介绍如何离线验证交付证书以及迁出流程最终向客户交付什么。
适用场景
在评估 MyDataPass 作为迁出或托管服务商、比较其产品与公开价格，或查询它与 GDPR、欧盟数据法等隐私法规的关系时使用。
运行要求
远程 streamable HTTP 端点；未声明任何软件包、账户、API 密钥或环境变量。
安装前请注意
这是只读的信息型服务器，内容来自单一厂商对其自身服务的介绍，应视为厂商材料而非独立意见。它本身不解密或验证导出包，那需要另外的离线工具和口令。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mydatapass，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.mydatapass%2Fmydatapass/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "mydatapass": {
      "type": "http",
      "url": "https://mcp.mydatapass.app/api/mcp"
    }
  }
}

README

mydatapass-verify

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.

Why this repo exists

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:

  • Your security team can review exactly how packages are encrypted before signing anything.
  • Recipients can decrypt and verify integrity offline, with no MyDataPass servers involved.
  • If MyDataPass disappeared tomorrow, every delivered package would remain fully recoverable with the passphrase and this tooling.

Transparency log: retention and closure commitment

Every signed certificate's SHA-256 fingerprint is appended to the public transparency log at mydatapass.app/transparency. The log holds hashes only, no customer data.

  • Retention: each log entry is kept for at least 5 years from the date it was added, and for as long as MyDataPass operates.
  • If MyDataPass ceases operations: we will publish a final copy of the complete log in a public archive (this repository, or a public archive linked from it), so every certificate remains checkable against the log without us.

The full certificate record (with the names of the parties) is kept for a fixed period per service and then reduced to its hash; the periods are in our Terms (§ 8) and DPA (Annex 1). A signed certificate stays verifiable offline with its signature, qualified time stamp and anchor, so keep your own copy.

What's in an export package

A MyDataPass package is a JSON file with four fields:

FieldDescription
ciphertext_b64AES-256-GCM ciphertext, Base64
iv_b6412-byte random nonce, Base64
salt_b6416-byte random KDF salt, Base64
hash_sha256SHA-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.

Verify an export

Option A — browser, fully offline

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.

Option B — command line

Requires Python 3.9+ and the cryptography package:

bash
pip install cryptographypython 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.

What this repo is NOT

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: [email protected].

License

MIT — see LICENSE.

来源：README.md，提交 0775972

工具

5

about_mydatapass

What MyDataPass is, the category it defines, and who it is for.

无需输入参数。

get_pricing

MyDataPass products and public prices: Exit, Exit Evidence Sprint, Exit-Ready and Enclave.

无需输入参数。

check_compliance_requirement

Check how MyDataPass relates to a data/privacy regulation (e.g. 'GDPR', 'EU Data Act', 'Article 20').

输入参数regulation必填

get_offboarding_guide

The step-by-step offboarding flow and what the client ultimately receives.

无需输入参数。

verify_certificate

Explain how to independently verify a MyDataPass delivery certificate (offline).

输入参数token

版本历史

1
  1. v0.1.0最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分