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.
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.
- 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
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.
One command plus a key — npx pageguard-mcp, then supply credentials