Robin Saige we check the tools AI agents call

Cookie Consent Compliance Scanner

io.github.vincentn-waivern/cookie-checker-gdpr-ccpa-gcmv2

Cookie consent scanner: GDPR, CCPA, GCMv2. PASS/FAIL compliance checklists with fix recommendations.

— the operator's own registry description reported

Publisher io.github.vincentn-waivern · first seen 2026-08-12 · endpoint https://consent-analyser-emea.waivern.com/mcp

block
verdict
dead-listing
cluster
http_error
answers
tools served

Dependency rating derived

block
block — dead / unreachable · kind unknown · V n/a
block — because dead / unreachable ●, no confirmed drift in 2 probes ●; not yet checked: harness, truth (0 runs)

Cluster dead-listing · distinctiveness —. Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersdead_listing
latency207 ms
protocolunknown
authn/a
Can it be used? Q4 · observed
capabilities0
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_67121691e77bc423040f248a · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?dead / unreachable — 2 probes ●evidence ↓
Q2What is it?kind unknown ○ evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?truth not yet run · no drift ●evidence ↓
Q5What company does it keep?dead-listing · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-08-14outcomehttp_error (was ok_tools)
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

no tool inventory served

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

Looking for an alternative?

This server doesn't answer, but these live, allow-verdict servers describe themselves similarly — similar by what they say they do — never verified drop-in replacements; check each one before depending on it.

serververdictshared terms
io.github.ark-forge/mcp-eu-ai-act
EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected.
allowconsent, cookie, gdpr, scanner
io.github.retampweb/pa1m-seo
Pay-per-call SEO agent: keyword research, SERP analysis, on-page optimization. x402, USDC on Base.
allowccpa, consent, cookie, gdpr
io.github.marcosnovo/lexvibe
One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.
allowccpa, consent, cookie, gdpr
com.scanlabsai/scanner
Scan a website for vulnerabilities: OWASP Top 10, CVEs, SSL, headers - with plain-English fixes
allowccpa, gdpr, scanner
io.github.Br0ski777/gdpr-scanner
Scan website GDPR compliance: consent, privacy policy, trackers. Score 0-100. x402.
allowconsent, cookie, gdpr
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T20:00:19Zhttp_error404207
2026-08-12T05:35:31Zok_tools2001412025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.vincentn-waivern/cookie-checker-gdpr-ccpa-gcmv2.svg)](https://robinsaige.com/s/io.github.vincentn-waivern/cookie-checker-gdpr-ccpa-gcmv2)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview