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.

io.github.CloudCorpRecords/redactpdf

NPM · @RENETURCIOS/REDACTPDF · 2 COMPONENTS

Permanently redact SSNs, cards, emails, phones and custom terms from local PDFs, verified gone.

70 Trust /100

Last scanned (22 hours ago)

Scores higher than 38% of npm servers

Category Documents and Files

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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 218 tokens (~109/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 55

    First indexed and scored.

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 4 Nov 2026 · Analysed npm/@reneturcios/redactpdf@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 npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~218 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 ~80

Report what would be redacted from a local PDF — per-category match counts — without writing anything.

NameTypeReqDescription
detectarray–Any of ssn, card, email, phone. Omit for all
pathstringyesAbsolute path to a PDF on this machine
termsarray–Literal strings to match, case-insensitive

No output schema declared.

No examples provided.

redact_pdf ~138

Write a redacted copy of a local PDF with detected sensitive text permanently removed and verified gone. Never modifies the input.

NameTypeReqDescription
detectarray–Any of ssn, card, email, phone. Omit for all
licensestring–Pro licence token; falls back to BLACKOUT_LICENSE
output_pathstring–Defaults to <input>-redacted.pdf; must not be the input
overwriteboolean–Allow replacing an existing output. Default false
pathstringyesAbsolute path to a PDF on this machine
termsarray–Literal strings to match, case-insensitive

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/redactpdf MCP server?

io.github.CloudCorpRecords/redactpdf runs locally as an npm package, launched with npx -y @reneturcios/redactpdf. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/redactpdf

# add to Claude Code
claude mcp add cloudcorprecords-redactpdf -- npx -y @reneturcios/redactpdf
Common questions

What is the io.github.CloudCorpRecords/redactpdf MCP server?

io.github.CloudCorpRecords/redactpdf is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/redactpdf. Permanently redact SSNs, cards, emails, phones and custom terms from local PDFs, verified gone. This page covers its npm package (@reneturcios/redactpdf).

Is the io.github.CloudCorpRecords/redactpdf MCP server safe to use?

io.github.CloudCorpRecords/redactpdf scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting 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 io.github.CloudCorpRecords/redactpdf MCP server expose?

io.github.CloudCorpRecords/redactpdf exposes 2 tools: check_pdf, redact_pdf. Their descriptions and schemas cost roughly 218 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/redactpdf MCP server still maintained?

io.github.CloudCorpRecords/redactpdf 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 io.github.CloudCorpRecords/redactpdf MCP server under?

io.github.CloudCorpRecords/redactpdf declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.