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.
npx agentmods add mcp/bzsanti/oxidize-python/oxidize-pdf-mcpgit clone --depth 1 https://github.com/bzsanti/oxidize-pythonWrote 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/bzsanti/oxidize-python/oxidize-pdf-mcp)<a href="https://agentmods.dev/mcp/bzsanti/oxidize-python/oxidize-pdf-mcp"><img src="https://agentmods.dev/badge/mcp/bzsanti/oxidize-python/oxidize-pdf-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
oxidize-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 4d 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
{ "oxidize-pdf-mcp": { "command": "uvx", "args": [ "oxidize-pdf" ], "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.
- 4d ago First seen · 9 lines scan A d805f10cba9a
oxidize-pdf-mcp is an MCP server published in the GitHub repository bzsanti/oxidize-python (4 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-08-31.
Other mcp servers, from other repositories
pdfnative-mcp
PDF MCP server: generate PDF/A, sign & verify PAdES (LTV), forms, merge, split, encrypt. 28 tools. Runs locally from the pdfnative-mcp npm package. Needs 10 environment variables to run.
docuqueue
MCP server "docuqueue", hosted remotely at docuqueue.com, as configured in docuqueue/docuqueue-mcp.
docuqueue-mcp
Generate PDFs from templates via AI chat. Works with Claude, ChatGPT, Cursor, and any MCP client. Remote server at docuqueue.com.
pdf-mcp
Surgical PDF access for AI agents: keyword, semantic & hybrid search; structured extraction of text, tables, images & TOC; OCR; and CJK/vertical-script support — with SQLite caching. Runs locally from the pdf-mcp Python package. Needs 2 environment variables to run.
paper-intelligence
MCP server enabling AI agents to efficiently search and understand PDF documents. Runs locally from the paper-intelligence Python package.
tooldash-mcp
Offline PDF and text tools: merge, extract pages, inspect, clean text. No upload, no API key. Runs locally from the tooldash-mcp npm package. Needs 1 environment variable to run.