PrivacyPill MCP server
app.lovable.privacy-pill-consent-studio/privacypillprivacy-pill-consent-studio.lovable.appstreamable-httpv1.0.0Scanned
GDPR cookie banners with Consent Mode v2, plus a free scan of what loads before consent.
9 tools: 4 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the PrivacyPill MCP server can do
The PrivacyPill MCP server is published by privacy-pill-consent-studio.lovable.app, a domain the MCP Registry verified. It has 9 tools. It can create or change data (4 tools: pre_consent_scan, create_site, configure_banner and run_compliance_scan), but cannot delete data. 5 tools only read.
3 tools bring in text other people can write (pre_consent_scan, get_embed_snippet and run_compliance_scan); 2 tools can send data out of your system (pre_consent_scan and run_compliance_scan).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 4Claude Code: ask
configure_bannerUpdate a site's cookie banner: layout (pill, bar, modal, corner), colours or preset, categories, services, Google Consent Mode v2, languages and wording.No findings
Why it is in this group
- The description's first verb is "update": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_siteAdd a domain to PrivacyPill and create its cookie banner.No findings
Why it is in this group
- The name "create_site" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
pre_consent_scanFree, 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…Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
run_compliance_scanScan 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 compliance score.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "run_compliance_scan" says "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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 compliance score. Scans of your own domains are saved; apply=true adds the detected services to that site's banner.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 5Show 5 read-only tools
get_accountShow the signed-in PrivacyPill account: number of sites, licenses (Free, Pro, Lifetime) and limits.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it Show the signed-in PrivacyPill account: number of sites, licenses (Free, Pro, Lifetime) and limits.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_embed_snippetGet the one-line PrivacyPill embed (with Consent Mode fallback) for a site, plus install steps for HTML, Google Tag Manager, WordPress, Shopify and Webflow.Reads text others writeNo findings
Why it is in this group
- The name "get_embed_snippet" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "html": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_siteGet one site with its full cookie banner settings (layout, colours, categories, Consent Mode, languages).No findings
Why it is in this group
- The name "get_site" says "get": a word for reading.
Description, as the server wrote it Get one site with its full cookie banner settings (layout, colours, categories, Consent Mode, languages).
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_banner_presetsList the built-in banner colour presets and the allowed layouts, languages and categories.No findings
Why it is in this group
- The name "list_banner_presets" says "list": a word for reading.
Description, as the server wrote it List the built-in banner colour presets and the allowed layouts, languages and categories.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_sitesList the domains (sites) on the PrivacyPill account with their plan, site key and last scan score.No findings
Why it is in this group
- The name "list_sites" says "list": a word for reading.
Description, as the server wrote it List the domains (sites) on the PrivacyPill account with their plan, site key and last scan score.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://kcnskqhvzxbsaauifxtd.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://privacy-pill-consent-studio.lovable.app/mcp: tools/list returned 10 tools to an anonymous client, including pre_consent_scan (write), consent_mode_check (write), create_site (write), configure_banner (write), run_compliance_scan (write)
Posture changes
- Nov 14, 2026
- Tools that change things, listed without credentials: 4 to 5
- Nov 7, 2026
- RFC 9728 protected resource metadata: https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource to https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource/mcp
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 4 -> 5.View diff
- Tools that change things, listed without credentials: 4 to 5
Tools6 changed.~6 changedView diff
- Changed:configure_bannerChanges thingsinputSchema
- Changed:create_siteChanges thingsinputSchema
- Changed:get_embed_snippetOnly readsinputSchema
- Changed:get_siteOnly readsinputSchema
- Changed:pre_consent_scanChanges thingsinputSchema
- Changed:run_compliance_scanChanges thingsinputSchema
PostureRemote posture changed. RFC 9728 protected resource metadata: https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource -> https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource/mcp.View diff
- RFC 9728 protected resource metadata: https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource to https://privacy-pill-consent-studio.lovable.app/.well-known/oauth-protected-resource/mcp
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http privacypill https://privacy-pill-consent-studio.lovable.app/mcpclaude mcp add --transport http privacypill https://privacy-pill-consent-studio.lovable.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__privacypill__get_account",
"mcp__privacypill__list_sites",
"mcp__privacypill__get_site",
"mcp__privacypill__get_embed_snippet",
"mcp__privacypill__list_banner_presets"
],
"ask": [
"mcp__privacypill__pre_consent_scan",
"mcp__privacypill__create_site",
"mcp__privacypill__configure_banner",
"mcp__privacypill__run_compliance_scan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as privacypill. Review it before you use it.
Capability tags behind 3 rules
- mcp__privacypill__pre_consent_scan untrusted-input, outbound
- mcp__privacypill__get_embed_snippet untrusted-input
- mcp__privacypill__run_compliance_scan untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.lovable.privacy-pill-consent-studio/privacypill/verify?hash=29a6dd7e7fd63c8c2acf43dbf8e4284435b9da3fa0289514af57e7d347413e31" | jq -e '.changed == false'Pinned hash 29a6dd7e7fd6, from Nov 12, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.lovable.privacy-pill-consent-studio/privacypill/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.lovable.privacy-pill-consent-studio/privacypill)Source: MCP Registry. Synced Oct 30, 2026, 17:17 UTC.
PrivacyPill MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PrivacyPill MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PrivacyPill MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PrivacyPill MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the PrivacyPill MCP server have?
- 9 tools: 4 write, 5 read. pre_consent_scan, create_site, configure_banner, run_compliance_scan, get_account, list_sites, get_site, get_embed_snippet and 1 more.
Does the PrivacyPill MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PrivacyPill MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): pre_consent_scan and run_compliance_scan.
Has the PrivacyPill MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.