mcpbeat Sign in

CookieYes MCP Server

by cookieyes Your server? Claim it
answering

CookieYes is answering right now. Last checked 10 min ago.

Manage cookie banners, run cookie scans and check GDPR/CCPA compliance from your AI assistant.

Uptime history 33 hours of history
33 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
79 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check CookieYes every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add mcp --transport http https://app.cookieyes.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.cookieyes.com/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://app.cookieyes.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.cookieyes.com/mcp streamable-http sign-in 69 ms 10 min ago

Alternatives to CookieYes

same job, measured the same way
EyalSec
by eyalsec

Read your EyalSec security events, machines, runs and rules from an AI assistant.

170 installs/wk local only
L
Legal Doc Analyzer
by vpatser1

Contract analysis, risk assessment, version diffs, compliance checks (GDPR, CCPA, SOC2)

52 installs/wk local only
Compliance Checker
by guardbee

KVKK/GDPR/CCPA compliance checks for codebases

696 installs/wk local only
Compliance Checker
by 4hmetuyar

KVKK/GDPR/CCPA compliance checks for codebases

local only
Agentos
by imran-siddique

Build and manage policy-compliant AI agents with safety enforcement and compliance checking

61 installs/wk local only
Agent Verify
by ai-blockchain-ventures

Security checks for AI agents and MCP configs: 124 tested checks, from your AI coding assistant.

151 installs/wk local only
W
Wisewall MCP
by ti-ab

Manage WiseWall sites from an AI coding assistant — deploy, configure DNS, secrets, and plans.

68 installs/wk local only
MCP Geracompliance
by geraservicesuk

EU AI Act and GDPR compliance: checks, audits, generate policies.

44 installs/wk local only

CookieYes — questions

Answers built from our own checks of this server.

Why is there no tool list for CookieYes?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is CookieYes working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 79 ms. The bar chart above shows every period we have measured.
How do I connect CookieYes?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to CookieYes?
No API key is involved. CookieYes answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is CookieYes?
It answers our handshake in 79 ms on average, which is faster than 98% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.