PageGuard MCP

io.github.pageguardPublished by GitHub account pageguardv1.0.1Updated Oct 24, 2026

Privacy compliance scanning for AI coding tools. Detects tracking tech, cookies, and data gaps.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

PageGuard MCP lets an AI coding assistant scan projects and live websites for privacy compliance issues and generate legal documents.

What you can do
Scan a local project directory for tracking technologies, cookies and third-party data collection from package.json, config and .env files, without network access or an API key. Scan a live website URL for privacy compliance issues, returning a risk score and compliance gap analysis. Generate AI-written legal documents such as privacy policy, terms of service and cookie policy from a prior URL scan.
When to use it
Useful when you want an assistant to check a codebase or website for privacy and tracking concerns, or to draft privacy policies and related legal documents based on a site scan.
Requirements
Runs locally via npx (Node.js). Local scans need no key or network. URL scans and document generation require the PAGEGUARD_API_KEY environment variable; PAGEGUARD_API_URL optionally overrides the API base URL. Document generation requires paid credits.
Before you install
Local scans read package.json, config and .env files, which may contain secrets. URL scans and document generation send data to PageGuard's service and need PAGEGUARD_API_KEY. Document generation costs money ($19–$49 per item, bulk packs available), so confirm spending before generating.

Installation

In SourceWeft

  1. Open PageGuard MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

pageguard-mcp

MCP (Model Context Protocol) server that exposes PageGuard privacy compliance scanning as tools for AI coding assistants. Works with Claude Code, Cursor, Windsurf, ChatGPT, and any MCP-compatible environment.

What it does

  • Local scan — Detects tracking technologies, cookies, and third-party data collection from your project's package.json, config files, and .env files. No API key needed, no network requests.
  • URL scan — Scans a live website for privacy compliance issues including risk scoring and compliance gap analysis.
  • Document generation — Generates AI-written legal documents (privacy policy, terms of service, cookie policy, etc.) tailored to your detected technologies.

Installation

Claude Code

Add to your project's .mcp.json or global MCP config:

json
{  "mcpServers": {    "pageguard": {      "command": "npx",      "args": ["pageguard-mcp"]    }  }}

Cursor

Add to Cursor Settings > MCP Servers:

json
{  "mcpServers": {    "pageguard": {      "command": "npx",      "args": ["pageguard-mcp"]    }  }}

Windsurf

Add to your MCP configuration:

json
{  "mcpServers": {    "pageguard": {      "command": "npx",      "args": ["pageguard-mcp"]    }  }}

Environment variables

VariableRequiredDescription
PAGEGUARD_API_KEYNo (local scan) / Yes (URL scan, doc gen)API key from getpageguard.com
PAGEGUARD_API_URLNoOverride API base URL (default: https://www.getpageguard.com)

Tools

pageguard_scan_local

Scan a local project directory for privacy-relevant technologies.

Input:

  • path (optional) — Absolute path to project directory. Defaults to current working directory.

Output: ComplianceReport JSON with detected technologies, data types, cookies, and third-party processors.

pageguard_scan_url

Scan a live website URL for privacy compliance issues.

Input:

  • url (required) — Full URL to scan, e.g. https://example.com

Output: ComplianceReport JSON with risk score, detected technologies, and compliance gaps.

pageguard_generate_docs

Generate AI-written legal compliance documents for a scanned site.

Input:

  • scanId (required) — Scan ID from a prior pageguard_scan_url result
  • documentType (optional) — One of: single ($29), bundle ($49), addon_security ($19), addon_a11y ($19), addon_schema ($19), app_bundle ($39), submission_guide ($19). Defaults to bundle.

Output: Generated document content.

Pricing

Scanning is free. Document generation requires credits:

  • Privacy Docs ($29) — Privacy Policy + Terms of Service + Cookie Policy
  • Fix Everything ($49) — All docs + Security Guide + Accessibility Report + Schema Markup
  • App Bundle ($39) — Privacy docs + App Store Submission Guide
  • Add-ons ($19 each) — Security Guide, Accessibility Report, Schema Markup, Submission Guide
  • Bulk packs — 5 for $79, 15 for $149, 50 for $349

Get an API key at getpageguard.com/#pricing.

License

MIT

Source: README.md at commit 0561a5f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts