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 分