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/mrslbt/pdf-itWrote 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/mrslbt/pdf-it/pdf-it)<a href="https://agentmods.dev/mcp/mrslbt/pdf-it/pdf-it"><img src="https://agentmods.dev/badge/mcp/mrslbt/pdf-it/pdf-it/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/mrslbt/pdf-it/pdf-it"><img src="https://agentmods.dev/badge/mcp/mrslbt/pdf-it/pdf-it.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pdf-it 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 1mo 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-it": {
"command": "npx",
"args": [
"-y",
"pdf-it-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.
- 1mo ago First seen · 10 lines scan A 0c0a6bbbc313
pdf-it is an MCP server published in the GitHub repository mrslbt/pdf-it (2 stars, last pushed 3mo 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
zoteus
MCP server that gives Claude, ChatGPT and other MCP clients access to a Zotero library: search, citations, adding items, safe writes, semantic search, PDF passages and page images. Runs locally from the @oscardvs/zoteus npm package. Needs 1 environment variable to run.
calibre-mcp
Calibre ebook library server: search, read content, curate metadata, semantic search, gated writes. Runs locally from the calibre-mcp npm package. Needs 4 environment variables to run.
laserfiche-mcp
Model Context Protocol (MCP) server for self-hosted Laserfiche repositories — search and read documents from Claude. Runs locally from the laserfiche-mcp Python package. Needs 6 environment variables to run.
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.
sheetrender-mcp
Render PDFs from templates and spreadsheet data via SheetRender, locally or at mcp.sheetrender.com. Runs locally from the @sheetrender/mcp npm package. Needs 2 environment variables to run.
truepath-pdf-mcp
Local-only PDF tools for AI — extract text, search, split/merge, render pages. Files never leave. Runs locally from the @truepathpdf/mcp-server npm package.