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/thrain-ai/blackout-pdfWrote 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/thrain-ai/blackout-pdf/blackout-mcp-blackout)<a href="https://agentmods.dev/mcp/thrain-ai/blackout-pdf/blackout-mcp-blackout"><img src="https://agentmods.dev/badge/mcp/thrain-ai/blackout-pdf/blackout-mcp-blackout/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/thrain-ai/blackout-pdf/blackout-mcp-blackout"><img src="https://agentmods.dev/badge/mcp/thrain-ai/blackout-pdf/blackout-mcp-blackout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
blackout 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 12d ago.
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
{
"blackout": {
"command": "npx",
"args": [
"-y",
"@thrain/blackout-mcp"
],
"env": {}
}
}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.
- 12d ago First seen · 10 lines scan A f22a12795eb9
blackout is an MCP server published in the GitHub repository thrain-ai/blackout-pdf (0 stars, last pushed 1mo ago), licensed Apache-2.0. 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-08-31.
Other mcp servers, from other repositories
heu-mcp
MCP Server for HEU Legal API - manage documents and PDFs for e-signature with Claude AI. Runs locally from the heu-mcp Python package. Needs 3 environment variables to run.
core
MCP server for ParseRail — gives Claude, Cursor, and any MCP client native tools to parse documents, extract fields, redact PII, analyze contracts, fight chargebacks, and enrich companies. Runs locally from the @kynth/api-mcp npm package. Needs 1 environment variable to run.
zapsign-mcp
ZapSign electronic document signing via the official API: create documents for signature (from PDF. Remote server at api.mcp.ai.
sign-cli
Agent-first e-signature MCP server with offline PAdES signing and hash-chained audit. Runs locally from the @drbaher/sign-cli npm package.
addsign-mcp
MCP server for AddSign — agents send documents for signature, track signing status, and download signed PDFs. Runs locally from the addsign-mcp npm package. Needs 1 environment variable to run.
zyta-sign-mcp
Servidor MCP para Zyta Sign — documentos, firmas y estudios desde Claude, Cursor o Codex. Runs locally from the zyta-sign-mcp npm package.