pageguard-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAGEGUARD_API_KEY | No | API key from getpageguard.com. Required for URL scan and document generation tools; not required for local scanning. | |
| PAGEGUARD_API_URL | No | Override API base URL | https://www.getpageguard.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pageguard_scan_localA | Scan a local project directory for privacy-relevant technologies by checking package.json dependencies, config files, and .env files against known tracking/analytics signatures. No API key or network access needed. Returns a ComplianceReport with detected technologies, data types collected, cookies, and third-party processors. |
| pageguard_scan_urlA | Scan a live website URL for privacy compliance issues. Detects tracking technologies, cookies, third-party data collection, and compliance gaps by analyzing the actual deployed site. Returns a ComplianceReport with risk score, detected technologies, and compliance gaps. Optionally uses PAGEGUARD_API_KEY env var for authenticated requests. |
| pageguard_generate_docsA | Generate AI-written legal compliance documents (privacy policy, terms of service, cookie policy, etc.) for a previously scanned site. Requires a scanId from a prior URL scan and a PAGEGUARD_API_KEY with available credits. Document types: 'single' ($29 — privacy + terms + cookie), 'bundle' ($49 — everything), 'addon_security' ($19), 'addon_a11y' ($19), 'addon_schema' ($19), 'app_bundle' ($39), 'submission_guide' ($19). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools serve distinctly different purposes: scan_local analyzes codebase dependencies, scan_url analyzes live websites, and generate_docs produces legal documents from scan results. No functional overlap exists between them.
All tools follow a consistent pageguard_verb_noun snake_case pattern. The scanning tools use parallel naming (scan_local, scan_url) to distinguish targets, while generate_docs clearly indicates its document creation purpose.
Three tools is appropriate for this focused domain, covering the essential scan-local, scan-production, and generate-documentation workflow. While functional, the surface is minimal and could benefit from supporting tools like get_scan or list_documents.
The core workflow is covered: dual scanning capabilities and document generation. Minor gaps exist in document lifecycle management (no retrieval of previous scans or generated documents), but agents can work with immediate return values.