# PrivacyPill (remote · privacy-pill-consent-studio.lovable.app)

GDPR cookie banners with Consent Mode v2, plus a free scan of what loads before consent.

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `privacy-pill-consent-studio.lovable.app`: 89/100 (this document), [markdown](https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio.md), [page](https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio)

## Channel facts

- Endpoint: `https://privacy-pill-consent-studio.lovable.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-lovable-privacy-pill-consent-studio-privacyp 'https://privacy-pill-consent-studio.lovable.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-lovable-privacy-pill-consent-studio-privacyp": {
      "url": "https://privacy-pill-consent-studio.lovable.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-lovable-privacy-pill-consent-studio-privacyp": {
      "type": "http",
      "url": "https://privacy-pill-consent-studio.lovable.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-lovable-privacy-pill-consent-studio-privacyp]
url = "https://privacy-pill-consent-studio.lovable.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lovable-privacy-pill-consent-studio-privacyp": {
      "type": "remote",
      "url": "https://privacy-pill-consent-studio.lovable.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-lovable-privacy-pill-consent-studio-privacyp --url 'https://privacy-pill-consent-studio.lovable.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-lovable-privacy-pill-consent-studio-privacyp:
    url: "https://privacy-pill-consent-studio.lovable.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-lovable-privacy-pill-consent-studio-privacyp": {
      "Transport": "http",
      "Url": "https://privacy-pill-consent-studio.lovable.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-lovable-privacy-pill-consent-studio-privacyp -t streamable-http -u 'https://privacy-pill-consent-studio.lovable.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-lovable-privacy-pill-consent-studio-privacyp": {
      "type": "http",
      "url": "https://privacy-pill-consent-studio.lovable.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 89, 0)

- [cosmetic] “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”

### 2026-11-20 (score 89, 0)

- [security] Tool “run_compliance_scan” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “run_compliance_scan” added an optional parameter “lang”

### 2026-11-19 (score 89, +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.

### 2026-11-17 (score 88, +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.

### 2026-11-15 (score 87, +1)

- [security] Tool “consent_mode_check” rewrote its description, which is the text the model reads

### 2026-11-14 (score 86, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 89 → 101
- [functional] Server version: 1.1.1 → 1.2.0
- [functional] New tool “consent_mode_check”

### 2026-11-13 (score 86, +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.

### 2026-11-11 (score 85, +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.

## MCP tools (10)

### `pre_consent_scan` (~149 tokens)

Check what loads before consent (free)

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.

Input parameters:

- `lang` (string): Language of the report's text: en (default) or nl (Dutch, with Dutch study figures).
- `url` (string, required): Public page to check, e.g. https://example.com

### `consent_mode_check` (~271 tokens)

Check Google Consent Mode v2 setup (free)

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.

Input parameters:

- `lang` (string): Language of the report's text: en (default) or nl (Dutch, with Dutch study figures).
- `url` (string, required): Public page to check, e.g. https://example.com

### `get_account` (~32 tokens)

Get account

Show the signed-in PrivacyPill account: number of sites, licenses (Free, Pro, Lifetime) and limits.

### `list_sites` (~31 tokens)

List sites

List the domains (sites) on the PrivacyPill account with their plan, site key and last scan score.

### `get_site` (~45 tokens)

Get site and banner settings

Get one site with its full cookie banner settings (layout, colours, categories, Consent Mode, languages).

Input parameters:

- `site_id` (string, required): Site id from list_sites or create_site.

### `create_site` (~105 tokens)

Create site

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.

Input parameters:

- `design` (object): Optional starting banner settings; see configure_banner for the fields.
- `domain` (string, required): 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.

### `configure_banner` (~150 tokens)

Configure banner

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.

Input parameters:

- `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, required): Site id from list_sites or create_site.

### `get_embed_snippet` (~62 tokens)

Get embed snippet

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.

Input parameters:

- `site_id` (string, required): Site id from list_sites or create_site.

### `run_compliance_scan` (~195 tokens)

Run compliance scan

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.

Input parameters:

- `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, required): Page URL, e.g. https://example.com

### `list_banner_presets` (~26 tokens)

List banner presets

List the built-in banner colour presets and the allowed layouts, languages and categories.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio#diagnostics

## Score history

- 2026-11-21: 89
- 2026-11-20: 89
- 2026-11-19: 89
- 2026-11-18: 88
- 2026-11-17: 88
- 2026-11-16: 87
- 2026-11-15: 87
- 2026-11-14: 86
- 2026-11-13: 86
- 2026-11-12: 85
- 2026-11-11: 85
- 2026-11-10: 84
- 2026-11-09: 84
- 2026-11-08: 83
- 2026-11-07: 83
- 2026-11-06: 82
- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79

## Common questions

### 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.

## Links

- Remote endpoint: https://privacy-pill-consent-studio.lovable.app/mcp
- Website: https://privacy-pill-consent-studio.lovable.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio.json
- HTML version of this page: https://verifymcp.io/servers/app-lovable-privacy-pill-consent-studio-privacypill/privacy-pill-consent-studio
