Skip to main content
Glama
mambalabsdev

Cookie Consent Audit MCP Server

Related Servers

Alternatives to Cookie Consent Audit MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      A
      quality
      F
      maintenance
      Scan 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.
      3
      9 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables compliance checking against KVKK, GDPR, and CCPA via the GuardBee API, including privacy policy analysis, cookie banner detection, requirements listing, and framework comparison.
      223 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues