Privacy MCP server

by thegridwork·io.github.thegridwork/privacy·v1.0.0·1 stars

Audit websites for GDPR, CCPA, and ePrivacy compliance — trackers, consent, and policies.

B78/100grade B

What users say

No reviews yet

Safety scan

B78/100

Adoption

New

1 stars48 downloads/wk

Reviews

Nobody has reviewed Privacy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

audit_privacywrite action
Run a comprehensive privacy audit on a website. Detects trackers (Google Analytics, Facebook Pixel, etc.), analyzes cookie consent mechanisms, checks privacy policy compliance, and reviews data collection forms. Evaluates against GDPR, CCPA, and ePrivacy Directive.
check_consent
Check if a website's cookie consent mechanism meets GDPR and ePrivacy requirements. Detects CMP platforms, reject options, pre-checked boxes, and cookie walls.
compare_privacy
Compare privacy practices of two websites side by side. Shows trackers, consent compliance, and overall scores for both.
scan_trackers
Quick scan to detect third-party trackers on a website. Lists all advertising, analytics, social, and fingerprinting trackers found with GDPR concerns for each.

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan15 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 168 days ago8/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 78/100; higher than 57% of 48,255 servers
Tools: 4; the typical server has 7
Tools that change things: 25%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 1; more than 65% of 28,688 servers
Downloads a week: 48; more than 40% of 12,191 servers with a package

What its tools let an agent do: 3 read · 1 change

Runs npx -y gridwork-privacy on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add privacy -- npx -y gridwork-privacy

From the Privacy repository's README, as published. We do not edit it. Read it on GitHub

MCP server that audits websites for GDPR, CCPA, and ePrivacy compliance.

Detects 30+ third-party trackers (Google Analytics, Facebook Pixel, TikTok, Criteo, etc.)
Analyzes cookie consent mechanisms (CMP detection, reject options, pre-checked boxes)
Checks privacy policy presence and required disclosures
Reviews data collection forms for sensitive fields
Classifies each tracker's GDPR concern level
Identifies specific regulatory articles for each finding

npx gridwork-privacy

{
  "mcpServers": {
    "gridwork-privacy": {
      "command": "npx",
      "args": ["-y", "gridwork-privacy"]
    }
  }
}

MIT — Gridwork

Nothing above is checked by us. What we check is on the safety report.

Is Privacy MCP server safe?: Mostly: it is graded B (78/100). Read the Privacy safety report
How do I install Privacy?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Privacy need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Privacy maintained?: The last commit was 206 days ago (2026-04-12). The latest release is v1.0.0.
How does Privacy compare with other MCP servers?: safety score 78/100 (higher than 57% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.