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/bitterdev/pdf-letter-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/bitterdev/pdf-letter-mcp/pdf-letter-mcp)<a href="https://agentmods.dev/mcp/bitterdev/pdf-letter-mcp/pdf-letter-mcp"><img src="https://agentmods.dev/badge/mcp/bitterdev/pdf-letter-mcp/pdf-letter-mcp/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/bitterdev/pdf-letter-mcp/pdf-letter-mcp"><img src="https://agentmods.dev/badge/mcp/bitterdev/pdf-letter-mcp/pdf-letter-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pdf-letter-mcp 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 9d 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
{
"pdf-letter-mcp": {
"command": "npx",
"args": [
"-y",
"pdf-letter-mcp"
],
"env": {
"PDF_LETTER_OUTPUT_DIR": "",
"PDF_LETTER_FONT_DIR": ""
}
}
}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.
- 9d ago First seen · 13 lines scan A bd6a20e69060
pdf-letter-mcp is an MCP server published in the GitHub repository bitterdev/pdf-letter-mcp (0 stars, last pushed 1mo ago), 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-08-31.
Other mcp servers, from other repositories
pdf-mcp
MCP server "pdf-mcp" as configured in I-CAN-hack/pdf-mcp. Runs locally from the src/pdf_mcp/server.py Python package.
cvx
Create, validate, and render CV PDFs from plain YAML — fully local, no accounts. Runs locally from the @hrtips/cvx npm package.
zenith
Author, validate, edit, and render deterministic .zen design docs to PNG/PDF. Runs locally from the @zenitheditor/zenith-mcp npm package.
pdf-reader-mcp
MCP server for PDF structure analysis - read, inspect, and validate PDF internals. Runs locally from the @shuji-bonji/pdf-reader-mcp npm package.
pdf-spec-mcp
MCP server for structured understanding of ISO 32000 (PDF) specifications. A specification reference, not a conformance checker — it never inspects PDF files. Runs locally from the @shuji-bonji/pdf-spec-mcp npm package.
pdf-toolkit-mcp
Write-capable PDF toolkit MCP: 22 tools to read, create, render, encrypt, merge & fill PDFs. Runs locally from the @aryanbv/pdf-toolkit-mcp npm package.