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/os-tack/fcpWrote 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/os-tack/fcp/pdf)<a href="https://agentmods.dev/mcp/os-tack/fcp/pdf"><img src="https://agentmods.dev/badge/mcp/os-tack/fcp/pdf/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/os-tack/fcp/pdf"><img src="https://agentmods.dev/badge/mcp/os-tack/fcp/pdf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pdf 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": {
"command": "uvx",
"args": [
"--refresh-package",
"fcp-pdf",
"--python",
"3.13",
"fcp-pdf"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 9. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 12 lines scan A 32ae35a630f3
pdf is an MCP server published in the GitHub repository os-tack/fcp (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
convert
File conversion: PDF, DOCX, STT, asynchronous TTS with MP3/ASS downloads, watermarking. Remote server at apick.app.
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.
mcp
Convert PDF, Word, Excel, PowerPoint, EPUB, HEIC & images — 35+ tools from convertica.net. Runs locally from the convertica-mcp npm package. Needs 1 environment variable to run.
pdf-reader-mcp
MCP server for extracting text, images, tables, links, annotations, and metadata from PDF files. Runs locally from the pdf-insight-mcp Python package.
vaultpdf-mcp
MCP server "vaultpdf-mcp" as configured in AlexeySamosadov/vaultpdf-mcp. Runs locally from the vaultpdf-mcp npm package.
bulkrender
Generate DOCX and PDF documents from AI assistants using BulkRender templates. Runs locally from the bulkrender-mcp npm package. Needs 1 environment variable to run.