PII Detector API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Nov 2, 2026

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

VerifiedSSEWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that scans text for personally identifiable information such as emails, phone numbers, SSNs and card numbers, returning redacted matches…

What you can do
  • Scan a block of text for PII and get back each match with its type, redacted value, position and confidence
  • Detect emails, international phone numbers, credit card numbers with Luhn validation, US SSNs, dates of birth, IP addresses, postal addresses, passport numbers and URLs containing tokens
  • Receive an overall risk level for the scanned text (low, medium, high or critical)
When to use it
Useful when an assistant needs to check pasted or generated text for sensitive personal data before sharing, logging or storing it, or to flag PII in a document. It is a single-purpose detector, not an email validator or a GDPR compliance scanner.
Requirements
A remote MCP endpoint reached over SSE; no local package, API key or signup. Each call is paid per use through the x402 protocol in USDC on the Base L2 network, so an x402-aware client with a funded wallet is needed to complete the payment challenge.
Before you install
Every call costs money (listed at $0.012 per detection) and is settled in USDC on Base, so a wallet must be configured and spending should be capped. The text you submit is sent to a third-party service, and the README names Coinbase CDP and PayAI as payment facilitators; do not send real sensitive data unless that is acceptable.

Installation

In SourceWeft

  1. Open PII Detector API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fpii-detector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

PII Detector API

[MCP Server] [x402] [License: MIT]

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.):

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

Quickstart -- HTTP (x402)

bash
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

Source: README.md at commit 83b97e0

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts