io.github.moxno/privacyscrubber-mcp

NPM · @PRIVACYSCRUBBER/MCP-SERVER · SCANNED AUG 3

Zero-Trust PII & secrets sanitizer. Locally scrubs data in-memory before sending context to LLMs.

Available components

+32 this week 58 58 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security70

No malware found by supply-chain analysis.Pass
CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, a direct dependency. A fixed version is available. View diagnostics → Fail
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (38 of 39), so this covers what we could see, not the whole tree. 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 0 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability70

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 419 tokens (~139/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management23

Stability observed for 7 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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @privacyscrubber/mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add moxno-privacyscrubber-mcp -- npx -y @privacyscrubber/mcp-server

# add to Codex CLI

codex mcp add moxno-privacyscrubber-mcp -- npx -y @privacyscrubber/mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "moxno-privacyscrubber-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@privacyscrubber/mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add moxno-privacyscrubber-mcp --command npx --arg -y --arg @privacyscrubber/mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  moxno-privacyscrubber-mcp:
    command: "npx"
    args: ["-y", "@privacyscrubber/mcp-server"]

// mcp.json

{
  "mcpServers": {
    "moxno-privacyscrubber-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@privacyscrubber/mcp-server"
      ]
    }
  }
}

Changelog

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.

2 Aug 26 +20
- Known CVEs: unverified → fail ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
31 Jul 26 −16
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
29 Jul 26 +46
- CVE-2025-66414 affects this package: high ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Licence: MIT functional
28 Jul 26 0
- Security disclosure: fail → unverified ▼ functional
27 Jul 26 26

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/@privacyscrubber/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding

ID	CVE	Severity	Vector	Fix available
GHSA-w48q-cv73-mx4w	CVE-2025-66414	high		yes

Dependencies 38 packages

38 packages in the resolved dependency tree · 38 deprecated · 24 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 3 exposed · ~419 tokens

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.

Tool Tokens

reveal_text ~63

Replaces masked tokens (e.g., [EMAIL_1], [API_KEY_1]) in the LLM's response back with the original private data from the local volatile RAM-only session map.

Input Output Examples

Name	Type	Req	Description
text	string	yes	The AI generated response containing placeholders to restore.

Name	Type	Req	Description
text	string	yes	The detokenized text with original values restored.

No examples provided.

sanitize_file ~160

Reads a local file, sanitizes its contents using the selected profile, and outputs the safe version for AI analysis. Securely keeps original identifiers in memory.

Input Output Examples

Name	Type	Req	Description
file_path	string	yes	Absolute path to the file to sanitize.
profile	string	—	The detection profile to use. Available: 'General' (Free), or PRO profiles: 'Dev' (Engineering/Code), 'Medical', 'Pharma', 'Legal', 'Compliance', 'CCPA', 'Finance', 'Bizops', 'Sales', 'WealthMgmt', '…

Name	Type	Req	Description
text	string	yes	The sanitized content of the file.

No examples provided.

sanitize_text ~196

Locally scrubs PII, secrets, and credentials (like API keys, passwords, emails, phones, names) from code, logs, or text. Replaces them with safe placeholders (e.g., [EMAIL_1], [API_KEY_1]). Keep your data secure before passing it to any LLM.

Input Output Examples

Name	Type	Req	Description
profile	string	—	The detection profile to use. Available: 'General' (Free), or PRO profiles: 'Dev' (Engineering/Code), 'Medical', 'Pharma', 'Legal', 'Compliance', 'CCPA', 'Finance', 'Bizops', 'Sales', 'WealthMgmt', '…
text	string	yes	The raw text, code, or logs to sanitize.

Name	Type	Req	Description
text	string	yes	The sanitized text output.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug

Day	Score
27 Jul	26
28 Jul	26
29 Jul	72
30 Jul	54
31 Jul	38
1 Aug	38
2 Aug	58
3 Aug	58