The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the GDPR Scanner API listing page.
Scan any website for GDPR compliance -- cookie consent, privacy policy, trackers, DPO contact. Score 0-100. 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.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
compliance_scan_gdpr | GET | /api/scan | $0.03 | Scan a website for GDPR compliance — cookie consent, privacy policy, trackers |
compliance_scan_gdpr | POST | /api/scan | $0.03 | Scan a website for GDPR compliance — cookie consent, privacy policy, trackers (POST variant) |
compliance_scan_gdprUse this when you need to check a website's GDPR compliance. Scans the URL plus /privacy-policy and /cookie-policy pages. Returns a compliance report in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
url | string | yes | Website URL to scan for GDPR compliance (e.g. https://example.com) |
Example response:
When to use: launching a website in the EU, FOR compliance audits, due diligence on acquisitions, and regular privacy monitoring.
Not for: PII in text (use compliance_detect_pii), tech detection (use website_detect_tech_stack), HTTP security headers (use network_analyze_headers).
compliance_scan_gdprUse this when you need to check a website's GDPR compliance. Scans the URL plus /privacy-policy and /cookie-policy pages. Returns a compliance report in JSON. POST variant of compliance_scan_gdpr -- same params passed as JSON body instead of query string.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
url | string | yes | Website URL to scan for GDPR compliance (e.g. https://example.com) |
Example response:
When to use: launching a website in the EU, FOR compliance audits, due diligence on acquisitions, and regular privacy monitoring.
Not for: PII in text (use compliance_detect_pii), tech detection (use website_detect_tech_stack), HTTP security headers (use network_analyze_headers).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT