Open standard MCP server for Zero-Trust Data Sanitization (ZTDS RFC v1.0). In-memory PII masking.
io.github.moxno/ztds — Model Context Protocol (MCP) Server
The io.github.moxno/ztds MCP server provides an open-standard integration for Zero-Trust Data Sanitization (ZTDS RFC v1.0). It performs in-memory PII masking, operating as a sanitization-focused server within the MCP ecosystem.
🛠️ Key Features
Implements Zero-Trust Data Sanitization (ZTDS RFC v1.0)
In-memory PII masking
Open standard MCP server
🚀 Use Cases
Sanitizing personally identifiable information (PII) in memory
Applying Zero-Trust Data Sanitization rules via MCP
The official developer CLI and automated CI/CD auditor for the Zero-Trust Data Sanitization (ZTDS™ RFC v1.0) architecture. Maintained by the ZTDS AI Consortium.
ZTDS™ is an open industry standard governing in-memory data sanitization for artificial intelligence, retrieval-augmented generation (RAG), and Large Language Model (LLM) pipelines.
1. The 4 Fundamental Invariants (RFC v1.0)
Every AI pipeline audited by ztds-audit is verified against the 4 core mathematical and architectural invariants:
Invariant 1: Zero External Egress Prior to Sanitization: Raw sensitive cleartext (PII, PHI, API secrets, private financial numbers) must never cross the local execution boundary prior to reversible surrogate tokenization.
Invariant 2: Deterministic Reversible Tokenization: Semantic, syntactic, and structural context must be preserved for LLM reasoning while de-identification lookup tables remain strictly in local host volatile memory.
Invariant 3: Cryptographic & In-Memory Isolation: Operations run in volatile heap or hardware-attested enclaves (WASM, Nitro Enclaves, C-ABI) with zero unencrypted disk spill and immediate memory zeroization.
Invariant 4: Continuous Subprocessor Exclusion: Local client-side execution eliminates third-party transmission, legally exempting deployments from GDPR Article 28 data processing agreements (Zero-DPA).
2. Quickstart
Run a zero-install security and invariant audit across your codebase or AI agent repository:
bash
npx ztds-audit --dir ./src --strict
Command-Line Flags
Flag
Description
Default
-d, --dir <path>
Target directory to audit
Current working directory
--json
Output structured machine-readable JSON report
false
--strict
Fail build on any low-severity or informational finding
false
-h, --help
Display CLI options and usage
N/A
Example Output
text
[ZTDS] ZTDS.ai In-Memory Codebase Auditor (RFC v1.0 Conformance)
----------------------------------------------------------------------
Directory: /home/runner/work/ai-agent/src
Files Scanned: 48 files in 18ms
Audit Hash: sha256:7f83b1657ff1fc53b92dc18148a1d65dfc2d4b1fa3d677284addd200126d9069
----------------------------------------------------------------------
[PASS] CONFORMANCE CONFIRMED: 0 INVARIANT VIOLATIONS DETECTED
All scanned files comply with ZTDS Invariant 1 (Zero-Egress) and Invariant 3 (RAM isolation).
[LEGAL STATUS] Qualifies for GDPR Article 28 DPA Exemption (Zero-Subprocessor Chain)
[PERFORMANCE] 0.00 Bytes Sensitive WAN Egress | Pure In-Memory Execution
Next Steps for Builders & Maintainers:
1. Include this audit hash in your pull request: https://ztds.ai/apply/
2. Embed your Verified Trust Badge in README.md to claim your registry backlink:
[](https://ztds.ai/registry/)
3. GitHub Actions CI/CD Integration
Enforce zero-trust data sanitization on every pull request by creating .github/workflows/ztds-audit.yml:
Verify cleartext leakage prevention, bijective fidelity, and microsecond latency across OpenAI GPT-4o, Anthropic Claude 3.5 Sonnet, Google Gemini 2.0 Pro, and DeepSeek-V3:
If ztds-audit detects sensitive credentials, unmasked PII, or third-party telemetry in your AI pipeline, install a certified ZTDS execution engine to achieve instant conformance:
Official zero-dependency reference MCP server (io.github.moxno/ztds on Anthropic Registry) for Cursor, Claude Desktop, and Zed. MCP Guide
Certified Pioneer SDK
@privacyscrubber/sdk
Commercial / Air-Gapped
High-throughput WASM engine with 30 high-ACV industry profiles (HIPAA, PCI-DSS, Legal FRE-502), multi-threaded pipeline bindings, offline Ed25519 node licensing. Get SDK
Air-Gapped IDE MCP
@privacyscrubber/mcp-server
Commercial / Stdio
Stdio MCP proxy (io.github.moxno/privacyscrubber-mcp) for Cursor, Windsurf, Claude Code, and autonomous developer agents with 30 enterprise profiles. MCP Guide
6. Ecosystem Demarcation & Neutrality
ZTDS.ai (ztds.ai): Independent, vendor-neutral open standard, certification authority, and technical consortium. Governs RFC v1.0 specifications under Apache 2.0 / CC BY 4.0.
PrivacyScrubber (privacyscrubber.com): Commercial reference implementation and pioneer engine provider.
7. Intellectual Property & Statutory Governance
Patent Application: U.S. & International Patents Pending (System and Method for Client-Side Zero-Trust Data Sanitization and Cryptographic Multi-Party Pipeline Handoff). Paris Convention & 35 U.S.C. § 119 Priority (locked through 14/09/2027).
Registered Trademark: ZTDS™ (ILPO Order #182655957, Classes 9 & 42).