ZTDS Reference

MCP开发工具

提供方 未标注

开发工具 未标注 未标注 官方维护 Claude DesktopClaudeCursorVS Code
查看接入方式

零信任数据清洗参考MCP服务器,适用于Cursor和Claude Desktop。本地内存中的PII去标识化和确定性替代令牌化(RFC v1.0)。

一句话选型结论

按资料字段整理

ZTDS Reference 属于开发工具类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 官方维护 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

开发

安装与配置

未标注 未标注
上游未给出传输方式
{ "mcpServers": { "ztds": { "command": "npx", "args": ["-y", "ztds-mcp"] } } }

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
ZTDS Reference当前 未标注 未标注 未标注 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方官方维护核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

7.1 KB
来自项目仓库与上游目录的原文,未做删改

ZTDS MCP Server (ztds-mcp)

Local Security Firewall for AI Agents & IDEs (Cursor, Claude Code, Windsurf)

Open-source reference implementation of the Zero-Trust Data Sanitization (ZTDS) protocol for the Model Context Protocol (MCP) ecosystem. Conforms to the open architectural specification RFC v1.0 and IETF Standards Track sibiryakov-ztds-protocol.

Runs 100% locally in device volatile memory (RAM) with zero network calls, zero external subprocessors, zero disk writes, and zero telemetry.


1-Click Quickstart (Automated Setup)

Auto-configure your installed AI IDEs and clients with a single command:```bash
npx ztds-mcp init


The configurator automatically:
1. Detects installed clients: **Cursor IDE**, **Claude Desktop**, and **Windsurf**.
2. Creates or safely merges the `ztds` server block into their local configuration files.
3. Executes an in-memory cryptographic self-test to verify zero-leakage tokenization.

To verify existing client configurations:```bash
npx ztds-mcp status

Standalone CLI Pre-Execution Auditor

Audit sensitive files, configuration directories, or CI/CD pipelines for credential leakage prior to AI agent ingestion:```bash

Scan a single sensitive file

npx ztds-mcp audit .env

Scan an entire repository/source directory

npx ztds-mcp audit ./src

Machine-readable JSON output for CI/CD gates (exits 1 on violation)

npx ztds-mcp audit --json


Outputs line-by-line category breakdowns, risk assessment, and cryptographic SHA-256 attestation receipts.

---

## Why AI IDEs Leak Data & How ZTDS Stops It

Autonomous agents in modern IDEs (Cursor, Claude Code, Windsurf) routinely index repository files, including `.env` secrets, database credentials, production logs, customer emails, and API keys. When an agent crafts a prompt or calls a tool, these sensitive strings are transmitted in cleartext across the internet to frontier LLM APIs.

**ZTDS MCP acts as an in-memory local security firewall**:
- **Intercepts**: Tools and prompt text are evaluated inside client RAM prior to transmission.
- **De-identifies**: Real credentials and PII are replaced with bijective, context-preserving synthetic tokens (`[API_SECRET_TOKEN_1]`, `[EMAIL_TOKEN_1]`).
- **Restores**: When the model returns code or instructions containing synthetic tokens, the local MCP server re-maps the cleartext back into the IDE response.
- **Zero Egress**: Real private keys and customer data never touch the network unmasked.

---

## The 4 Core Protocol Invariants

1. **Invariant 1: Zero External Egress Prior to Sanitization**
   Cleartext PII, PHI, and credentials never cross the local execution boundary unmasked.
2. **Invariant 2: Deterministic Context-Preserving Reversible Tokenization**
   Sensitive values are replaced by synthetic tokens maintaining syntactic and semantic context for LLMs.
3. **Invariant 3: Verifiable Ephemeral RAM Isolation (Theorem 2 Zeroization)**
   Mapping tables exist strictly in volatile memory and are zeroized upon session termination.
4. **Invariant 4: Subprocessor Chain Exclusion**
   Operates strictly as a local computational utility under GDPR Recital 26, rendering Data Processing Agreements (DPAs) unnecessary.

---

## Manual Client Configuration

If you prefer configuring your clients manually without `npx ztds-mcp init`:

### 1. Claude Desktop

Add to `claude_desktop_config.json`:```json
{
  "mcpServers": {
    "ztds": {
      "command": "npx",
      "args": ["-y", "ztds-mcp"]
    }
  }
}

