PII Detector API
br0ski777/pii-detector-x402
The source repository is pretty bare, so here's what we know: this server scans text for personally identifiable information using regex patterns and Luhn validation. It catches emails, phone numbers, social security numbers, credit cards, and IP addresses. The x402 suffix and klymax402 domain suggest this is part of someone's personal toolkit. You'd reach for this when you need to scrub or flag PII in user input, logs, or documents before they hit storage or external APIs. It runs as a remote service over SSE, so you're making network calls rather than running detection locally. No code visible in the repo means you're trusting the remote endpoint. Useful for quick PII audits if you don't want to roll your own regex soup.
- tool
- 1
- last updated
- May 16, 2026
Tools
1 toolsPublic tool metadata for what this MCP can expose to an agent.
compliance_detect_piiUse 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, I1 params
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, I
Parameters* required
textstringText content to scan for PII
Sponsors
Readme
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
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
compliance_detect_pii | POST | /api/detect | $0.012 | Detect 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
| Name | Type | Required | Description |
|---|---|---|---|
text | string | yes | Text 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.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Details
- Repository
- github.com/br0ski777/pii-detector-x402
- Website
- github.com/Br0ski777/pii-detector-x402
- Transport
- SSE
- Registry
- MCP registry, active