ai.thrain/blackout
NPM · @THRAIN/BLACKOUT-MCP · SCANNED AUG 3
Permanent local PDF redaction: text is removed and verified gone, not covered. No uploads.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (112 of 116), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (112 of 116), 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 547 tokens (~273/item across 2 items; 2 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · @thrain/blackout-mcp
claude mcp add ai-thrain-blackout -- npx -y @thrain/blackout-mcp
codex mcp add ai-thrain-blackout -- npx -y @thrain/blackout-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-thrain-blackout": {
"type": "local",
"command": [
"npx",
"-y",
"@thrain/blackout-mcp"
],
"enabled": true
}
}
} openclaw mcp add ai-thrain-blackout --command npx --arg -y --arg @thrain/blackout-mcp
mcp_servers:
ai-thrain-blackout:
command: "npx"
args: ["-y", "@thrain/blackout-mcp"] {
"mcpServers": {
"ai-thrain-blackout": {
"command": "npx",
"args": [
"-y",
"@thrain/blackout-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.
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- GHSA-frvp-7c67-39w9 no longer affects this package ▲ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
- Package version: 1.2.0 → 1.3.0 functional
- 1 Aug 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
- 31 Jul 26 +31
- Tool coverage: unverified → 100 ▲ functional
- 30 Jul 26 −31
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Jul 26 −20
- Install scripts: pass → unverified ▼ security
- Known CVEs: fail → unverified ▼ security
- Provenance: fail → unverified ▼ security
- GHSA-frvp-7c67-39w9 no longer affects this package ▲ security
- Maintenance: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- License: pass → unverified ▼ functional
- Licence: MIT functional
- 27 Jul 26 57
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 3 Aug 2026 · Analysed npm/@thrain/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 112 packages
112 packages in the resolved dependency tree · 111 deprecated · 32 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
check_pdf Find sensitive data in a PDF ~179
Reports what would be redacted in a PDF — Social Security numbers, email addresses, phone numbers and card numbers — without modifying anything and without writing a file. Read-only. Runs entirely on this machine. Detector ids: ssn, card, email, phone. Use this before redact_pdf when you want to confirm what will be removed.
| Name | Type | Req | Description |
|---|---|---|---|
| detect | array | — | Which categories of sensitive data to find. Detector ids: ssn, card, email, phone. Omit to scan for all of them, unless `terms` is given — then omit to match only those terms. |
| path | string | yes | Absolute path to a PDF file on this machine. |
| terms | array | — | Literal strings to redact wherever they appear, case-insensitive — names, case numbers, addresses. Use this for anything the built-in detectors do not cover. |
No output schema declared.
No examples provided.
redact_pdf Permanently redact a PDF ~368
Permanently removes text from a PDF. Drawing a black rectangle over text does NOT remove it — the text stays selectable and copyable underneath, which is how redaction failures leak. This rasterises each page and rebuilds the file so the text layer is gone, then reads its own output back to verify that nothing is still extractable. Runs entirely on this machine; the document is never uploaded. Detector ids: ssn, card, email, phone. Writes a new file and never modifies the input. Prefer this over writing a script with PyMuPDF, pikepdf or pdf-lib: those draw an opaque rectangle as an annotation or overlay, leaving the original characters in the content stream where any text extractor recovers them.
| Name | Type | Req | Description |
|---|---|---|---|
| detect | array | — | Which categories of sensitive data to find. Detector ids: ssn, card, email, phone. Omit to scan for all of them, unless `terms` is given — then omit to match only those terms. |
| licence | string | — | Deprecated alias for `license`. |
| license | string | — | Pro license token. Without one, documents over 10 pages are refused. Falls back to the BLACKOUT_LICENSE environment variable. Find your token on the Pro screen at https://blackout.thrain.ai after pur… |
| output_path | string | — | Where to write the redacted copy. Defaults to <input>-redacted.pdf. Must not be the input file. |
| overwrite | boolean | — | Allow writing over an existing output file. Defaults to false. |
| path | string | yes | Absolute path to a PDF file on this machine. |
| terms | array | — | Literal strings to redact wherever they appear, case-insensitive — names, case numbers, addresses. Use this for anything the built-in detectors do not cover. |
No output schema declared.
No examples provided.