PII Detector API is listed as active in the registry but did not answer our last check. It exposes 1 tools. Last commit 2 Sep 2026.
Detect PII in text: emails, phones, SSNs, credit cards, IPs. Regex + Luhn. x402.
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add pii-detector --transport sse https://pii-detector.api.klymax402.com/mcp
https://pii-detector.api.klymax402.com/mcp
[mcp_servers.pii-detector]
url = "https://pii-detector.api.klymax402.com/mcp"
{
"mcpServers": {
"pii-detector": {
"url": "https://pii-detector.api.klymax402.com/mcp"
}
}
}
{
"servers": {
"pii-detector": {
"type": "sse",
"url": "https://pii-detector.api.klymax402.com/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
compliance_detect_pii
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://pii-detector.api.klymax402.com/mcp | sse | answering | 37 ms | 11 min ago |
Detects and redacts PII (emails, phones, SSNs, names, addresses) from text. $0.02/call via x402.
Permanently redact SSNs, cards, emails, phones and custom terms from local PDFs, verified gone.
Regex and Luhn heuristic PII redaction and tokenization engine sanitizing sensitive emails, phones,
Auto-detects and obfuscates PII (IPs, emails, API keys, names) so Claude never sees real client data
DomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record.
DomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record.
Pre-share check: flags API keys, emails, your private terms in text. As is. x402 $0.005, Base
Detect-only CSV check before CRM import: duplicate, invalid and role emails, blanks, phones, dates.
Answers built from our own checks of this server.