Ztds

Name: Ztds
Author: moxno

by moxnoversion 1.0.0i★ –iRuns on your computer

Registry nameio.github.moxno/ztds

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new↓ 82/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ztds": {
      "command": "npx",
      "args": [
        "-y",
        "ztds-mcp"
      ]
    }
  }
}

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ztds": {
      "command": "npx",
      "args": [
        "-y",
        "ztds-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ztds": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "ztds-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account moxno, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5689 servers in this category
Published to the registry more recently than 50% of the other 5689 servers in this category
Basic checks equal to or better than 100% of the other 5689 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ztds safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 42 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 972.7K/wk★ 64.2KUpdated 2 days ago

Computer or cloud

Install

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 18K/wk★ 48.1KUpdated 22 days ago

Runs on your computer

Install

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsGrowing★ 5.2KUpdated 2 months ago

Runs in the cloud✓ exa.ai

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ztds-mcp & ztds-audit — Zero-Trust Data Sanitization (ZTDS™ RFC v1.0) MCP Server & Invariant Auditor

This repository contains the official Model Context Protocol (MCP) Server implementation (`ztds-mcp`) and Codebase Invariant Auditor (`ztds-audit`) for the Zero-Trust Data Sanitization (ZTDS™ RFC v1.0) standard. Maintained by the ZTDS AI Consortium.

MCP Server Source Code (in this repository): packages/ztds-mcp/index.js
MCP Manifest & Server Card: packages/ztds-mcp/manifest.json | server-card.json | smithery.yaml
MCP Server Test Suite: packages/ztds-mcp/test.js
CLI Invariant Auditor: bin/ztds-audit.js

ZTDS™ governs in-memory data sanitization for AI agents, IDE assistants (Claude Desktop, Claude Code, Cursor, Windsurf, Zed), retrieval-augmented generation (RAG), and Large Language Model (LLM) pipelines. It executes 100% locally in volatile device memory (RAM) with zero external network calls, zero disk writes, and zero subprocessors.

1. MCP Server Implementation (`ztds-mcp`)

The reference MCP server (packages/ztds-mcp/index.js) implements the Model Context Protocol (2024-11-05) over stdio JSON-RPC 2.0 transport with zero external runtime dependencies. It intercepts sensitive cleartext (PII, PHI, API secrets, IBANs, credit cards) in client RAM prior to LLM dispatch, substitutes deterministic surrogate tokens ([EMAIL_TOKEN_1], [API_SECRET_TOKEN_1]), and restores authentic values locally in LLM responses.

1.1 Installation & MCP Client Configuration

Option A: 1-Click Automated Setup

npx ztds-mcp init

Option B: Claude Desktop (`claude_desktop_config.json`) & Cursor IDE (`.cursor/mcp.json`)

"mcpServers": { "ztds": { "command": "npx", "args": ["-y", "ztds-mcp"] } } }

Option C: Run Directly from Repository Source

"mcpServers": { "ztds": { "command": "node", "args": ["/absolute/path/to/ztds.ai/packages/ztds-mcp/index.js"] } } }

Option D: Claude Code CLI

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

1.2 MCP Tools (`tools/list` & `tools/call`)

Implemented in packages/ztds-mcp/index.js:

Tool Name	Input Schema (`properties`)	Description
`ztds_sanitize`	`text` (`string`, required), `sessionId` (`string`, optional)	Masks sensitive PII, PHI, and credentials in client volatile RAM with deterministic surrogate tokens (`[EMAIL_TOKEN_1]`, `[API_SECRET_TOKEN_1]`) before LLM ingestion and emits a cryptographic SHA-256 `ZTDS-RECEIPT-*` attestation.
`ztds_restore`	`text` (`string`, required), `sessionId` (`string`, optional)	Restores original unmasked cleartext from surrogate tokens locally in volatile RAM using atomic single-pass lookup (preventing second-order token injection).
`ztds_audit`	`text` (`string`, required)	Audits text or file contents for exposed credentials and PII against ZTDS RFC v1.0, returning category breakdowns, risk level (`LOW`/`HIGH`/`CRITICAL`), and a SHA-256 compliance receipt.
`ztds_info`	`{}` (no arguments)	Returns active ZTDS RFC v1.0 protocol status, IETF Standards Track metadata, and volatile RAM session metrics.
`ztds_reset_session`	`sessionId` (`string`, optional)	Explicitly zeroizes and destroys the volatile in-memory surrogate mapping table (Theorem 2 RAM zeroization).

Example JSON-RPC `tools/call` (`ztds_sanitize` -> `ztds_restore`)

Request (`ztds_sanitize`):

"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "ztds_sanitize", "arguments": { "text": "Customer alice@acme.org reported failure with key sk-proj-demo-key.", "sessionId": "ide-session-01" } } }

Response:

"jsonrpc": "2.0", "id": 1, "result": { "content": [ { "type": "text", "text": "Customer [EMAIL_TOKEN_1] reported failure with key [API_SECRET_TOKEN_1].\n\n> [ZTDS Invariant 1 Attested] Zero external network egress.\n> Receipt: ZTDS-RECEIPT-8F4B2C19E0A3D712 | Execution: 42µs | Entities Masked: 2" } ], "isError": false } }