Config file locations:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- Linux: ~/.config/Claude/claude_desktop_config.json

2. Cursor IDE

Add to .cursor/mcp.json in your workspace root:```json
{
"mcpServers": {
"ztds": {
"command": "npx",
"args": ["-y", "ztds-mcp"]
}
}
}


### 3. Windsurf / Codeium

Add to `~/.codeium/windsurf/mcp_config.json`:```json
{
  "mcpServers": {
    "ztds": {
      "command": "npx",
      "args": ["-y", "ztds-mcp"]
    }
  }
}

Available MCP Tools, Resources & Prompts

MCP Tools (tools/list & tools/call)

Tool Input Schema Description
ztds_sanitize { text: string, sessionId?: string } Masks sensitive PII/credentials with deterministic surrogate tokens prior to LLM transmission.
ztds_restore { text: string, sessionId?: string } Restores original cleartext from volatile in-memory mapping into LLM output.
ztds_audit { text: string } Scans text for exposed credentials and PII, returning SHA-256 integrity receipt and risk score.
ztds_info {} Retrieves RFC v1.0 standard details, academic citations, and enterprise documentation.
ztds_reset_session { sessionId?: string } Purges and zeroizes all volatile session token mappings (Theorem 2).

MCP Resources (resources/list & resources/read)

Resource URI MIME Type Description
ztds://spec/rfc-v1 application/json Formal ZTDS RFC v1.0 / IETF draft-sibiryakov-ztds-protocol specification and 4 core invariants.
ztds://session/telemetry application/json Real-time volatile RAM session count and zero-egress attestation status.

MCP Prompts (prompts/list & prompts/get)

Prompt Arguments Description
ztds_guard task (string, required) Activates the ZTDS Zero-Trust Data Sanitization guardrail in Claude or Cursor.

Certified Commercial Reference Implementation (PrivacyScrubber)

ZTDS is an open, vendor-neutral standard. The open-source ztds-mcp package serves as the reference implementation covering universal baseline entities (Email, Phone, SSN, Credit Cards, IPv4, IBAN, API Secrets).

For production enterprise workloads requiring continuous regulatory compliance and air-gapped guarantees, PrivacyScrubber is the pioneer certified implementation offering:
- 30 Specialized Industry Profiles: HIPAA PHI (18 identifiers), PCI-DSS 4.0, GLBA Financial, SEC 17a-4, CJIS Law Enforcement, FERPA Student Records, Defense ITAR/CMMC, FRE-502 Legal Work-Product.
- Agentic Guard Automation: Autonomous zero-trust tool wrappers (guard_exec, guard_read_file, guard_apply_patch).
- Air-Gapped Node Licensing: Disconnected Ed25519 cryptographic tokens without cloud telemetry.
- Headless SDK: Backend RAG pipeline redaction for Node.js / TypeScript / Python (@privacyscrubber/sdk).
- SOC 2 Type II Evidence Binder: Automated audit artifacts (ztds-evidence-binder.json) for Drata, Vanta, and AuditBoard.

Deploy the commercial implementation:```bash

Production MCP Server

npm install -g @privacyscrubber/mcp-server

Headless Backend SDK

npm install @privacyscrubber/sdk


Website: https://privacyscrubber.com

---

## Verification & Self-Test

To run the offline test suite:```bash
node test.js

Conforms to standard JSON-RPC 2.0 stdio protocol. Zero runtime dependencies.


License

Apache-2.0. Maintained by the ZTDS AI Consortium (Working Group WG-1).
Website: https://ztds.ai
Lead Architect: Ilya Sibiryakov (Author of ZTDS RFC v1.0, IETF Standards Track sibiryakov-ztds-protocol, U.S. & Int'l Patents Pending).

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
ZTDS Reference 怎么安装?

在客户端按下面的安装命令接入:{ "mcpServers": { "ztds": { "command": "npx", "args": ["-y", "ztds-mcp"] } } }。装完在客户端配置里引用同一个包或端点。

ZTDS Reference 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

ZTDS Reference 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

ZTDS Reference 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

ZTDS Reference 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

ZTDS Reference 能提供哪些能力?

资料显示能力标签包括 开发。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。