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/jztan/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/jztan/pdf-mcp/pdf-mcp)<a href="https://agentmods.dev/mcp/jztan/pdf-mcp/pdf-mcp"><img src="https://agentmods.dev/badge/mcp/jztan/pdf-mcp/pdf-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/jztan/pdf-mcp/pdf-mcp"><img src="https://agentmods.dev/badge/mcp/jztan/pdf-mcp/pdf-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
pdf-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-mcp": {
"command": "uvx",
"args": [
"pdf-mcp"
],
"env": {
"PDF_MCP_CACHE_DIR": "",
"PDF_MCP_CACHE_TTL": ""
}
}
}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 · 12 lines scan A 69a5b274d188
pdf-mcp is an MCP server published in the GitHub repository jztan/pdf-mcp (133 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
nutrient-dws-mcp-server
Nutrient Processor + Data Extraction MCP: convert, OCR, sign, redact, and extract PDFs/Office docs. Runs locally from the @nutrient-sdk/dws-mcp-server npm package. Needs 5 environment variables to run.
pdf-rag-mcp
MCP server "pdf-rag-mcp" as configured in MBaranekTech/pdf-rag-mcp. Runs locally from the pdf-rag-mcp Python package.
pdfmux
Self-healing PDF extraction for RAG — #2 of 8 engines on opendataloader-bench (0.903). Flags pages it can't read instead of dropping them, and certifies any extractor's output for silent drops. Verify signed manifests offline, free. Per-page confidence, 7-tool MCP server, LangChain/LlamaIndex loaders. LlamaParse…
paper-intelligence
MCP server enabling AI agents to efficiently search and understand PDF documents. Runs locally from the paper-intelligence Python package.
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.