GDPR Scanner API
Scan website GDPR compliance: consent, privacy policy, trackers. Score 0-100. x402.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport sse gdpr-scanner-api 'https://gdpr-scanner.api.klymax402.com/mcp'{
"mcpServers": {
"gdpr-scanner-api": {
"type": "sse",
"url": "https://gdpr-scanner.api.klymax402.com/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
GDPR 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 bodyAny 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
Questions fréquentes
Qu'est-ce que GDPR Scanner API ?
Scan website GDPR compliance: consent, privacy policy, trackers. Score 0-100. x402.
Comment installer GDPR Scanner API ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport sse gdpr-scanner-api 'https://gdpr-scanner.api.klymax402.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour GDPR Scanner API ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
GDPR Scanner API est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient GDPR Scanner API ?
Il est publié par Br0ski777. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.