What are the risks of connecting to npm:pageguard-mcp?

References sensitive file paths / environment secrets. Overall trust grade C (74/100).

When was npm:pageguard-mcp last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

npm:pageguard-mcp

Item: npm:pageguard-mcp
Rating: 74
Author: wmcp.sh

https://www.npmjs.com/package/pageguard-mcp

74/100 · MCP Trust Grade · checked 1mo ago · MCP 1.0.1

Is the npm:pageguard-mcp MCP server safe to use?

Independent trust grade C (74/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:pageguard-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 3 tools · Developer Tools

pageguard_scan_local

Scan a local project directory for privacy-relevant technologies by checking package.json dependencies, config files, and .env files against known tra

pageguard_scan_url

Scan a live website URL for privacy compliance issues. Detects tracking technologies, cookies, third-party data collection, and compliance gaps by ana

pageguard_generate_docs

Generate AI-written legal compliance documents (privacy policy, terms of service, cookie policy, etc.) for a previously scanned site. Requires a scanI

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 3 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 1 source file

Maintenance / popularity20%92

published within 90 days
2 published versions

Tool hygiene15%95

✓ ships TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
10 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package pageguard-mcp@1.0.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:pageguard-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:pageguard-mcp grade C

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Apageguard-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C](https://wmcp.sh/mcp/grade/npm%3Apageguard-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Apageguard-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Apageguard-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Apageguard-mcp/badge.svg" alt="MCP Trust Grade C · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.