Zero-Trust Data Sanitization

MCP Server: IDE Prompt Security Gateway for Cursor & Claude Desktop

Zero-Trust Agentic Pipelines: Secure Your IDE Localhost

100% Local RAM Airplane Mode 0 Bytes Egress
Free to start · $0 Free / $99/mo Teams
MCP IDE File Scrubbing

AI Summary / Key Takeaways

Verified Zero-Trust Logic

"Air-gapped Model Context Protocol (MCP) server for Cursor, Windsurf, and Claude Code. Scrub code secrets and PII locally before LLM transmission."

Install the MCP Server: Run 'npx @privacyscrubber/mcp-server' or add it to your .cursor/mcp.json config. The server starts locally on stdio — no network port, no HTTP, no authentication required.
Call sanitize_file or sanitize_text: Use 'audit_directory_for_pii' to scan an entire codebase for leaked secrets before ingestion. Then call the 'sanitize_file' tool with a file path, or 'sanitize_text' with raw content. The MCP server applies the active detection profile and returns a tokenized version with a session token map.
Reveal with reveal_text: After the AI model processes your tokenized prompt, paste the response into 'reveal_text'. Tokens ([NAME_1], [EMAIL_2]) are restored to original values from the in-memory session map. Zero persistence, zero server.

Enterprise-Grade AI Privacy

Add custom redaction rules and priority support with PRO.

GO PRO
Live Turnkey Simulator · ZTDS Engine

Interactive PII Detection & Sanitization Sandbox

Test real-time client-side RAM tokenization. Choose a specialized preset or paste your own raw prompt to test instant reversible redaction.

Protected in IDE Prompt Security (MCP): API Access KeysSECRETInternal Server HostnamesDB_URI
0 Bytes Server Egress
<1.8ms Latency
Select Industry Test Payload:
Raw Input Payload
0 chars
RAM-Only Isolated Session
1-Click Safe AI Launch:
Automated Detection Classes:
API Access Keys / TokensSECRETInternal Server HostnamesDB_URI
Enterprise Challenge

The Challenge with AI Data Workflows

Developers using AI-powered IDEs like Cursor often run "codebase-wide analysis" that inadvertently uploads hardcoded API keys, customer emails in test databases, and production log dumps to external LLMs.

Zero-Egress Data Protection
Eliminates corporate data leaks before prompts hit external AI models.
Zero-Trust Resolution

How It Works

1

Install the MCP Server

Run 'npx @privacyscrubber/mcp-server' or add it to your .cursor/mcp.json config. The server starts locally on stdio — no network port, no HTTP, no authentication required.

2

Call sanitize_file or sanitize_text

Use 'audit_directory_for_pii' to scan an entire codebase for leaked secrets before ingestion. Then call the 'sanitize_file' tool with a file path, or 'sanitize_text' with raw content. The MCP server applies the active detection profile and returns a tokenized version with a session token map.

3

Reveal with reveal_text

After the AI model processes your tokenized prompt, paste the response into 'reveal_text'. Tokens ([NAME_1], [EMAIL_2]) are restored to original values from the in-memory session map. Zero persistence, zero server.

Supported Formats & Limitations

Supported Formats

Cursor IDEClaude DesktopVS CodeFilesystem directories

System Limitations

  • Requires Node.js runtime for the local MCP server
  • Operates via stdio transport (no network ports exposed)
  • Designed for developer environments and automated CI/CD staging

Unblock Autonomous AI Coding: Zero Secret & PII Leaks in Cursor & Claude Desktop

Autonomous AI coding assistants—including Cursor Composer, Windsurf, and Claude Code—transform developer productivity by reading full repository trees, logs, and configuration files into LLM context windows. But this velocity introduces an immediate security risk: a simple prompt like "Fix database connection timeout" can cause an autonomous agent to read .env.production, database connection strings, and test databases containing real customer PII, transmitting them in plaintext to third-party model providers.

The PrivacyScrubber MCP Server gives engineering teams the ultimate outcome: unconstrained AI coding velocity with zero secret exfiltration risk. Operating directly on your machine over standard input/output (stdio), it intercepts file reads and prompt payloads locally, replacing secrets and personal data with reversible tokens ([API_KEY_1], [DB_URI_1], [NAME_1]) before data leaves your workstation.

Air-Gapped stdio Gateway: Real-Time Protection with 0ms Network Latency

Unlike cloud DLP proxies that add 200ms+ network delays and require root CA certificate installations, PrivacyScrubber runs as a lightweight local child process:

