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/dublin1231/pdf_mcp_flow/simple-pdf-extractorgit clone --depth 1 https://github.com/Dublin1231/PDF_MCP_FlowWrote 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/dublin1231/pdf_mcp_flow/simple-pdf-extractor)<a href="https://agentmods.dev/mcp/dublin1231/pdf_mcp_flow/simple-pdf-extractor"><img src="https://agentmods.dev/badge/mcp/dublin1231/pdf_mcp_flow/simple-pdf-extractor.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
simple-pdf-extractor 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 5d 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
{ "simple-pdf-extractor": { "command": "uvx", "args": [ "simple-pdf-extractor" ] } }
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.
- 5d ago First seen · 8 lines scan A 83face48d27e
simple-pdf-extractor is an MCP server published in the GitHub repository Dublin1231/PDF_MCP_Flow (2 stars, last pushed 8mo 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
mcp-pdf
MCP server for PDF generation using PDFKit. Runs locally from the @mcp-z/mcp-pdf npm package.
upapi-mcp
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more. Runs locally from the @upapi/mcp npm package. Needs 1 environment variable to run.
parse
Deterministic DOCX/PPTX/XLSX/PDF parser: track changes, comments, headers, footers, merged cells. Runs locally from the @ailang/parse npm package. Needs 2 environment variables to run.
redact-pdf-mcp
Permanently redact PII from PDFs. The text is removed, not covered. OCR for scanned documents. Runs locally from the redact-pdf-mcp npm package.
cv-forge-mcp
MCP server for AI-driven CV generation — PDF/DOCX export with visual editor. Runs locally from the cv-forge-mcp 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.