Pre-payment PII screener for x402 — catches emails, SSNs, names before agents sign.
Pre-payment PII screener for x402 — agents call before signing, catching emails, SSNs, phone numbers, names, and other personal data in payment metadata before it reaches the merchant. Part of the toolkit family. Thin MCP (Model Context Protocol) adapter over the library. x402 agentic payments routinely carry user-supplied free text — descriptions, memos, query-string parameters — straight…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Pre-payment PII screener for x402 — agents call before signing, catching emails, SSNs, phone numbers, names, and other personal data in payment metadata before it reaches the merchant. Part of the toolkit family. Thin MCP (Model Context Protocol) adapter over the library. x402 agentic payments routinely carry user-supplied free text — descriptions, memos, query-string parameters — straight through to merchants and facilitators. When an LLM agent generates that text, it can include PII the user…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.