1.3 MCP Resources (`resources/list` & `resources/read`)

The MCP server exposes structured read-only protocol and telemetry resources via resources/list and resources/read:

Resource URI	MIME Type	Description
`ztds://spec/rfc-v1`	`application/json`	Formal ZTDS RFC v1.0 / IETF `draft-sibiryakov-ztds-protocol` specification metadata and the 4 core mathematical invariants.
`ztds://session/telemetry`	`application/json`	Real-time volatile RAM session count, capacity limits, and zero-egress attestation status (zero cleartext exposure).

1.4 MCP Prompts (`prompts/list` & `prompts/get`)

Prompt Name	Arguments	Description
`ztds_guard`	`task` (`string`, required)	Activates the ZTDS Zero-Trust Data Sanitization guardrail for the current IDE/agent workflow, instructing the model to invoke `ztds_sanitize` prior to external reasoning and `ztds_restore` on output.

1.5 Programmatic / Node.js SDK Usage (`packages/ztds-mcp/index.js`)

The MCP server module exports its JSON-RPC dispatcher and in-memory sanitization primitives for direct programmatic integration and testing:

import {

handleMessage, sanitizeText, restoreText, auditText, resetSessionStore, TOOLS, PROMPTS, RESOURCES } from './packages/ztds-mcp/index.js';

// 1. Direct in-memory sanitization & restoration const scrubbed = sanitizeText('Send wire to DE89370400440532013000 for john@example.com', 'session-1'); console.log(scrubbed.sanitizedText); // "Send wire to [IBAN_TOKEN_1] for [EMAIL_TOKEN_1]"

const restored = restoreText(Confirmed transfer to ${scrubbed.sanitizedText}, 'session-1'); console.log(restored.restoredText);

// 2. Direct MCP JSON-RPC 2.0 protocol invocation const rpcResponse = await handleMessage({ jsonrpc: '2.0', id: 1, method: 'tools/list', params: {} });

// 3. Zeroize volatile session memory (Theorem 2) resetSessionStore('session-1');

Run the MCP server verification suite locally:

node packages/ztds-mcp/test.js

2. The 4 Fundamental Invariants (RFC v1.0)

Every AI pipeline protected by ztds-mcp and 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).

3. Codebase Invariant Auditor CLI (`ztds-audit`)

Run a zero-install security and invariant audit across your codebase or AI agent repository:

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

Command-Line Flags

Flag	Description	Default
`-d, --dir`	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

[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:

Include this audit hash in your pull request: https://ztds.ai/apply/
Embed your Verified Trust Badge in README.md to claim your registry backlink:

4. 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

on: push: branches: [ main, master ] pull_request: branches: [ main, master ]

jobs: audit: name: Verify ZTDS RFC v1.0 Invariants runs-on: ubuntu-latest steps:

name: Checkout Codebase uses: actions/checkout@v4

name: Setup Node.js Runtime uses: actions/setup-node@v4 with: node-version: '20'

name: Execute ZTDS Invariant Audit uses: moxno/ztds.ai@main with: dir: './src' strict: true

5. Empirical AI Safety Benchmark (Frontier LLMs)

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:

# Execute 25 multi-domain enterprise scenarios across 4 frontier LLM families

npx ztds-bench

Generate formal Markdown evaluation report & Ed25519 cryptographic certificate

npx

Only the beginning is shown; read the rest in the repo

Ztds

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

ztds-mcp & ztds-audit — Zero-Trust Data Sanitization (ZTDS™ RFC v1.0) MCP Server & Invariant Auditor

1. MCP Server Implementation (ztds-mcp)

1.1 Installation & MCP Client Configuration

Option A: 1-Click Automated Setup

Option B: Claude Desktop (claude_desktop_config.json) & Cursor IDE (.cursor/mcp.json)

Option C: Run Directly from Repository Source

Option D: Claude Code CLI

1.2 MCP Tools (tools/list & tools/call)

Example JSON-RPC tools/call (ztds_sanitize -> ztds_restore)

1.3 MCP Resources (resources/list & resources/read)

1.4 MCP Prompts (prompts/list & prompts/get)

1.5 Programmatic / Node.js SDK Usage (packages/ztds-mcp/index.js)

2. The 4 Fundamental Invariants (RFC v1.0)

3. Codebase Invariant Auditor CLI (ztds-audit)

Command-Line Flags

Example Output

4. GitHub Actions CI/CD Integration

5. Empirical AI Safety Benchmark (Frontier LLMs)

Generate formal Markdown evaluation report & Ed25519 cryptographic certificate

1. MCP Server Implementation (`ztds-mcp`)

Option B: Claude Desktop (`claude_desktop_config.json`) & Cursor IDE (`.cursor/mcp.json`)

1.2 MCP Tools (`tools/list` & `tools/call`)

Example JSON-RPC `tools/call` (`ztds_sanitize` -> `ztds_restore`)

1.3 MCP Resources (`resources/list` & `resources/read`)

1.4 MCP Prompts (`prompts/list` & `prompts/get`)

1.5 Programmatic / Node.js SDK Usage (`packages/ztds-mcp/index.js`)

3. Codebase Invariant Auditor CLI (`ztds-audit`)