+-----------------------------------------------------------------------------------+
| LOCAL WORKSTATION / IDE (Cursor, Claude Desktop, Windsurf, VS Code)               |
|                                                                                   |
|  1. Developer Prompt / Autonomous Agent File Read                                 |
|     "Analyze logs/orders.json and fix the failing payment transaction"            |
|           |                                                                       |
|           v (stdio JSON-RPC IPC - 0ms Network Latency)                            |
|  +-----------------------------------------------------------------------------+  |
|  | PRIVACYSCRUBBER MCP SERVER (Local Node.js Process)                          |  |
|  | - Intercepts sanitize_file / sanitize_text tool calls                       |  |
|  | - 30 Specialized Profiles (DevOps Secrets, AWS, DB URIs, GDPR, HIPAA)     |  |
|  | - Replaces sensitive values with [AWS_KEY_1], [DB_URI_1], [CUSTOMER_1]     |  |
|  | - Volatile In-Memory Session Map (Zero Disk Writes, Zero Remote Telemetry)  |  |
|  +-----------------------------------------------------------------------------+  |
|           |                                                                       |
|           v (Tokenized Prompt)                                                    |
|  2. Tokenized Payload Egress -> External AI API (Anthropic / OpenAI / DeepSeek)   |
+-----------------------------------------------------------------------------------+
                                    | (External Network)
                                    v
       External LLM analyzes code structure without learning actual secrets
                                    |
+-----------------------------------------------------------------------------------+
|  3. Model Response -> IDE Agent executes reveal_text                              |
|     Tokens rehydrated in local memory -> Developer sees working solution!         |
+-----------------------------------------------------------------------------------+

60-Second Setup: 1-Click Blueprints for Cursor & Claude Desktop

Deploy PrivacyScrubber into your AI IDE in under 60 seconds with zero network ports or firewall configurations:

Cursor AI (.cursor/mcp.json) Global / Workspace
{
  "mcpServers": {
    "privacyscrubber": {
      "command": "npx",
      "args": ["-y", "@privacyscrubber/mcp-server"],
      "env": {
        "PS_PROFILE": "devops",
        "PS_TIER": "pro"
      }
    }
  }
}
Claude Desktop (claude_desktop_config.json) macOS / Windows
{
  "mcpServers": {
    "privacyscrubber": {
      "command": "npx",
      "args": ["-y", "@privacyscrubber/mcp-server"],
      "env": {
        "PS_PROFILE": "general",
        "PRIVACYSCRUBBER_TELEMETRY": "false"
      }
    }
  }
}

Developer Secrets & PII Coverage: Zero-Trust Detection for Source Code

Calibrated specifically for source code, database dumps, and infrastructure manifests:

Cloud Credentials

AWS Access Keys (AKIA...), GCP Service Account JSON keys, and Azure Client Secrets.

[AWS_KEY_N]

Database URIs

