Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/dambuchs/redact-pdf-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/dambuchs/redact-pdf-mcp/redact-pdf)<a href="https://agentmods.dev/mcp/dambuchs/redact-pdf-mcp/redact-pdf"><img src="https://agentmods.dev/badge/mcp/dambuchs/redact-pdf-mcp/redact-pdf/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/dambuchs/redact-pdf-mcp/redact-pdf"><img src="https://agentmods.dev/badge/mcp/dambuchs/redact-pdf-mcp/redact-pdf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
redact-pdf scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"redact-pdf": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 9 lines scan A bee3ed7236be
redact-pdf is an MCP server published in the GitHub repository dambuchs/redact-pdf-mcp (1 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-19.
Other mcp servers, from other repositories
zenith
Author, validate, edit, and render deterministic .zen design docs to PNG/PDF. Runs locally from the @zenitheditor/zenith-mcp npm package.
docgen-mcp-server
Render HTML/markdown to PDF, export rows to xlsx, and fill AcroForm PDFs. Runs locally from the @cyanheads/docgen-mcp-server npm package. Needs 6 environment variables to run.
pdf-suite-mcp
37 tools to read, create, merge, split, watermark, fill, redact & search PDFs. Local, no API key. Runs locally from the pdf-suite-mcp npm package.
pdf-toolkit-mcp
Legacy PDF Toolkit identity, pinned to its 2.1.1 package; maintained successor: PDF Suite MCP. Runs locally from the pdf-suite-mcp npm package.
cvx
Create, validate, and render CV PDFs from plain YAML — fully local, no accounts. Runs locally from the @hrtips/cvx npm package.
reportflow-mcp
Generate PDF reports from Re:port Flow templates via Claude and other AI agents. Runs locally from the reportflow-mcp npm package. Needs 4 environment variables to run.