pageguard_scan_localLABSCO SUMMARY
The local scan is free and answers most of the question.
The local scan reads your package.json, config and .env files and tells you which trackers and third-party processors you shipped, with no key, no network call and no cost. The URL scan and document generation are the paid half, and what comes out is a drafted document rather than legal advice.
What it is
A Node server over PageGuard's privacy compliance scanning: a local scan that reads your project files, a live scan of a deployed URL, and legal documents generated from what either one found.
What you get
- Tracking technologies, cookies and third-party data collection detected from
package.json, config files and.env— locally, with no network request and no key - A live site scanned for compliance issues, returning a risk score and a compliance gap analysis
- Legal documents generated from a scan ID — privacy policy, terms of service, cookie policy and others
- A ComplianceReport in JSON with the detected technologies, data types, cookies and third-party processors
Requirements
npx — npx pageguard-mcp in the client config. The local scan needs no key. PAGEGUARD_API_KEY is required for the URL scan and for document generation, and documents are priced per type, single or bundle, with each add-on at $19. PAGEGUARD_API_URL overrides the API base.
Setup effort
One command — npx pageguard-mcp
USE CASES
01
Finding out what your app is actually collecting
Scan the project locally and get back the technologies, data types, cookies and third-party processors it detected.
02
Checking a live site before somebody else does
Scan the deployed URL for a risk score and a compliance gap analysis.
03
Producing the policy pages a launch needs
Feed the scan ID into document generation and get a privacy policy, terms and cookie policy written against what was detected.
04
Catching a tracker a dependency dragged in
Rerun the local scan after a dependency change; it reads the manifest rather than the running site.
3 tools
Listed in project docs. Your client may show a different list.
pageguard_scan_urlpageguard_generate_docsBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
npx on PATH
Optional
PAGEGUARD_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx pageguard-mcpMCP Clients
Claude Code, Cursor, Windsurf
JSON
{
"mcpServers": {
"pageguard": {
"command": "npx",
"args": [
"pageguard-mcp"
]
}
}
}Local scans need no key. For URL scans and document generation, set PAGEGUARD_API_KEY in the server's environment (for example an env entry beside args), using a key from getpageguard.com/#pricing.
