Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

pdffr

NPM · PDFFR-MCP · SCANNED SEP 25

Local, private PDF to Markdown for agents: geometry-first parsing, OCR only where needed.

Available components

npm · pdffr-mcp 78
+3 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 37 of 123 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 481 tokens (~160/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the pdffr MCP server?

pdffr runs locally as an npm package, launched with npx -y pdffr-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · pdffr-mcp

# add to Claude Code
claude mcp add amersarhan-pdffr-mcp -- npx -y pdffr-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "amersarhan-pdffr-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pdffr-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "amersarhan-pdffr-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pdffr-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add amersarhan-pdffr-mcp -- npx -y pdffr-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "amersarhan-pdffr-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pdffr-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add amersarhan-pdffr-mcp --command npx --arg -y --arg pdffr-mcp
# ~/.hermes/config.yaml
mcp_servers:
  amersarhan-pdffr-mcp:
    command: "npx"
    args: ["-y", "pdffr-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "amersarhan-pdffr-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pdffr-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add amersarhan-pdffr-mcp -t stdio -c npx -a -y pdffr-mcp
// mcp.json
{
  "mcpServers": {
    "amersarhan-pdffr-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pdffr-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +4
    • Stability: unverified → 0.27 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/pdffr-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 123 packages
Packages resolved 123
Stale 37
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~481 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
pdf_outline ~137

List the headings of a PDF with their level and page number, so you can decide which pages to read with pdf_to_markdown.

NameTypeReqDescription
base64string–Raw PDF bytes, base64-encoded
langstring–Tesseract language(s) for OCR, e.g. 'eng', 'deu', 'eng+ara' (default 'eng')
ocrboolean–Escalate ink the text layer cannot explain to on-device OCR (default true)
pathstring–Path to a PDF on this machine
urlstring–URL of a PDF to fetch

No output schema declared.

No examples provided.

pdf_tables ~136

Extract every table in a PDF as JSON rows: [{ page, rows: string[][] }]. The first row is the header.

NameTypeReqDescription
base64string–Raw PDF bytes, base64-encoded
langstring–Tesseract language(s) for OCR, e.g. 'eng', 'deu', 'eng+ara' (default 'eng')
ocrboolean–Escalate ink the text layer cannot explain to on-device OCR (default true)
pathstring–Path to a PDF on this machine
urlstring–URL of a PDF to fetch

No output schema declared.

No examples provided.

pdf_to_markdown ~208

Decompile a PDF into Markdown (headings, lists, tables, math as LaTeX) locally. Born-digital pages take milliseconds; scans and screenshots get on-device OCR only where needed. Nothing is uploaded. Use pdf_outline first on long documents to pick pages.

NameTypeReqDescription
base64string–Raw PDF bytes, base64-encoded
langstring–Tesseract language(s) for OCR, e.g. 'eng', 'deu', 'eng+ara' (default 'eng')
maxCharsinteger–Truncate the Markdown to this many characters (default 200000)
ocrboolean–Escalate ink the text layer cannot explain to on-device OCR (default true)
pagesstring–Page selection like '1-3,7' (default all)
pathstring–Path to a PDF on this machine
urlstring–URL of a PDF to fetch

No output schema declared.

No examples provided.

Common questions

What is the pdffr MCP server?

pdffr is an MCP server listed in the public MCP registry as io.github.AmerSarhan/pdffr-mcp. Local, private PDF to Markdown for agents: geometry-first parsing, OCR only where needed. This page covers its npm package (pdffr-mcp).

Is the pdffr MCP server safe to use?

pdffr scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the pdffr MCP server expose?

pdffr exposes 3 tools: pdf_to_markdown, pdf_outline, pdf_tables. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.

Is the pdffr MCP server still maintained?

pdffr is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the pdffr MCP server under?

pdffr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.