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
} |
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_infoA | Retrieve ZTDS open specification details (RFC v1.0, IETF draft-02) 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 |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct function: sanitize redacts PII/secrets, restore reverses token mapping, audit checks exposure and generates receipts, info retrieves specification details, and reset_session zeroizes in-memory mappings. There is no functional overlap between any pair of tools.
All tools share a consistent ztds_ prefix and snake_case, with most names using a verb form (sanitize, restore, audit, reset_session). The exception is ztds_info, which is noun-based rather than verb-based, creating a minor deviation.
Five tools is well-scoped for a focused zero-trust data sanitization server. Each tool earns its place by covering a distinct operation in the sanitization/restoration/audit lifecycle, without redundancy.
The surface covers the full lifecycle: sanitize (redact), restore (unmask), audit (verify and attest), reset_session (cleanup), plus info for specification details. No obvious gaps for the stated purpose of local PII/secrets management.