PII Detector API

Official registry Productivity

Detect PII in text: emails, phones, SSNs, credit cards, IPs. Regex + Luhn. x402.

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 (sse)
Claude Code
claude mcp add --transport sse pii-detector-api 'https://pii-detector.api.klymax402.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "pii-detector-api": {
            "type": "sse",
            "url": "https://pii-detector.api.klymax402.com/mcp"
        }
    }
}

Documentation

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

Contents
  1. PII Detector API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

PII Detector API

Detect PII in text: emails, phones, SSNs, credit cards, IPs, addresses. Regex-based. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "pii-detector": {
      "url": "https://pii-detector.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://pii-detector.api.klymax402.com/api/detect" \
  -H "Content-Type: application/json" \
  -d '{"text":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
compliance_detect_piiPOST/api/detect$0.012Detect personally identifiable information (PII) in text
compliance_detect_pii

Use this when you need to scan text for personally identifiable information (PII). Detects emails, phone numbers (international), credit card numbers (with Luhn validation), US SSNs, dates of birth, IP addresses, postal addresses (US/UK/FR), passport numbers, and URLs with tokens. Returns each match with type, redacted value, position, and confidence. Includes overall risk level (low/medium/high/critical). Do NOT use for email validation — use email_verify_address. Do NOT use for GDPR compliance — use compliance_scan_gdpr.

Parameters

NameTypeRequiredDescription
textstringyesText content to scan for PII

Example agent prompts

  • "Scan text for personally identifiable information (PII)"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Frequently asked questions

What is PII Detector API?

Detect PII in text: emails, phones, SSNs, credit cards, IPs. Regex + Luhn. x402.

How do I install PII Detector API?

It runs as a remote server. In Claude Code: claude mcp add --transport sse pii-detector-api 'https://pii-detector.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does PII Detector API 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 Detector API open source?

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

Who maintains PII Detector API?

It is published by Br0ski777. 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.