Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.thrain/blackout

NPM · @THRAIN/BLACKOUT-MCP · SCANNED SEP 22

Permanent local PDF redaction: text is removed and verified gone, not covered. No uploads.

Available components

npm · @thrain/blackout-mcp 83
0 this week 83 Trust /100
Trust breakdown (7 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 → 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
  • 34 of 113 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability70
  • 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 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

How do I install the ai.thrain/blackout MCP server?

ai.thrain/blackout runs locally as an npm package, launched with npx -y @thrain/blackout-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 · @thrain/blackout-mcp

# add to Claude Code
claude mcp add ai-thrain-blackout -- npx -y @thrain/blackout-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-thrain-blackout": {
      "command": "npx",
      "args": [
        "-y",
        "@thrain/blackout-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-thrain-blackout": {
      "command": "npx",
      "args": [
        "-y",
        "@thrain/blackout-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ai-thrain-blackout -- npx -y @thrain/blackout-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-thrain-blackout": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@thrain/blackout-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-thrain-blackout --command npx --arg -y --arg @thrain/blackout-mcp
# ~/.hermes/config.yaml
mcp_servers:
  ai-thrain-blackout:
    command: "npx"
    args: ["-y", "@thrain/blackout-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-thrain-blackout": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@thrain/blackout-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ai-thrain-blackout -t stdio -c npx -a -y @thrain/blackout-mcp
// mcp.json
{
  "mcpServers": {
    "ai-thrain-blackout": {
      "command": "npx",
      "args": [
        "-y",
        "@thrain/blackout-mcp"
      ]
    }
  }
}
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.

  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 Sept 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.

  • 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.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 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.

  • 13 Sept 26 0
    • Package version: 1.1.0 → 1.3.0 functional
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 22 Sept 2026 · Analysed npm/@thrain/blackout-mcp@1.3.0

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 →

Dependencies 113 packages
Packages resolved 113
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~547 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. 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 →

Tool Tokens
check_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.

NameTypeReqDescription
detectarray–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.
pathstringyesAbsolute path to a PDF file on this machine.
termsarray–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 ~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.

NameTypeReqDescription
detectarray–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.
licencestring–Deprecated alias for `license`.
licensestring–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_pathstring–Where to write the redacted copy. Defaults to <input>-redacted.pdf. Must not be the input file.
overwriteboolean–Allow writing over an existing output file. Defaults to false.
pathstringyesAbsolute path to a PDF file on this machine.
termsarray–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.

Common questions

What is the ai.thrain/blackout MCP server?

ai.thrain/blackout is an MCP server listed in the public MCP registry as ai.thrain/blackout. Permanent local PDF redaction: text is removed and verified gone, not covered. No uploads. This page covers its npm package (@thrain/blackout-mcp).

Is the ai.thrain/blackout MCP server safe to use?

ai.thrain/blackout scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 ai.thrain/blackout MCP server expose?

ai.thrain/blackout exposes 2 tools: check_pdf, redact_pdf. Their descriptions and schemas cost roughly 547 tokens of context every time the server is loaded.

Is the ai.thrain/blackout MCP server still maintained?

ai.thrain/blackout is still listed as active in the MCP registry. We last reached this channel on 22 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 ai.thrain/blackout MCP server under?

ai.thrain/blackout declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.