Cookie Consent Compliance Scanner

Start a cookie consent compliance scan on the given URL. The scan runs asynchronously in the background. This tool returns a run_id immediately — the actual scan takes 60–120 seconds. Use get_scan_status(run_id) to poll for completion, then call get_scan_report(run_id) or get_...

Check whether a scan is still running. Poll this every 10–15 seconds after calling scan_url. When done=True, call get_scan_report or get_failing_checks to retrieve results.

Retrieve the compliance report for a completed scan. Always call get_scan_status first to confirm done=True. For a focused view of what needs fixing, prefer get_failing_checks instead.

Return only the FAIL and PARTIAL checks from a completed scan. This is the most useful tool for an agent writing a compliance summary or remediation plan — it omits all the passing checks and focuses entirely on what needs to be fixed, with actionable recommendations for each...

List your recent scans (or recent public scans if anonymous). Returns scans ordered most-recent first. Use the run_id from any row to retrieve the full report with get_scan_report or get_failing_checks.