Redact MCP
NPM · @MATTZAM/REDACT-MCP
Auto-detects and obfuscates PII (IPs, emails, API keys, names) so Claude never sees real client data
Available components
Last scanned (20 hours ago)
Scores higher than 39% of npm servers
Category Security
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 Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.34.5, reached via @huggingface/transformers > sharp. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 52 of 167 dependencies flagged as unhealthy (1 deprecated). 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 225 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability29
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 882 tokens (~110/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety50
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "redact_remove_mapping" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- Manipulation check failed: an AI judge found 1 of 9 captured unit(s) of tool text manipulative, the first being "server instructions". See how to fix → Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- GHSA-wq5f-xc86-pv6w no longer affects this package ▲ security
- GHSA-rgj7-g3m4-5g8c no longer affects this package ▲ security
- GHSA-f88m-g3jw-g9cj no longer affects this package ▲ security
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/@mattzam/redact-mcp@2.0.4
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 →
Vulnerabilities 3 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 167 packages
| Packages resolved | 167 |
|---|---|
| Deprecated | 1 |
| Stale | 52 |
| 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 →
redact_add_mapping ~79
Manually add a specific real→fake mapping. Use this when you know a specific value should be redacted (e.g., a client company name, internal hostname).
| Name | Type | Req | Description |
|---|---|---|---|
| fake | string | yes | The fake replacement value |
| real | string | yes | The real/sensitive value to map |
| type | string | – | Category of the value |
No output schema declared.
No examples provided.
redact_audit_log ~55
View recent audit log entries showing what was redacted and when. Requires REDACT_AUDIT_LOG=true environment variable to be set.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of recent entries to return (default: 20) |
No output schema declared.
No examples provided.
redact_deobfuscate ~54
Reverses obfuscation — replaces all fake values back with the original real values. Use this when generating final reports or deliverables for the client.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Obfuscated text to restore |
No output schema declared.
No examples provided.
redact_obfuscate ~68
Takes raw text and returns an obfuscated version with all detected PII replaced by consistent fake values. Uses regex + AI-based NER detection. Use this to sanitize any pasted text, command output, or data before analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Raw text to obfuscate |
No output schema declared.
No examples provided.
redact_proxy_request ~158
Makes a real HTTP request to the target, then obfuscates the entire response before returning it. Use this INSTEAD of curl/fetch for all pentest HTTP requests. The URL, headers, and body are deobfuscated first (in case you're using already-obfuscated values), then the real request is made, and the response is fully sanitized.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Request body (for POST/PUT/PATCH) |
| followRedirects | boolean | – | Follow HTTP redirects |
| headers | object | – | Request headers as key-value pairs |
| method | string | – | HTTP method (GET, POST, PUT, DELETE, etc.) |
| url | string | yes | Target URL (can contain obfuscated or real values) |
No output schema declared.
No examples provided.
redact_read_file ~75
Reads a file from disk and returns its content with all detected PII obfuscated. Use this INSTEAD of the Read tool for any client data files, config files, or logs that may contain sensitive information.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | File encoding |
| path | string | yes | Absolute path to the file to read |
No output schema declared.
No examples provided.
redact_remove_mapping ~41
Remove a mapping by its real value. Use this to undo a false positive detection.
| Name | Type | Req | Description |
|---|---|---|---|
| real | string | yes | The real value whose mapping should be removed |
No output schema declared.
No examples provided.
redact_show_mappings ~30
Display all current real→fake mappings, grouped by type. Shows what is currently being redacted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Redact MCP server?
Redact MCP runs locally as an npm package, launched with npx -y @mattzam/redact-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 · @mattzam/redact-mcp
claude mcp add r3352-redact-mcp -- npx -y @mattzam/redact-mcp
What is the Redact MCP server?
Redact MCP is listed in the public MCP registry as io.github.r3352/redact-mcp. Auto-detects and obfuscates PII (IPs, emails, API keys, names) so Claude never sees real client data. This page covers its npm package (@mattzam/redact-mcp).
Is the Redact MCP server safe to use?
Redact MCP scores 70 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 4 November 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 Redact MCP server expose?
Redact MCP exposes 8 tools: redact_obfuscate, redact_deobfuscate, redact_proxy_request, redact_read_file, redact_add_mapping, and 3 more. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.
Is the Redact MCP server still maintained?
Redact MCP is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Redact MCP server under?
Redact 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.