# CookieYes MCP Server

> CookieYes' hosted MCP server lets an agent list sites, check whether cookie banners are live, read scan and GDPR or CCPA compliance results, start cookie scans and change banner colours and layout, over OAuth 2.1.

- Canonical: https://www.anchorterminal.com/tools/cookieyes-mcp
- Pricing: https://www.anchorterminal.com/tools/cookieyes-mcp#pricing
- Reviews: https://www.anchorterminal.com/tools/cookieyes-mcp#reviews
- Markdown: https://www.anchorterminal.com/tools/cookieyes-mcp.md (~3,850 tokens)
- Slim: https://www.anchorterminal.com/tools/cookieyes-mcp.min.md (~1,080 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/cookieyes-mcp.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT cookieyes-mcp.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-08

## Overview

**Grade D · 47.5/100 · rank #1153 of 1510 · #17 in CMS & website publishing · not agent-ready · confidence medium**


## Assessment

CookieYes' MCP server is small and careful, with 10 tools marked read-only or write, OAuth 2.1 behind an owner switch, and no personal data or consent logs exposed. It's on the Free plan too. Little else is published, no changelog, limits or llms.txt, and the status page needs script to read.

## Facts

| Field | Value |
| --- | --- |
| Vendor | CookieYes Limited (https://www.cookieyes.com) |
| Kind | MCP server |
| Category | CMS & website publishing (https://www.anchorterminal.com/categories/cms) |
| Transport | Streamable HTTP |
| Endpoint | `https://app.cookieyes.com/mcp` |
| Auth | OAuth · OAuth 2.1 with PKCE issuing a scoped token. The account owner must first turn on 'Enable OAuth-based access' under MCP access, and can turn it off for every client. |
| Pricing | Freemium (Freemium) · Works on every plan, including Free, with plan-based limits on some tools. Paid plans from $10 a month with a 14-day free trial; annual billing gives two months free (checked 2026-11-07). |
| x402 | No · No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07). |
| Licence | unknown |
| Tools exposed | 10 |
| MCP registry name | `com.cookieyes/mcp` |
| Docs | https://www.cookieyes.com/documentation/mcp-server/ |
| llms.txt | not found |
| Surface listed | The hosted MCP server at app.cookieyes.com/mcp, read from cookieyes.com on 7 November 2026. Only an MCP initialize was sent, which asked for sign-in |
| Category | cms, since it changes what a website shows; there is no consent-management category |
| Capabilities | compliance.cookies, compliance.gdpr, web.scan |
| Tags | official, hosted, mcp, remote-mcp, oauth, freemium, free-tier, mcp-registry |
| JSON | https://www.anchorterminal.com/api/v1/tools/cookieyes-mcp.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-07 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 30 | 6.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 46 | 7.5 |
| Agent ergonomics | 13% | 16.2 | 66 | 10.7 |
| Security & auth | 14% | 17.5 | 61 | 10.7 |
| Payments & pricing | 10% | 12.5 | 30 | 3.8 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 53 | 4.6 |
| Transparency & trust (editorial 35, provenance 61) | 7% | 8.8 | 48 | 4.2 |
| Negative events | up to −15 | up to −15 | none recorded | 0 |
| **Total** | | | | **47.5 → D** |

### Why each score

- Reliability 30 (checked 2026-11-07): A status page at status.cookieyes.com that renders only with script, so components and history weren't read (10 of 20). No history (5). Plan-based tool limits mentioned without numbers (5 of 15). No retry guidance (0). No SLA found (0). Not labelled beta (10). 10 + 5 + 5 + 0 + 0 + 10 = 30.
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 46 (checked 2026-11-07): Schemas not read without sign-in (15 of 25). No llms.txt found in the pages read (0). A table gives each of the 10 tools a type and a description, with example prompts (15 of 20). Inputs not verifiable (5 of 15). Example prompts for every tool, FAQ on connection errors (8 of 15). Registry version 1.0.0, no changelog (3 of 15). 15 + 0 + 15 + 5 + 8 + 3 = 46.
- Agent ergonomics 66 (checked 2026-11-07): 10 tools (25). Domain-scoped calls; no paging needed for the data involved (10 of 20). Connection errors covered in the FAQ (8 of 20). Every tool marked Read-only or Write, with client confirmation for writes (15 of 20). Few inputs; no SDKs (8 of 15). 25 + 10 + 8 + 15 + 8 = 66.
- Security & auth 61 (checked 2026-11-07): OAuth 2.1 with PKCE and a scoped token, behind an owner switch (28 of 30). Seven of ten tools are read-only, the owner can turn MCP off, and writes are confirmed in the client (15 of 20). Personal data, consent logs and cookie values are never exposed to the server (10). No audit log found (0). security.txt points to the support address; no certifications read (8 of 20). 28 + 15 + 10 + 0 + 8 = 61.
- Payments & pricing 30 (checked 2026-11-07): No machine payment protocol (0). Plan prices public (10). Free plan, MCP included (20). A person signs up and an owner enables access (0). 0 + 10 + 20 + 0 = 30.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 53 (checked 2026-11-07): Registry entry com.cookieyes/mcp updated 2 November 2026 (30). No dated releases found (0). Documentation and support; no changelog (8 of 15). Official registry entry under its own namespace (15). No package to read (0). 30 + 0 + 8 + 15 + 0 = 53. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
- Transparency & trust 48 (checked 2026-11-07): Closed service; the privacy policy names CookieYes Limited under EU and UK data protection law; terms not found at /terms-of-service/ (10 of 30). Personal data deleted on account closure, otherwise kept as long as needed (20 of 30). No deprecation policy (0). Service providers described by role, no list (5 of 20). 10 + 20 + 0 + 5 = 35.

Fix list, everything this grade says the listing lacks, the biggest gain first (13 items). What it covers is at https://www.anchorterminal.com/fixes/cookieyes-mcp.md (JSON https://www.anchorterminal.com/fixes/cookieyes-mcp.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "cookieyes-mcp", "plan": "read"}`, free while the beta runs

### What we couldn't check

- Terms and certifications not read
- People, ownership and investors not researched

### Sources

- MCP server docs: <https://www.cookieyes.com/documentation/mcp-server/> (seen 2026-11-07)
- pricing: <https://www.cookieyes.com/pricing/> (seen 2026-11-07)
- privacy policy: <https://www.cookieyes.com/privacy-policy/> (seen 2026-11-07)
- security.txt: <https://www.cookieyes.com/.well-known/security.txt> (seen 2026-11-07)
- lead, awesome-remote-mcp-servers pull request #3626: <https://github.com/punkpeye/awesome-remote-mcp-servers/pull/3626> (seen 2026-11-07)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/cookieyes-mcp/history.json

- 2026-11-07: graded 47.5 D (methodology 0.7)

## Who's behind it (provenance 61/100, checked 2026-11-07)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | CookieYes Limited | 20/20 |
| Domain age | cookieyes.com, no registry record we could read | 0/15 |
| Endpoint on the vendor's domain | app.cookieyes.com | 15/15 |
| Terms of service | not found | 0/10 |
| Privacy policy | published, not read by us yet | 4/10 |
| Status page | status.cookieyes.com | 10/10 |
| Changelog | not found | 0/10 |
| security.txt | valid | 10/10 |
| People named | not researched yet | n/a |
| Support route | help pages | 5/5 |

Not looked up: RDAP isn't requested under the 1 November 2026 rules.

security.txt lists support@cookieyes.com and expires 7 May 2027.

The terms weren't found at /terms-of-service/.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0.


**Privacy policy** (https://www.cookieyes.com/privacy-policy/), not read yet.


## Humans behind the project (researched 2026-11-07 from public pages, not part of the grade)

### Key people

- No people named yet.
- Note: People, ownership and investors weren't researched in this batch (7 November 2026, leads from the awesome-remote-mcp-servers pull requests).

### Getting support

- Help: https://www.cookieyes.com/documentation/mcp-server/
- Sources: https://www.cookieyes.com/documentation/mcp-server/

## Live (updated 2026-11-08 00:43 UTC)

- Right now: up, HTTP 401, 52 ms, checked 2026-11-08 00:43 UTC (mcp-initialize on `https://app.cookieyes.com/mcp`, asks for auth)
- Uptime 24h 100.0% (61 probes) · 30 days 100.0% (61 probes) · p50 84 ms · p95 157 ms
- Vendor status page: not read, no machine-readable status found
- Always current: https://www.anchorterminal.com/api/v1/live/cookieyes-mcp.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Strengths

- 10 tools, each marked read-only or write
- OAuth 2.1 with PKCE behind an account-owner switch
- Personal data, consent logs and cookie values are never exposed
- Available on the Free plan

## Weaknesses

- No changelog or published limits
- No audit log of agent calls
- Status page unreadable without script
- Terms not found at the usual path



## Before you call it (notes for agents)

1. Ask the account owner to enable OAuth-based access first
2. Confirm with the user before changing banner colours or layout
3. Run trigger_cookie_scan, then read get_scan_results once it finishes

## Connect

Claude Code:

```bash
claude mcp add cookieyes --transport http https://app.cookieyes.com/mcp
```

MCP client configuration:

```json
{
  "mcpServers": {
    "cookieyes": {
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}
```

Through letme: https://letme.dev/cookieyes-mcp (letme picks it for compliance.cookies, the top-graded tool for the job, letme picks it for compliance.gdpr, the top-graded tool for the job, letme picks it for web.scan, the top-graded tool for the job). letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| DatoCMS | BB | 74.4 | 85 | same category (CMS & website publishing) | no | https://www.anchorterminal.com/tools/datocms.md |
| Sanity | BB | 72.7 | 121 | same category (CMS & website publishing) | no | https://www.anchorterminal.com/tools/sanity.md |
| Cosmic | BB | 72.5 | 124 | same category (CMS & website publishing) | no | https://www.anchorterminal.com/tools/cosmic.md |
| Kontent.ai | BB | 70.6 | 194 | same category (CMS & website publishing) | no | https://www.anchorterminal.com/tools/kontent-ai.md |
| Webflow | BB | 70.4 | 200 | same category (CMS & website publishing) | no | https://www.anchorterminal.com/tools/webflow.md |
| Strapi | B | 67.7 | 309 | same category (CMS & website publishing) | no | https://www.anchorterminal.com/tools/strapi.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- Tools list_domains, get_website_details, get_embed_code, list_banners, get_banner_status, update_banner_colours, update_banner_layout, get_scan_results, get_compliance_status and trigger_cookie_scan (source: <https://www.cookieyes.com/documentation/mcp-server/>)
- Works on all plans, including Free, with plan-based usage limits on some tools (source: <https://www.cookieyes.com/documentation/mcp-server/>)
- Personal data, consent logs and cookie values are never exposed to the server (source: <https://www.cookieyes.com/documentation/mcp-server/>)

- #17 of 18 in Best headless CMS and website publishing for AI agents: https://www.anchorterminal.com/best/cms/index.md
- All 136 cms comparisons: https://www.anchorterminal.com/compare/cms/index.md

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on cookieyes.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "cookieyes-mcp", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/cookieyes-mcp"><img src="https://www.anchorterminal.com/badges/cookieyes-mcp.svg" alt="CookieYes MCP Server on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![CookieYes MCP Server on Anchor Terminal](https://www.anchorterminal.com/badges/cookieyes-mcp.svg)](https://www.anchorterminal.com/tools/cookieyes-mcp)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/cookieyes-mcp">CookieYes MCP Server on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say CookieYes MCP Server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/cookieyes-mcp-dark.png
- Light: https://www.anchorterminal.com/assets/share/cookieyes-mcp-light.png

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
