Cookie CMP Scanner
Pricing
from $15.00 / 1,000 browser page checkeds
Inventory cookies, consent banners, CMP vendor hints, Consent Mode signals, tracker categories, and privacy risk recommendations from supplied page snapshots.
Connect the Cookie CMP Scanner — browser, screenshot, and rendered-page Actor to an AI application through the Apify MCP server. MCP clients with OAuth support sign you in to Apify without an API token.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/cookie-cmp-scanner" } }}Add the configuration above to your project's .mcp.json file for Claude Code, then run /mcp in Claude Code to sign in to Apify. It connects to the hosted Apify MCP server with the Cookie CMP Scanner — browser, screenshot, and rendered-page Actor already loaded. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
For other MCP clients, get a client-specific configuration with the Cookie CMP Scanner — browser, screenshot, and rendered-page Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,junipr/cookie-cmp-scanner.
You can connect to the Apify MCP server using an MCP client that supports Streamable HTTP.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.