PrivacyPill
REMOTE · PRIVACY-PILL-CONSENT-STUDIO.LOVABLE.APP
GDPR cookie banners with Consent Mode v2, plus a free scan of what loads before consent.
Available components
Last scanned (17 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1198 tokens (~119/item across 10 items; 10 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- “consent_mode_check” added an optional parameter “lang” cosmetic
- “pre_consent_scan” added an optional parameter “lang” cosmetic
- “run_compliance_scan” reworded the description of “lang” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 20 Nov 26 0
- Tool “run_compliance_scan” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “run_compliance_scan” added an optional parameter “lang” cosmetic
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- Tool “consent_mode_check” rewrote its description, which is the text the model reads security
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 89 → 101 ▼ functional
- Server version: 1.1.1 → 1.2.0 functional
- New tool “consent_mode_check” functional
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://privacy-pill-consent-studio.lovable.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lovable.app | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a0305f14b2a99af130a9e43af07d3e5 |
| SANs: lovable.app, *.lovable.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of privacy-pill-consent-studio.lovable.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| lovable.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource"
Bearer realm="mcp", resource_metadata="https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://privacy-pill-consent-studio.lovable.app/mcp |
| Authorisation server | https://kcnskqhvzxbsaauifxtd.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://privacy-pill-consent-studio.lovable.app/mcp | Verified | 200 | |
| http (plaintext) | http://privacy-pill-consent-studio.lovable.app/mcp | HTTPS enforced | 301 | https://privacy-pill-consent-studio.lovable.app/mcp |
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 →
configure_banner Configure banner ~150
Update a site's cookie banner: layout (pill, bar, modal, corner), colours or preset, categories, services, Google Consent Mode v2, languages and wording. Only the fields you pass change. Pro sites can also switch geo-targeting and monthly rescans.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | – | Banner fields to change; nested objects merge. |
| domain | string | – | Change the domain (bare domain). |
| geo_targeting | boolean | – | Pro: only show the banner where consent law applies. |
| monthly_rescan | boolean | – | Pro: rescan the site automatically every month. |
| name | string | – | – |
| site_id | string | yes | Site id from list_sites or create_site. |
No output schema declared.
No examples provided.
consent_mode_check Check Google Consent Mode v2 setup (free) ~271
Free, no sign-in: fetch a public page as a first-time visitor and check its Google Consent Mode v2 setup — whether gtag.js or Google Tag Manager is present, whether a consent default is set before the tags load, the default values of ad_storage, analytics_storage, ad_user_data and ad_personalization, whether wait_for_update, url_passthrough and ads_data_redaction are used, whether a consent banner is detected, and which tags fire before consent. Returns pass / warning / fail per check with plain-language fixes and copy-paste default snippets. It also reads the consent banner's own settings and, in country_rules, checks the banner rules that can be tested from outside for Italy (Garante 2021 guidelines) and Spain (AEPD cookie guide, July 2023 update), each with its source and a fix (automatic check, not legal advice). Static check (no JavaScript runs), so consent updates after a click aren't visible. Shares the free quota of 10 checks per hour per visitor with pre_consent_scan.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the report's text: en (default) or nl (Dutch, with Dutch study figures). |
| url | string | yes | Public page to check, e.g. https://example.com |
No output schema declared.
No examples provided.
create_site Create site ~105
Add a domain to PrivacyPill and create its cookie banner. Returns the site, its banner settings and the embed snippet. The free plan includes one site.
| Name | Type | Req | Description |
|---|---|---|---|
| design | object | – | Optional starting banner settings; see configure_banner for the fields. |
| domain | string | yes | Bare domain such as example.com (no https://). |
| license_id | string | – | Attach a Pro or Lifetime license from get_account. |
| name | string | – | Friendly name shown in the dashboard. |
No output schema declared.
No examples provided.
get_account Get account ~32
Show the signed-in PrivacyPill account: number of sites, licenses (Free, Pro, Lifetime) and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_embed_snippet Get embed snippet ~62
Get the one-line PrivacyPill embed (with Consent Mode fallback) for a site, plus install steps for HTML, Google Tag Manager, WordPress, Shopify and Webflow.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Site id from list_sites or create_site. |
No output schema declared.
No examples provided.
get_site Get site and banner settings ~45
Get one site with its full cookie banner settings (layout, colours, categories, Consent Mode, languages).
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Site id from list_sites or create_site. |
No output schema declared.
No examples provided.
list_banner_presets List banner presets ~26
List the built-in banner colour presets and the allowed layouts, languages and categories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sites List sites ~31
List the domains (sites) on the PrivacyPill account with their plan, site key and last scan score.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pre_consent_scan Check what loads before consent (free) ~149
Free, no sign-in: fetch a public page as a first-time visitor and report which trackers (GA4, Google Ads, Meta Pixel, TikTok, LinkedIn, Hotjar…) and cookies load before the visitor consents, which ones wait, which other sites the page contacts (e.g. Google Fonts), and how to fix it. Static check of the HTML and headers (no JavaScript runs). Limited to 10 checks per hour per visitor.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the report's text: en (default) or nl (Dutch, with Dutch study figures). |
| url | string | yes | Public page to check, e.g. https://example.com |
No output schema declared.
No examples provided.
run_compliance_scan Run compliance scan ~195
Scan a public web page for trackers (GA4, Google Ads, GTM, Meta Pixel, Hotjar, TikTok, LinkedIn…), cookies and Consent Mode setup, and get a 0–100 consent setup score with the reason for its grade (read from the page's HTML; not legal advice). Anything confirmed loading before consent caps the grade at D; what can't be confirmed lowers confidence, not the grade. Scans of your own domains are saved; apply=true adds the detected services to that site's banner.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | Add detected services and cookie names to the site's banner. |
| lang | string | – | Language of the grade reason: en, fr, de, it, es, nl (default en). |
| site_id | string | – | Save the scan to this site (otherwise matched by domain). |
| url | string | yes | Page URL, e.g. https://example.com |
No output schema declared.
No examples provided.
How do I install the PrivacyPill MCP server?
PrivacyPill is a hosted endpoint at https://privacy-pill-consent-studio.lovable.app/mcp, 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 · privacy-pill-consent-studio.lovable.app
claude mcp add --transport http app-lovable-privacy-pill-consent-studio-privacyp 'https://privacy-pill-consent-studio.lovable.app/mcp'
What is the PrivacyPill MCP server?
PrivacyPill is an MCP server listed in the public MCP registry as app.lovable.privacy-pill-consent-studio/privacypill. GDPR cookie banners with Consent Mode v2, plus a free scan of what loads before consent. This page covers its hosted endpoint (https://privacy-pill-consent-studio.lovable.app/mcp).
Is the PrivacyPill MCP server safe to use?
PrivacyPill scores 89 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 PrivacyPill MCP server expose?
PrivacyPill exposes 10 tools: pre_consent_scan, consent_mode_check, get_account, list_sites, get_site, and 5 more. Their descriptions and schemas cost roughly 1,066 tokens of context every time the server is loaded.
Does the PrivacyPill MCP server require authentication?
Yes. PrivacyPill asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the PrivacyPill MCP server still maintained?
PrivacyPill is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PrivacyPill MCP server?
VerifyMCP ran 13 checks on PrivacyPill, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.