What it does
The server provides one tool, compliance_detect_pii, which scans text for personally identifiable information. It detects email addresses, international phone numbers, credit card numbers validated with the Luhn check, US Social Security numbers, dates of birth, IP addresses, US, UK and French postal addresses, passport numbers and URLs containing tokens. Each match is returned with its type, a redacted value, its position and a confidence score, together with an overall risk level from low to critical.
Use it when text needs checking for personal data before it is stored, shared or passed to another system. It is not meant for email validation, which the publisher directs to a separate tool, nor for GDPR compliance checks, which fall under compliance_scan_gdpr.
Each call is paid per request through x402: one call to the detection endpoint costs $0.012 in USDC on Base L2, with no API key or signup. The server is added to an MCP client configuration, and an x402-aware client handles the payment cycle automatically. It is one of 100 micropayment APIs in the klymax402 marketplace, and the code is released under the MIT license.
Limitations and requirements
Each call is paid in USDC on Base L2 through the x402 protocol, so a wallet and an x402-aware client are required. The publisher describes the detection as regex-based.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
PII Detector API
Detect PII in text: emails, phones, SSNs, credit cards, IPs. Regex + Luhn. x402.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it