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.

io.github.jztan/pdf-mcp

MCPB · PDF-MCP-3.6.0.MCPB · 2 COMPONENTS

Agentic RAG over one PDF or a whole folder: hybrid search, selective page reads, tables, OCR.

0 this week 54 Trust /100

Last scanned (10 hours ago)

Scores higher than 88% of MCPB servers

Category Documents and Files

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 887 tokens (~68/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 19 Oct 26 +1

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

  • 17 Oct 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.

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 5 Nov 2026 · Analysed mcpb/https://github.com/jztan/pdf-mcp/releases/download/v3.6.0/pdf-mcp-3.6.0.mcpb

Provenance No attestation

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

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 13 exposed · ~887 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_cache_clear ~64

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Clear expired or all cache entries.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_cache_stats ~64

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Cache size and per-document breakdown.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_corpus_overview ~69

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: One triage card per document in a folder.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_corpus_search ~72

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Search across every PDF in a folder, with document and page provenance.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_corpus_warm ~69

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Index a folder of PDFs within a time budget.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_extract_chart ~71

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Chart data as exact (x, y) tables from plot geometry.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_get_toc ~63

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Full table of contents.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_info ~70

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Page count, metadata, table of contents summary, scanned-page detection.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_read_all ~69

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Read a whole document in one call, size-capped.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_read_pages ~71

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Read specific pages, with OCR, tables, and images on demand.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_render_pages ~69

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Render pages as images for diagrams, handwriting, and scans.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdf_search ~69

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Hybrid keyword and semantic search inside one PDF, with paragraph excerpts.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

server_info ~67

UNAVAILABLE: pdf-mcp could not finish setting up. pdf-mcp could not download a component it needs to finish setting up. Check that this computer is connected to the internet, then quit and reopen Claude Desktop. (When working: Which optional features, settings, and updates are active.)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.jztan/pdf-mcp server?

io.github.jztan/pdf-mcp ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, c5f440c35e0ab33a5568f4f4a3339974832c66d9e3a1590c067bc79d11650ca9; the commands to do that are on this page. If it does not match, do not open it.

mcpb · pdf-mcp-3.6.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

c5f440c35e0ab33a5568f4f4a3339974832c66d9e3a1590c067bc79d11650ca9

macOS / Linux

echo "c5f440c35e0ab33a5568f4f4a3339974832c66d9e3a1590c067bc79d11650ca9  pdf-mcp-3.6.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\pdf-mcp-3.6.0.mcpb).Hash -eq "c5f440c35e0ab33a5568f4f4a3339974832c66d9e3a1590c067bc79d11650ca9"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the io.github.jztan/pdf-mcp server?

io.github.jztan/pdf-mcp is listed in the public MCP registry as io.github.jztan/pdf-mcp. Agentic RAG over one PDF or a whole folder: hybrid search, selective page reads, tables, OCR. This page covers its MCPB bundle (https://github.com/jztan/pdf-mcp/releases/download/v3.6.0/pdf-mcp-3.6.0.mcpb).

Is the io.github.jztan/pdf-mcp server safe to use?

io.github.jztan/pdf-mcp scores 54 out of 100 on VerifyMCP. 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 io.github.jztan/pdf-mcp server expose?

io.github.jztan/pdf-mcp exposes 13 tools: pdf_info, pdf_search, pdf_read_pages, pdf_read_all, pdf_get_toc, and 8 more. Their descriptions and schemas cost roughly 887 tokens of context every time the server is loaded.

What licence is the io.github.jztan/pdf-mcp server under?

io.github.jztan/pdf-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.