Open standard MCP server for Zero-Trust Data Sanitization (ZTDS RFC v1.0). Local in-RAM PII guard.
117
ztds-mcp)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.
Auto-configure your installed AI IDEs and clients with a single command:
npx ztds-mcp init
The configurator automatically:
ztds server block into their local configuration files.To verify existing client configurations:
npx ztds-mcp status
Run the containerized ztds-mcp image (linux/amd64 and linux/arm64) with zero host filesystem access:
docker pull brandmeweb/ztds-mcp:latest
Configure in claude_desktop_config.json or .cursor/mcp.json:
{
"mcpServers": {
"ztds": {
"command": "docker",
"args": ["run", "-i", "--rm", "brandmeweb/ztds-mcp:latest"]
}
}
}
Audit sensitive files, configuration directories, or CI/CD pipelines for credential leakage prior to AI agent ingestion:
# 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.
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:
[API_SECRET_TOKEN_1], [EMAIL_TOKEN_1]).If you prefer configuring your clients manually without npx ztds-mcp init:
Add to claude_desktop_config.json:
{
"mcpServers": {
"ztds": {
"command": "npx",
"args": ["-y", "ztds-mcp"]
}
}
}
Config file locations:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonAdd to .cursor/mcp.json in your workspace root:
{
"mcpServers": {
"ztds": {
"command": "npx",
"args": ["-y", "ztds-mcp"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"ztds": {
"command": "npx",
"args": ["-y", "ztds-mcp"]
}
}
}
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). |
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. |
prompts/list & prompts/get)| Prompt | Arguments | Description |
|---|---|---|
ztds_guard | task (string, required) | Activates the ZTDS Zero-Trust Data Sanitization guardrail in Claude or Cursor. |
Explore the vendor-neutral specification, security boundaries, and regulatory blueprints on ztds.ai:
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:
guard_exec, guard_read_file, guard_apply_patch).@privacyscrubber/sdk).ztds-evidence-binder.json) for Drata, Vanta, and AuditBoard.Deploy the commercial implementation:
# Production MCP Server
npm install -g @privacyscrubber/mcp-server
# Headless Backend SDK
npm install @privacyscrubber/sdk
Website: https://privacyscrubber.com
Commercial integration references:
To run the offline test suite:
node test.js
Conforms to standard JSON-RPC 2.0 stdio protocol. Zero runtime dependencies.
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).
Content type
Image
Digest
sha256:f9fc71c0d…
Size
58.6 MB
Last updated
1 day ago
docker pull brandmeweb/ztds-mcp