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.

PDF Triage

NPM · PDF-TRIAGE-MCP · SCANNED SEP 22

Read local PDFs without uploading. Classifies first, flags untrustworthy text, bounds output.

Available components

npm · pdf-triage-mcp 84
0 this week 84 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
  • 31 of 104 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 613 tokens (~153/item across 4 items; 4 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 Management97
  • Stability observed for 29 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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 PDF Triage MCP server?

PDF Triage runs locally as an npm package, launched with npx -y pdf-triage-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 · pdf-triage-mcp

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

  • 22 Sept 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.

  • 20 Sept 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.

  • 18 Sept 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 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.

  • 13 Sept 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.

  • 11 Sept 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.

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 22 Sept 2026 · Analysed npm/pdf-triage-mcp@0.1.2

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 104 packages
Packages resolved 104
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~613 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_classify ~135

Triage a local PDF without extracting its text (typically 10-50ms). Returns whether the document is text-based, scanned, image-based or mixed, a confidence score, and the exact 1-indexed pages that need OCR. ALWAYS call this before pdf_extract on an unfamiliar or large document: it is cheap, and it tells you whether local extraction is worth attempting at all. If it reports scanned, image_based, or encoding issues, do not extract — route the document to an OCR service instead.

NameTypeReqDescription
pathstringyesAbsolute path, or path relative to an allowed root, of a .pdf file

No output schema declared.

No examples provided.

pdf_extract ~190

Extract a local PDF to Markdown, preserving headings, lists and tables. Output is TRUNCATED by default to protect your context window — to read a long document, call repeatedly with the `pages` parameter rather than raising `maxChars`. Call pdf_classify first on unfamiliar documents. If the response carries a critical warning (encoding issues, no text layer, right-to-left script), the text is unreliable and must not be quoted as fact.

NameTypeReqDescription
compactboolean–Collapse dot leaders and source padding for token efficiency. Defaults to true.
maxCharsinteger–Truncation ceiling. Defaults to the server setting (40000).
pagesarray–1-indexed page numbers to extract. Omit for the whole document. Prefer this over raising maxChars.
pathstringyesAbsolute path, or path relative to an allowed root, of a .pdf file

No output schema declared.

No examples provided.

pdf_search ~155

Find text inside a local PDF and return matching pages with surrounding context. Much cheaper than pdf_extract when you only need to locate something — use this first on long documents, then pdf_extract with the `pages` it reports.

NameTypeReqDescription
contextCharsinteger–Characters of surrounding context per match. Defaults to 200.
maxMatchesinteger–Maximum matches to return. Defaults to 25.
pathstringyesAbsolute path, or path relative to an allowed root, of a .pdf file
querystringyesLiteral text to find, or a regular expression when `regex` is true
regexboolean–Treat `query` as a JavaScript regular expression. Defaults to false.

No output schema declared.

No examples provided.

pdf_tables ~133

Return only the tables from a local PDF as Markdown, skipping prose. Useful for invoices, financial statements and reports where the numbers are the point. Tables are detected from the PDF's own drawing operations and text alignment — the cell values are read directly from the document, not guessed by a model or OCR.

NameTypeReqDescription
maxCharsinteger–Truncation ceiling. Defaults to the server setting.
pagesarray–1-indexed pages to search for tables. Omit for the whole document.
pathstringyesAbsolute path, or path relative to an allowed root, of a .pdf file

No output schema declared.

No examples provided.

Common questions

What is the PDF Triage MCP server?

PDF Triage is an MCP server listed in the public MCP registry as io.github.vishalmeena2211/pdf-triage-mcp. Read local PDFs without uploading. Classifies first, flags untrustworthy text, bounds output. This page covers its npm package (pdf-triage-mcp).

Is the PDF Triage MCP server safe to use?

PDF Triage scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 PDF Triage MCP server expose?

PDF Triage exposes 4 tools: pdf_classify, pdf_extract, pdf_search, pdf_tables. Their descriptions and schemas cost roughly 613 tokens of context every time the server is loaded.

Is the PDF Triage MCP server still maintained?

PDF Triage is still listed as active in the MCP registry. We last reached this channel on 22 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 PDF Triage MCP server under?

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