English Français العربية

PII & Secret Redactor

Official registry Security

Detect and redact PII and secrets before text reaches an LLM, with reversible placeholders.

Source code Documentation

What can you do with PII & Secret Redactor?

  • detect_pii: findings with type, position and a masked preview. Never echoes full values.
  • redact_text: placeholder (stable tokens like <EMAIL_1>, same value gives the same token), mask, salted hash, or remove.
  • restore_text: swap placeholders back to the originals in the model's response, using the mapping you keep.
  • list_detectors: exactly what is and is not covered.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http pii-secret-redactor 'https://pii-redactor-mcp.mcpize.run/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "pii-secret-redactor": {
            "type": "http",
            "url": "https://pii-redactor-mcp.mcpize.run/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. PII & Secret Redactor
  2. Send the question, not the customer's data
  3. What it detects
  4. Tools
  5. Be clear about the limits
  6. Use it

PII & Secret Redactor

Redact PII and secrets from text before it reaches an LLM. Checksum-verified cards, IBANs and routing numbers, SSN range rules, API keys, and reversible placeholders you can restore after the model responds.

Send the question, not the customer's data

Strip personal data and credentials out of text before it goes to a model, a log or a ticket, then put the originals back in the answer.

What it detects

  • Verified, not just matched: credit cards (Luhn, brand identified), IBANs (mod-97), US routing numbers (ABA checksum), SSNs (invalid ranges rejected). Order numbers and random digit strings are left alone.
  • Contact and identity: emails, phone numbers (US and international), labelled dates of birth, US street addresses, IPv4 and IPv6.
  • Secrets: Anthropic, OpenAI, AWS, GitHub, Stripe, Slack and Google keys, JWTs, private keys, database URLs with credentials.

Tools

  • detect_pii: findings with type, position and a masked preview. Never echoes full values.
  • redact_text: placeholder (stable tokens like <EMAIL_1>, same value gives the same token), mask, salted hash, or remove.
  • restore_text: swap placeholders back to the originals in the model's response, using the mapping you keep.
  • list_detectors: exactly what is and is not covered.

Be clear about the limits

Pattern and checksum based. It does not detect personal names or free-form addresses in other formats, so it reduces exposure but is not a compliance guarantee for HIPAA, GDPR or PCI. Input is processed in memory and never stored or logged.

Use it

Hosted on MCPize with a free tier (10 calls a day). Remote MCP endpoint (streamable HTTP, API key from MCPize):

https://pii-redactor-mcp.mcpize.run/mcp

Or run it yourself:

npm install
node server.js   # listens on :8080, MCP at /mcp

MIT licensed.

Frequently asked questions

What is PII & Secret Redactor?

Detect and redact PII and secrets before text reaches an LLM, with reversible placeholders.

How do I install PII & Secret Redactor?

It runs as a remote server. In Claude Code: claude mcp add --transport http pii-secret-redactor 'https://pii-redactor-mcp.mcpize.run/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does PII & Secret Redactor need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is PII & Secret Redactor open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains PII & Secret Redactor?

It is published by tylerscomic-lab. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.