Cookie Consent Audit MCP Server
Related Servers
Alternatives to Cookie Consent Audit MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables AI agents to check a list of websites by running an Apify Actor through one tool, returning per-site tech stack, on-page SEO issues and score, robots.txt rules for AI crawlers, sitemap, llms.txt presence, and an AI-readiness score. Supports local stdio operation with an Apify token for tool calls.8MIT- AlicenseAqualityAmaintenanceEnables AI coding agents to generate LGPD-compliant cookie banners by detecting trackers in local projects, and to scan published sites for privacy violations, returning actionable results.1857 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables automated evaluation of one or many domains in a real browser for accessibility conformance, returning one row per domain with the issues automated checks find by severity, top failing rules, sample elements, a 0–100 score, and European Accessibility Act exposure signals.MIT

honestkit-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to access fourteen web-data tools for scraping, SEO and site auditing, extraction, validation, enrichment, and screenshots through Apify actors. It runs those tools on the user's own Apify account via an API token.MIT
pageguard-mcpofficial
AlicenseAqualityFmaintenanceScan any project or website for privacy compliance issues directly in your AI coding tool. Detects tracking tech, cookies, and third-party data collection. Works in Claude Code, Cursor, and Windsurf.39 npm1MIT
@guardbee/mcp-complianceofficial
AlicenseNot gradedqualityFmaintenanceEnables compliance checking against KVKK, GDPR, and CCPA via the GuardBee API, including privacy policy analysis, cookie banner detection, requirements listing, and framework comparison.223 npmMIT
TDQS
Scored across 1 tool
With only a single tool in the set, there is no possibility of confusing it with another. Its purpose—auditing cookie consent behavior across domains—is stated unambiguously and covers a clear, distinct scope.
The lone tool follows a clean verb_noun snake_case convention (audit_cookie_consent). With one tool there is no opportunity for inconsistent conventions to arise.
A single tool is on the thin side for a server purpose; 3-15 is typically well-scoped. However, the tool is heavily parameterized and performs multi-domain, multi-session batch auditing, so it earns its place rather than being trivial.
The audit itself is thorough, but the surface has a notable gap: the description mentions failed runs are returned 'with its run ID', implying a way to look up or re-fetch run results, yet no such retrieval/list/status tool exists. Agents cannot query past runs or monitor async audits, creating a dead end.