PageGuard MCP
NPM · PAGEGUARD-MCP · SCANNED SEP 20
Privacy compliance scanning for AI coding tools. Detects tracking tech, cookies, and data gaps.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 166 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 355 tokens (~118/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the PageGuard MCP server?
PageGuard MCP runs locally as an npm package, launched with npx -y pageguard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pageguard-mcp
claude mcp add pageguard-pageguard-mcp -- npx -y pageguard-mcp
{
"mcpServers": {
"pageguard-pageguard-mcp": {
"command": "npx",
"args": [
"-y",
"pageguard-mcp"
]
}
}
} {
"servers": {
"pageguard-pageguard-mcp": {
"command": "npx",
"args": [
"-y",
"pageguard-mcp"
]
}
}
} codex mcp add pageguard-pageguard-mcp -- npx -y pageguard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pageguard-pageguard-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"pageguard-mcp"
],
"enabled": true
}
}
} openclaw mcp add pageguard-pageguard-mcp --command npx --arg -y --arg pageguard-mcp
mcp_servers:
pageguard-pageguard-mcp:
command: "npx"
args: ["-y", "pageguard-mcp"] {
"McpServers": {
"pageguard-pageguard-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pageguard-mcp"
]
}
}
} assistant mcp add pageguard-pageguard-mcp -t stdio -c npx -a -y pageguard-mcp
{
"mcpServers": {
"pageguard-pageguard-mcp": {
"command": "npx",
"args": [
"-y",
"pageguard-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/pageguard-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pageguard_generate_docs ~177
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).
| Name | Type | Req | Description |
|---|---|---|---|
| documentType | string | – | Product type to generate. One of: single, bundle, addon_security, addon_a11y, addon_schema, app_bundle, submission_guide. Defaults to 'bundle'. |
| scanId | string | yes | The scan ID from a previous pageguard_scan_url result |
No output schema declared.
No examples provided.
pageguard_scan_local ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Absolute path to the project directory. Defaults to the current working directory. |
No output schema declared.
No examples provided.
pageguard_scan_url ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The full URL to scan, e.g. https://example.com |
No output schema declared.
No examples provided.
What is the PageGuard MCP server?
PageGuard MCP is listed in the public MCP registry as io.github.pageguard/pageguard-mcp. Privacy compliance scanning for AI coding tools. Detects tracking tech, cookies, and data gaps. This page covers its npm package (pageguard-mcp).
Is the PageGuard MCP server safe to use?
PageGuard MCP scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PageGuard MCP server expose?
PageGuard MCP exposes 3 tools: pageguard_scan_local, pageguard_scan_url, pageguard_generate_docs. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Is the PageGuard MCP server still maintained?
PageGuard MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the PageGuard MCP server under?
PageGuard MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.