# GDPR Scanner API MCP server

Scan website GDPR compliance: consent, privacy policy, trackers. Score 0-100. x402.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-br0ski777-gdpr-scanner
- Repository: https://github.com/Br0ski777/gdpr-scanner-x402
- Website: https://github.com/Br0ski777/gdpr-scanner-x402

## Install
- Endpoint: https://gdpr-scanner.api.klymax402.com/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://gdpr-scanner.api.klymax402.com/mcp

## Tools
- 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.

Returns: 1. complianceScore (0-100) 2. cookieConsent (detected boolean, type) 3. privacyPolicy (found boolean, url) 4. termsOfService (found boolean) 5. dpoContact (found boolean, email) 6. dataRetention (mentioned boolean) 7. thirdPartyTrackers array (Google Analytics, Facebook Pixel, etc.) 8. recommendations array.

Example output: {"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"]}

Use this BEFORE launching a website in the EU, FOR compliance audits, due diligence on acquisitions, and regular privacy monitoring.

Do NOT use for PII in text -- use compliance_detect_pii instead. Do NOT use for tech detection -- use website_detect_tech_stack instead. Do NOT use for HTTP security headers -- use network_analyze_headers instead. Endpoint: https://gdpr-scanner.api.klymax402.com/mcp
- 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.

Returns: 1. complianceScore (0-100) 2. cookieConsent (detected boolean, type) 3. privacyPolicy (found boolean, url) 4. termsOfService (found boolean) 5. dpoContact (found boolean, email) 6. dataRetention (mentioned boolean) 7. thirdPartyTrackers array (Google Analytics, Facebook Pixel, etc.) 8. recommendations array.

Example output: {"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"]}

Use this BEFORE launching a website in the EU, FOR compliance audits, due diligence on acquisitions, and regular privacy monitoring.

Do NOT use for PII in text -- use compliance_detect_pii instead. Do NOT use for tech detection -- use website_detect_tech_stack instead. Do NOT use for HTTP security headers -- use network_analyze_headers instead. Endpoint: https://gdpr-scanner.api.klymax402.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.Br0ski777
- Version: 1.1.0
- Runtime: Sse
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 16, 2026
- Source: https://registry.modelcontextprotocol.io
