Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bannerproof

REMOTE · API.BANNERPROOF.APP · 2 COMPONENTS

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

69 Trust /100

Last scanned (5 hours ago)

Scores higher than 54% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2346 tokens (~130/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.bannerproof.app/mcp/free

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bannerproof.app CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 620e0f589a0ee13c9d2bf8b311edc193bc4
SANs: *.bannerproof.app, bannerproof.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.bannerproof.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
bannerproof.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.bannerproof.app/mcp/free Verified 200
http (plaintext) http://api.bannerproof.app/mcp/free HTTPS enforced 301 https://api.bannerproof.app/mcp/free
MCP tools · 18 exposed · ~2,188 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_info ~32

Shows the connected Bannerproof account: plan, how many monitored domains it allows and uses, and the remaining audit credits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

add_domain ~121

Adds a domain to weekly monitoring in the connected account (within the plan's domain limit) and runs its first scan. Requires a plan with a free domain slot; otherwise it returns an error that names the plan needed.

NameTypeReqDescription
domainstringyesThe website's domain, e.g. example.com
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

audit_domain ~208

Full audit of any website (for example a client's or a prospect's site) that is NOT monitored in the account. Spends 1 audit credit, so it is marked destructive and runs only with confirm=true. If the same site was audited in the last 24 hours, the earlier result is returned without spending a credit unless force_new=true. If the site can't be scanned, the credit is returned automatically.

NameTypeReqDescription
confirmbooleanyesConfirms spending 1 audit credit; without true the audit does not run
domainstringyesThe website's domain, e.g. client-site.com
force_newboolean–Run a new paid audit even if this site was audited in the last 24 hours
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

audit_domains ~181

Audits up to 10 websites at once (e.g. an agency's client list or prospects). Spends 1 audit credit per new audit and runs only with confirm=true; sites audited in the last 24 hours are reused without spending. If the account doesn't have enough credits for the whole list, nothing starts (no partial batch). A site that can't be scanned (down, blocking bots, too slow) is not charged — its credit is returned automatically. Returns a job_id per site — follow up with get_audits_status for all of them, then get_findings per domain.

NameTypeReqDescription
confirmbooleanyesConfirms spending 1 audit credit per new audit; without true nothing runs
domainsarrayyesThe websites' domains, e.g. ["client-a.com", "client-b.de"] — up to 10

No output schema declared.

No examples provided.

compare_scans ~119

Compares the latest scan of a monitored domain with the previous one (or with the newest scan on or before a given date): new issues, resolved issues, score change, banner and reject option changes. Use it to confirm a fix worked or to see what a site update broke.

NameTypeReqDescription
compare_with_datestring|null–Optional date (e.g. 2026-10-01): compare with the newest scan on or before that date instead of the previous one
domainstringyesA domain monitored in the connected account

No output schema declared.

No examples provided.

explain_finding ~171

Explains one finding in plain language: what it is, why it is a problem, how to fix it and which rule it relates to. Pass the tracker name exactly as get_findings returned it. Free, no account needed.

NameTypeReqDescription
languagestring|null–Language for the fix instructions: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Default en.
statusstring|null–What was found: fired_before_consent (default), still_active_after_reject, missing_reject_option, tcf_consent_after_reject or gpc_ignored
trackerstringyesThe tracker or cookie name from get_findings, e.g. 'Meta (Facebook) Pixel' or '_ga cookie'

No output schema declared.

No examples provided.

get_audits_status ~89

Status of several audits at once (e.g. the job_ids audit_domains returned): which are done with their score and issue count, which are still running, and which failed — with the reason. Failed scans are not charged: their audit credit goes back to the account automatically.

NameTypeReqDescription
job_idsarrayyesThe job_ids from audit_domains or audit_domain — up to 10

No output schema declared.

No examples provided.

get_capabilities ~48

Describes what Bannerproof checks, what each tool does, what needs an account and what it costs. Call this first when the user asks what this server can do or which tool to use.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_evidence ~93

Evidence pack of the latest scan of a domain: every tracker request in order with its phase (before consent / after Reject) and time, plus the cookies and consent signals. Returns a summary and download links (CSV and JSON, open without a login) for a client, a developer or a dispute. Works for monitored domains and audited sites.

NameTypeReqDescription
domainstringyesThe domain, e.g. example.com

No output schema declared.

No examples provided.

get_findings ~172

Full findings of the latest scan of a domain: which trackers and third-party requests fired before consent or kept running after 'Reject', the cookie banner's reject option, Google Consent Mode v2 signals, what happens after 'Accept', IAB TCF consent after Reject, Global Privacy Control, and a concrete fix and legal reference for each issue. Works for domains monitored in the account and for sites audited with audit_domain(s). For one finding in more depth use explain_finding.

NameTypeReqDescription
domainstringyesThe domain, e.g. example.com
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

get_quick_check_result ~99

Gets the result of a quick_check that was still running, by the job_id that quick_check returned.

NameTypeReqDescription
job_idstringyesThe job_id returned by quick_check
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

get_report_link ~114

Creates (or returns the existing) private link to the latest report of a domain, for sending to a client or developer — opens without a login. Works for monitored domains and audited sites.

NameTypeReqDescription
domainstringyesThe domain, e.g. example.com
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

get_scan_status ~101

Gets the status of a scan_domain or audit_domain that was still running, by the job_id it returned.

NameTypeReqDescription
job_idstringyesThe job_id returned by scan_domain or audit_domain
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

get_upgrade_link ~246

Returns a direct checkout link on bannerproof.app for a plan or audit credits (payment happens there, never in the chat). goal: 'audit' = one-off full report for one domain (€19), 'solo' = monitoring for 1 domain (€11/month), 'monitoring' = up to 7 domains (€49/month), 'agency' = up to 25 domains with white-label reports (€139/month), 'credits' = audit credits for checking any site (5 for €79, 15 for €199, 40 for €449). Prices include VAT; the checkout shows the final price.

NameTypeReqDescription
creditsinteger|null–For goal=credits: 5, 15 or 40
domainstring|null–The domain the purchase is for, if any (pre-fills it after checkout)
goalstringyesaudit, solo, monitoring, agency or credits
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

list_domains ~29

Lists the domains monitored in the connected Bannerproof account, with the latest score and whether issues were found.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quick_check ~180

Free check, no account needed: opens a public website like a first-time visitor and reports whether trackers or third-party requests fire before the visitor consents (GDPR/ePrivacy), with a 0–100 score. Returns only yes/no and the score; the full findings (which trackers, the exact requests, how to fix each one) are available with a connected Bannerproof account (get_findings). Results are cached for up to 7 days. This is an automated technical check, not legal advice.

NameTypeReqDescription
domainstringyesThe website's domain, e.g. example.com
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

scan_domain ~140

Runs a fresh scan of a domain monitored in the connected account (e.g. to check a fix). Waits up to about 40 seconds; if the scan is still running it returns a job_id for get_scan_status. A manual scan can be run once every 15 minutes per domain.

NameTypeReqDescription
domainstringyesA domain monitored in the connected account, e.g. example.com
languagestring|null–Language for the fix instructions and report links: en, de, fr, es, it, nl, da, sv, fi, no, et, pl or pt. Normally the language of the conversation. Default en.

No output schema declared.

No examples provided.

scan_history ~45

Score and issue count over time for a domain monitored in the account (newest first, up to 30).

NameTypeReqDescription
domainstringyesA domain monitored in the connected account

No output schema declared.

No examples provided.

Install

How do I install the Bannerproof MCP server?

Bannerproof is a hosted endpoint at https://api.bannerproof.app/mcp/free, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.bannerproof.app

# add to Claude Code
claude mcp add --transport http app-bannerproof-bannerproof 'https://api.bannerproof.app/mcp/free'
Common questions

What is the Bannerproof MCP server?

Bannerproof is an MCP server listed in the public MCP registry as app.bannerproof/bannerproof. EU cookie-consent audit: trackers before consent, Reject all, Consent Mode v2, TCF; evidence + fixes. This page covers its hosted endpoint (https://api.bannerproof.app/mcp/free).

Is the Bannerproof MCP server safe to use?

Bannerproof scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Bannerproof MCP server expose?

Bannerproof exposes 18 tools: quick_check, get_quick_check_result, account_info, list_domains, add_domain, and 13 more. Their descriptions and schemas cost roughly 2,188 tokens of context every time the server is loaded.

Does the Bannerproof MCP server require authentication?

No. We connected to Bannerproof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bannerproof MCP server still maintained?

Bannerproof is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.