EU PII Redaction
PYPI · EU-PII-REDACT
Redact EU personal data (names, national IDs, IBANs) in text and files; restore it later.
Available components
Last scanned (16 hours ago)
Scores higher than 63% of PyPI 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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 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 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 389 tokens (~129/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 Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 18 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +21
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.40 ▲ functional
- 12 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Oct 26 69
First indexed and scored.
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 18 Oct 2026 · Analysed pypi/eu-pii-redact@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| No linked repository | 1 |
| 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_file ~135
Redact a text file into a new file without showing its contents. Returns only counts per type, so the personal data never enters the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| input_path | string | yes | UTF-8 text file to redact (.txt, .md, .csv, .json, .log, .eml...). |
| output_path | string | yes | Where to write the redacted copy. |
| overwrite | boolean | – | – |
| save_mapping | boolean | – | Also write <output_path>.map.json (owner-only permissions) so restore_file can put the original values back later. |
| types | – | – | Only these types; default all. |
No output schema declared.
No examples provided.
redact_text ~85
Redact personal data in a text and return the redacted text plus the detected entities (type, position, placeholder). Original values are not returned.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | "label" replaces with [TYPE_n] placeholders, "mask" with asterisks. |
| text | string | yes | Text to redact. |
| types | – | – | Only these types; default all. |
No output schema declared.
No examples provided.
restore_file ~102
Put the original values back into a file, locally (no API call). Returns only how many placeholders were restored, not the values.
| Name | Type | Req | Description |
|---|---|---|---|
| input_path | string | yes | File containing placeholders, e.g. an edited redacted file or an LLM answer saved to disk. |
| mapping_path | string | yes | The .map.json written by redact_file. |
| output_path | string | yes | Where to write the restored file. |
| overwrite | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the EU PII Redaction MCP server?
EU PII Redaction runs locally as a PyPI package, launched with uvx eu-pii-redact. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · eu-pii-redact
claude mcp add julianjohansen-eu-pii-redact -- uvx eu-pii-redact
What is the EU PII Redaction MCP server?
EU PII Redaction is an MCP server listed in the public MCP registry as io.github.JulianJohansen/eu-pii-redact. Redact EU personal data (names, national IDs, IBANs) in text and files; restore it later. This page covers its PyPI package (eu-pii-redact).
Is the EU PII Redaction MCP server safe to use?
EU PII Redaction scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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 EU PII Redaction MCP server expose?
EU PII Redaction exposes 3 tools: redact_text, redact_file, restore_file. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Is the EU PII Redaction MCP server still maintained?
EU PII Redaction is still listed as active in the MCP registry. We last reached this channel on 18 October 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 EU PII Redaction MCP server under?
EU PII Redaction declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.