scrub-vault
Related Servers
Alternatives to scrub-vault
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables local, in-memory de-identification of PII, PHI, and credentials with deterministic reversible surrogate tokens before LLM transmission, then restores originals from volatile session mappings and audits for exposures without network egress or disk writes.5115 npm1Apache 2.0
- AlicenseAqualityBmaintenanceLocal pseudonymisation MCP server that detects PII in text, replaces it with opaque tokens before sending to cloud LLMs, and restores tokens afterward.273 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, in-memory sanitization of sensitive text before LLM ingestion by replacing PII, PHI, and credentials with deterministic reversible tokens, then restoring the originals in responses. It also audits content for exposed secrets and PII and provides compliance receipts without external network egress or disk writes.12 npm1Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceEnables agents to encrypt and sanitize sensitive data such as credentials, credit card numbers, and addresses locally before dispatching prompts to cloud LLMs, then rehydrate the masked values client-side. It runs deterministically with zero external dependencies over MCP JSON-RPC stdio, so no plaintext PII leaves the user's machine.-
- FlicenseAqualityBmaintenancePII sanitization layer for autonomous AI agent pipelines. Detects and redacts emails, phone numbers, national IDs, private keys, and financial data before text reaches LLMs. Supports EN, ES (LATAM), PT (BR/PT), DE, JA.12-
- AlicenseAqualityBmaintenanceEnables safe interaction with cloud LLMs by redacting sensitive entities into reversible placeholders, enforcing deterministic egress policies with human approval, and rehydrating responses so real data never leaves the process.4MIT
TDQS
Scored across 4 tools
Each tool targets a distinct operation: masking text, restoring values, auditing risk, and anonymizing JSON. Mask/unmask are clearly paired complements rather than overlapping, and audit/anonymize are separate concerns.
All tools use a consistent scrub_ prefix followed by a verb_noun pattern (mask_text, unmask_text, audit_risk, anonymize_json) in uniform snake_case.
Four tools is well-scoped for a focused PII-scrubbing server, with mask/unmask round-trip, an audit function, and a JSON variant each earning its place.
Covers the core lifecycle of mask, unmask, audit, and JSON anonymization with no obvious dead ends. Minor gaps exist around token_map persistence/management and document/file-level operations, but agents can work around these.