About Gdpr Scanner X402
Gdpr Scanner X402 is an MCP server and pay-per-call API for checking website GDPR compliance. It examines consent, policies, trackers, and DPO contact details, then returns a scored JSON report for compliance reviews and privacy monitoring.
Key features
- 01Scan cookie consent and policies
- 02Detect third-party trackers
- 03Check DPO contact details
- 04Return score and recommendations
Use cases
- 01Reviewing a site before EU launch
- 02Auditing website privacy compliance
- 03Monitoring sites for privacy issues
MCP support
Exposes the compliance_scan_gdpr tool to MCP clients, which accepts a website URL and returns a JSON compliance report. Calls use x402 micropayments in USDC on Base.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gdpr-scanner.api.klymax402.com/mcpclaude mcp add --transport sse br0ski777-gdpr-scanner https://gdpr-scanner.api.klymax402.com/mcp{"mcpServers":{"br0ski777-gdpr-scanner":{"type":"sse","url":"https://gdpr-scanner.api.klymax402.com/mcp"}}}Open in Cursor{"servers":{"br0ski777-gdpr-scanner":{"type":"sse","url":"https://gdpr-scanner.api.klymax402.com/mcp"}}}Open in VS Code{"mcpServers":{"br0ski777-gdpr-scanner":{"type":"sse","url":"https://gdpr-scanner.api.klymax402.com/mcp"}}}{"mcpServers":{"br0ski777-gdpr-scanner":{"serverUrl":"https://gdpr-scanner.api.klymax402.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEGDPR Scanner API
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.
Quickstart -- MCP
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
{
"mcpServers": {
"gdpr-scanner": {
"url": "https://gdpr-scanner.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
curl "https://gdpr-scanner.api.klymax402.com/api/scan?url=https://example.com"
# -> 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
| 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_gdpr
Use 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:
{"url":"https://example.com","complianceScore":72,"cookieConsent":{"detected":true,"type":"banner"},"privacyPolicy":{"found":true,"url":"/privacy"},"thirdPartyTrackers":["Google Analytics","Facebook Pixel"],"recommendations":["Add DPO contact info","Add data retention policy"]}
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_gdpr
Use 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:
{"url":"https://example.com","complianceScore":72,"cookieConsent":{"detected":true,"type":"banner"},"privacyPolicy":{"found":true,"url":"/privacy"},"thirdPartyTrackers":["Google Analytics","Facebook Pixel"],"recommendations":["Add DPO contact info","Add data retention policy"]}
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).
Example agent prompts
- "Check a website's GDPR compliance"
- "Check a website's GDPR compliance"
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.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.