ztds-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ztds_sanitizeB | Sanitize sensitive PII and secrets in prompt text locally using ZTDS RFC v1.0 zero-egress invariants. |
| ztds_restoreB | Restore authentic cleartext values into LLM-generated output from local in-memory token mapping. |
| ztds_auditC | Audit text for PII/secrets exposure against ZTDS RFC v1.0 standard and generate an attestation receipt. |
| ztds_infoB | Retrieve ZTDS open specification details (RFC v1.0, IETF Standards Track) and enterprise upgrade guide. |
| ztds_reset_sessionC | Zeroize and purge volatile in-memory token mappings (Theorem 2 RAM zeroization). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ztds_guard | Activates the ZTDS Zero-Trust Data Sanitization guardrail in Claude or Cursor. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ZTDS RFC v1.0 Protocol Specification & 4 Core Invariants | Formal Zero-Trust Data Sanitization (ZTDS RFC v1.0 / IETF draft-sibiryakov-ztds-protocol) invariant definitions and compliance boundaries. |
| ZTDS Volatile RAM Session Telemetry | Real-time ephemeral session count and zero-egress attestation status (zero cleartext exposure). |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: specification info, auditing, sanitization, restoration, and session zeroization. Audit vs. sanitize is disambiguated by the attestation receipt focus, and restore vs. reset_session by their opposite data-mapping operations.
All tools use the ztds_ prefix and snake_case, giving a predictable namespace. Minor inconsistency exists because ztds_info is noun-based while most others are verbs, and ztds_reset_session is the only multiword action name.
Five tools is well-scoped for this domain, with each tool earning its place across info, sanitize, audit, restore, and reset operations. There is no obvious redundancy or missing sibling tool at this count.
The surface covers the core lifecycle: read the standard, sanitize text, audit for compliance, restore mappings, and zeroize session data. Minor gaps remain around explicit session/status inspection or policy configuration, but core agent workflows are supported.