Back to Browse

Bannerproof MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

EU cookie-consent audit: trackers before consent, Reject all, Consent Mode v2, TCF; evidence + fixes

About

EU cookie-consent audit: trackers before consent, Reject all, Consent Mode v2, TCF; evidence + fixes

Remote endpoints: streamable-http: https://api.bannerproof.app/mcp streamable-http: https://api.bannerproof.app/mcp/free

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "app-bannerproof-bannerproof": {
      "url": "https://api.bannerproof.app/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Bannerproof — cookie-consent audits for AI assistants and CI

Bannerproof checks a website the way a real first-time visitor from the EU sees it, and reports:

  • trackers, analytics/ad tags and tracking cookies that load before consent;
  • whether the cookie banner has “Reject all” on the first layer, and what still fires after Reject;
  • Google Consent Mode v2 state per signal (ad_storage, analytics_storage, ad_user_data, ad_personalization);
  • IAB TCF consent string before a choice and after Reject;
  • Global Privacy Control (informational in the EU);
  • cookies the site sets that its own cookie policy doesn’t mention;
  • third-party embeds that leak visitor data before consent (Google Fonts, YouTube, Maps, reCAPTCHA).

Every finding comes with the exact request as evidence, a concrete fix (13 languages) and the legal reference (ePrivacy Art. 5(3), GDPR, national law). Works with any consent platform — Cookiebot, Usercentrics, OneTrust, Complianz, CookieYes, Borlabs, iubenda or a custom banner.

This repository holds the public pieces: the MCP server listing, connection examples and a GitHub Action. The service itself runs at bannerproof.app.


1. MCP server (Claude, ChatGPT, Cursor, …)

Remote MCP server, Streamable HTTP, OAuth 2.0:

https://api.bannerproof.app/mcp

A free quick check works without an account (https://api.bannerproof.app/mcp/free). Full findings, monitoring, audits and evidence exports use a Bannerproof account — sign in with OAuth when your client asks, or use an API token from Settings.

ClientHow to connect
Claude (claude.ai / Desktop)Settings → Connectors → find Bannerproof in the directory, or add a custom connector with the URL above
Claude Codeclaude mcp add --transport http bannerproof https://api.bannerproof.app/mcp
Cursorsee examples/cursor-mcp.json
Clinesee llms-install.md
Other clientsadd an MCP server with the URL above (OAuth), or send Authorization: Bearer <API token>

Step-by-step guide: bannerproof.app/help/connect-claude-chatgpt

Tools

ToolWhat it doesAccount
quick_checkyes/no + score for any public sitefree
explain_findingwhat a finding means, why it matters, how to fix it, legal basisfree
get_capabilitieswhat the server checks and what each tool doesfree
get_findingsfull findings with evidence, fixes and legal referencesyes
scan_domainfresh scan of a monitored domainyes
compare_scanswhat changed since the previous scanyes
get_evidenceevidence pack (every request with phase and time, cookies, consent signals) as CSV/JSONyes
get_report_linkprivate report link to send to a client or developeryes
audit_domain / audit_domainsaudit any site, or up to 10 at once (1 audit credit each; failed scans are refunded)yes
get_audits_statusstatus of several audits at onceyes
list_domains, add_domain, scan_history, account_info, get_upgrade_linkaccount helpersyes

The server is listed in the official MCP Registry as app.bannerproof/bannerproof (server.json).


2. Deploy check (CI)

Fail a pipeline when a release breaks cookie consent. The domain must be monitored in your Bannerproof account; create an API token in Settings and store it as a secret.

GitHub Action

- uses: bannerproof/bannerproof@v1
  with:
    domain: example.com
    api-token: ${{ secrets.BANNERPROOF_TOKEN }}
    fail-on: new   # "new" = only issues this release added (default), "any" = any issue

Full workflow: examples/github-workflow.yml.

Any other CI

curl -fsS -X POST https://api.bannerproof.app/api/ci/check \
  -H "X-Api-Token: $BANNERPROOF_TOKEN" -H "Content-Type: application/json" \
  -d '{"domain":"example.com","failOn":"new"}'
HTTP statusMeaning
200pass
422fail — the JSON body lists new_issues
202still scanning — poll the poll URL from the body
429the domain was scanned less than 5 minutes ago (Retry-After header)
502the site couldn't be scanned

Webhook

In Settings you can also add a webhook: after every scan of a monitored domain Bannerproof POSTs a scan.completed event (score, new and resolved issues) signed with HMAC-SHA256 — X-Bannerproof-Signature: sha256=<hex of HMAC(secret, "<X-Bannerproof-Timestamp>.<body>")>.


Bannerproof is an automated technical check of what a site sends at scan time — not legal advice.

Support: support@bannerproof.app

Reviews

No reviews yet

Be the first to review this server!