Ztds MCP server

by moxno·io.github.moxno/ztds·v1.0.0

No reviews yet

Open standard MCP server for Zero-Trust Data Sanitization (ZTDS RFC v1.0). In-memory PII masking.

A92/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A92/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Ztds yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ztds tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

ztds_audit
Audit text for PII/secrets exposure against ZTDS RFC v1.0 standard and generate an attestation receipt.
ztds_info
Retrieve ZTDS open specification details (RFC v1.0, IETF draft-02) and enterprise upgrade guide.
ztds_reset_session
Zeroize and purge volatile in-memory token mappings (Theorem 2 RAM zeroization).
ztds_restore
Restore authentic cleartext values into LLM-generated output from local in-memory token mapping.
ztds_sanitize
Sanitize sensitive PII and secrets in prompt text locally using ZTDS RFC v1.0 zero-egress invariants.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan4 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Ztds compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 92/100; higher than 95% of 48,255 servers
Tools: 5; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 5 read

Install Ztds in Claude Code, Cursor or VS Code

Runs npx -y ztds-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ztds -- npx -y ztds-mcp

Add to Cursor

What the publisher says

From the Ztds repository's README, as published. We do not edit it. Read it on GitHub

ztds-audit — Zero-Trust Data Sanitization (ZTDS RFC v1.0) Invariant Auditor

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:

npx ztds-audit --dir ./src --strict

Command-Line Flags

Example Output

[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:
   [![ZTDS Verified](https://ztds.ai/badge/your-app.svg)](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:

name: ZTDS Zero-Trust Compliance Audit

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Ztds: common questions

Is Ztds MCP server safe?: Yes, by our scan: it is graded A (92/100). Read the Ztds safety report
How do I install Ztds?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Ztds need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Ztds maintained?: The last commit was 38 days ago (2026-09-27). The latest release is v1.0.0.
How does Ztds compare with other MCP servers?: safety score 92/100 (higher than 95% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.