Connection strings for PostgreSQL, MongoDB (mongodb+srv://), MySQL, and Redis with passwords.

[DB_URI_N]

Private Keys

RSA, OpenSSH, and Ed25519 blocks (-----BEGIN PRIVATE KEY-----), and TLS/SSL certificates.

[PRIV_KEY_N]

API & JWT Tokens

Stripe Live keys (sk_live_), GitHub PATs (ghp_), Bearer tokens, and OpenAI secret tokens.

[TOKEN_N]

Exposed MCP Tool Reference: Native Integration with Agent Context

Your AI coding assistant automatically discovers four native tools via the standard Model Context Protocol schema:

Tool IdentifierInput ParametersOperational OutputTypical Use Case
sanitize_texttext: string, profile?: stringTokenized string + entity count telemetrySanitizing ad-hoc code snippets or chat prompt text
sanitize_filefilePath: string, profile?: stringSanitized file string (.txt, .json, .log, .csv, .env)Feeding entire files into context without manual copy-paste
reveal_texttokenizedText: stringRestored plaintext string using RAM session mapRehydrating AI responses back to working code with real keys
audit_directory_for_piidirPath: string, profile?: stringComprehensive JSON audit report with line numbersPre-flight codebase scan before autonomous agent execution

Security & Speed Comparison: Local MCP Gateway vs. Disruptive Cloud Proxies

How local stdio interception provides absolute security and uncompromised developer speed:

Security & Dev FactorCloud DLP Network ProxyStatic Git Hooks (TruffleHog)PrivacyScrubber MCP Server
Processing ArchitectureRemote cloud hop (180–350ms)Pre-commit shell scriptLocal stdio IPC (<1ms latency)
AI Agent InterceptionFails on WebSocket / HTTP/2 streamsNone: Only triggers on git commitNative MCP tool integration
Reversible Token RevealDestructive redaction (Breaks code)N/A (Blocks commit)1-Click reveal_text in local memory
Customer PII DetectionGeneric regex / High false positivesSecrets only (Zero PII detection)30 Specialized Profiles (GDPR, HIPAA, FinTech)
Third-Party Vendor RiskNew subprocessor requiring DPA/BAASelf-hostedZero-Trust: Zero servers, 0-day clearance

Enterprise Rule Governance: Enforce Zero-Leak Code Across 50+ Engineers at $99/mo Flat

In enterprise engineering teams, you cannot rely on individual developers configuring custom regex patterns manually. With the TEAMS Tier ($99/mo Flat), security architects push centralized detection schemas—such as proprietary account ID formats and internal microservice token standards—directly to every developer's MCP server through encrypted team sync.

For automated repository pre-audits prior to launching agentic workflows, explore the companion Automated Directory Auditing guide. If your team also works across web-based chat interfaces, pair your IDE gateway with our in-browser Chrome Extension.

Client-Side ZTDS™ Execution & Conformance Verification

All PII detection and deterministic tokenization execute 100% inside local client memory — eliminating cloud proxies, external subprocessors, and network data egress.

100% Local RAM Airplane Mode Verified IETF RFC Draft
ZTDS™ Verified
ZTDS-CERT-2026-PRIVACYSCRUBBER-WEB-D02DC6
ZTDS™ RFC v1.0 Verified Capability·ZTDS-CERT-2026-PRIVACYSCRUBBER-WEB-D02DC6
Verify Cryptographic Seal

Frequently Asked Questions

Technical Details & Privacy Architecture

Which IDEs and AI agents are supported?
Any MCP-compatible client: Cursor, Claude Desktop, VS Code with Copilot (via MCP extension), Windsurf, Continue.dev, and any agent framework implementing the Model Context Protocol specification. The server communicates over stdio — no HTTP port, no authentication.
What tools does the MCP server expose?
Three tools: (1) sanitize_text — accepts a string, returns tokenized output + session token count. (2) sanitize_file — accepts a file path, reads the file locally, returns tokenized content as string (supports .txt, .md, .csv, .json, .log, .docx). (3) reveal_text — accepts a tokenized string, restores original values from the in-memory session map. Session map is cleared when the MCP server process exits.
Does the MCP server send any data to external APIs?
Zero. The entire processing pipeline runs in the local Node.js process. No HTTP requests are made during sanitize_text, sanitize_file, or reveal_text operations. The session map is held in process RAM and cleared on exit. This is a ZTDS-compliant tool call — verifiable by inspecting the source code on npm.
Does the MCP server support industry-specific detection profiles?
Yes. PRO users can set the active profile (Legal, Finance, Medical, HR, DevOps, Security, etc.) via a tool parameter or server config. Free tier includes General PII as well as a 5,000-character free quota across all 30 specialized profiles. PRO unlocks unlimited character volume across all 30 profiles including API key detection, IBAN masking, and medical PHI extraction.
Is the PrivacyScrubber MCP Server free to use?
Yes, 100% free with built-in session quota directly in Cursor, Claude Desktop, Windsurf, and VS Code. No credit card, no account registration, and no timed trials required. The free quota covers General PII and all 30 specialized profiles. PRO and TEAMS plans remove all character limits and enable centralized organizational policy synchronization.
How do I verify the MCP server is processing locally?
Run the server with the --verbose flag: 'npx @privacyscrubber/mcp-server --verbose'. All tool calls are logged to stderr with input byte counts and output token counts. No URLs, no external hostnames appear in the logs — confirming purely local execution.
Can I push custom rules to my engineering team's IDEs?
Yes. With the TEAMS tier, admins can use Centralized Rule Sync to push custom regex rules (e.g., internal API token formats or proprietary IDs) directly to their developers' PII MCP Servers. This ensures consistent 'Team-Synced IDE MCP' protection across your entire engineering department.
100% Zero-Trust Deployment

Protect Your IDE Prompts & Secrets in Under 60 Seconds

Zero open ports. Zero external network egress. Works natively with Cursor and Claude Desktop.