io.github.nickjlamb/redacta-mcp
NPM · REDACTA-MCP · SCANNED SEP 27
Pseudonymise and restore patient identifiers & PII in text — local, HIPAA Safe Harbor mode.
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 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to nickjlamb/redacta). View diagnostics → Pass
- Clear OSI-approved license (MIT-0).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 828 tokens (~118/item across 7 items; 7 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 Management90
- Stability observed for 27 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 Safety75
- 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; "discard_session" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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 io.github.nickjlamb/redacta-mcp server?
io.github.nickjlamb/redacta-mcp runs locally as an npm package, launched with npx -y redacta-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 · redacta-mcp
claude mcp add nickjlamb-redacta-mcp -- npx -y redacta-mcp
{
"mcpServers": {
"nickjlamb-redacta-mcp": {
"command": "npx",
"args": [
"-y",
"redacta-mcp"
]
}
}
} {
"servers": {
"nickjlamb-redacta-mcp": {
"command": "npx",
"args": [
"-y",
"redacta-mcp"
]
}
}
} codex mcp add nickjlamb-redacta-mcp -- npx -y redacta-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nickjlamb-redacta-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"redacta-mcp"
],
"enabled": true
}
}
} openclaw mcp add nickjlamb-redacta-mcp --command npx --arg -y --arg redacta-mcp
mcp_servers:
nickjlamb-redacta-mcp:
command: "npx"
args: ["-y", "redacta-mcp"] {
"McpServers": {
"nickjlamb-redacta-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"redacta-mcp"
]
}
}
} assistant mcp add nickjlamb-redacta-mcp -t stdio -c npx -a -y redacta-mcp
{
"mcpServers": {
"nickjlamb-redacta-mcp": {
"command": "npx",
"args": [
"-y",
"redacta-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.
- 27 Sept 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 23 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.77 functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 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 27 Sept 2026 · Analysed npm/redacta-mcp@2.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | nickjlamb/redacta |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nickjlamb/redacta/.github/workflows/mcpb-pack.yaml@refs/heads/main |
| Rekor log index | 2389725837 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:72fb0cc7b7b22364c1a31c588b2b632fdacf90aec5e9bc744d61f0e24c9d4a11c64261dfecdd9b4c4669c00d1048901d95560e5754483f1b9ee43f3fc |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| 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 →
check_output Check output for leaked identifiers ~112
Scan generated text for verbatim reappearance of the original values held in a protected session (tolerant of spacing, dashes and case for identifier-like values) and re-tokenise anything found. Returns which token categories leaked — never the raw values — plus the sanitised text and a general self-check. Scope is verbatim reappearance only: paraphrases and inferred identities are not detected.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id returned by protect. |
| text | string | yes | Model output to inspect. |
No output schema declared.
No examples provided.
discard_session Discard a protection session ~49
Delete a session's private mapping immediately instead of waiting for expiry. Idempotent. After this, no restoration is possible for that session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id to discard. |
No output schema declared.
No examples provided.
protect Protect text (mapping stays server-side) ~213
Redact patient identifiers and PII, replacing each distinct value with a labelled token ([NHS_NUMBER_1], [PATIENT_NAME_1], ...). The reversal mapping is kept privately inside the Redacta server and is NEVER included in this response — you receive only the protected text, an opaque session_id for later controlled restoration, a count of what was replaced, and a self-check of possible leftovers. Sessions expire automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Which pattern sets to apply. Defaults to clinical + general. 'clinical' = NHS/NI/DOB/MRN/postcode/SSN/ZIP/email/phone/names; 'general' = URLs, IPs, payment cards, IBANs, account numbers, vehicle regs… |
| text | string | yes | The text to protect. |
No output schema declared.
No examples provided.
redact Redact / pseudonymise text (legacy — exposes token map) ~181
LEGACY: like protect, but returns the token_map (token -> original value) in the response, which places the reversal key in the client and potentially the model context. Kept for backward compatibility and client-managed workflows. Prefer protect, which keeps the mapping server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Which pattern sets to apply. Defaults to clinical + general. 'clinical' = NHS/NI/DOB/MRN/postcode/SSN/ZIP/email/phone/names; 'general' = URLs, IPs, payment cards, IBANs, account numbers, vehicle regs… |
| text | string | yes | The text to redact. |
No output schema declared.
No examples provided.
reinstate Re-identify from a client-held token map (legacy) ~104
LEGACY: reverse a redaction using a token map held by the client (from the legacy redact tool). Restored personal data will appear in this tool result. For session-based restoration that keeps mappings server-side, use protect + release_to_file.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Text containing Redacta tokens to restore. |
| token_map | object | yes | Token map, e.g. {"[NHS_NUMBER_1]": "943 476 5919"}. |
No output schema declared.
No examples provided.
release_to_file Restore identifiers into a local file ~104
Restore original identifiers into text produced from a protected session, writing the result to a file inside the server's configured release directory (REDACTA_RELEASE_DIR). Returns only a receipt — file path, size, and counts — so restored data never enters the model context. This is the privacy-preserving way to complete the round trip.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id returned by protect. |
| text | string | yes | Text containing Redacta tokens to restore. |
No output schema declared.
No examples provided.
self_check Self-check for residual identifiers ~65
Scan already-redacted text for anything that still looks like an identifier (long numbers, emails, postcodes, URLs). A second pair of eyes, not a guarantee. Returns a list of possible leftovers to review.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Redacted text to re-scan. |
No output schema declared.
No examples provided.
What is the io.github.nickjlamb/redacta-mcp server?
io.github.nickjlamb/redacta-mcp is listed in the public MCP registry as io.github.nickjlamb/redacta-mcp. Pseudonymise and restore patient identifiers & PII in text, local, HIPAA Safe Harbor mode. This page covers its npm package (redacta-mcp).
Is the io.github.nickjlamb/redacta-mcp server safe to use?
io.github.nickjlamb/redacta-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.nickjlamb/redacta-mcp server expose?
io.github.nickjlamb/redacta-mcp exposes 7 tools: protect, release_to_file, check_output, discard_session, redact, and 2 more. Their descriptions and schemas cost roughly 828 tokens of context every time the server is loaded.
Is the io.github.nickjlamb/redacta-mcp server still maintained?
io.github.nickjlamb/redacta-mcp is still listed as active in the MCP registry. We last reached this channel on 27 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 io.github.nickjlamb/redacta-mcp server under?
io.github.nickjlamb/redacta-mcp declares the MIT-0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.