Papyrio PDF Tools
NPM · PAPYRIO-MCP
Compress, convert, merge, split and OCR PDFs from an assistant, using local files.
Available components
Last scanned (9 hours ago)
Scores higher than 45% of npm servers
Category Documents and Files
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2149 tokens (~179/item across 12 items; 12 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_pdfs" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
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.
- 4 Nov 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.
- 2 Nov 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.
- 31 Oct 26 +1
- Package version: 0.1.3 → 0.1.4 functional
- 28 Oct 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.
- 26 Oct 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.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.27 ▲ functional
- Package version: 0.1.3 → 0.1.4 functional
- 14 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
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 npm/papyrio-mcp@0.1.4
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compress_pdf ~194
Shrink a PDF by downsampling its images. Image-heavy files lose 30-80% of their size; text stays selectable. Use this when a PDF is too large to email or upload. Already-optimized files come back unchanged rather than larger. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the PDF to compress. |
| level | string | – | Compression strength. low keeps images at 300 DPI, medium at 150, high at 72. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
No output schema declared.
No examples provided.
extract_pdf_text ~160
Return the text of a PDF as UTF-8, so it can be read or summarized. Fast and exact when the PDF already has a text layer. A scanned PDF has none — run ocr_pdf on it first. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the PDF. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.txt" suffix. |
No output schema declared.
No examples provided.
image_to_pdf ~144
Wrap a JPG, PNG or WebP image in a PDF page. Use this when an image needs to be submitted or printed as a PDF. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the image. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
No output schema declared.
No examples provided.
merge_pdfs ~162
Combine 2 to 10 PDFs into one document, in the order given. Use this to join separate scans, chapters or invoices into a single file. Password-protected files must be unlocked first. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Absolute paths to the PDFs, in the order they should appear. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
No output schema declared.
No examples provided.
ocr_pdf ~307
Add an invisible text layer to a scanned PDF so its text can be searched, selected and extracted. Use this before extract_pdf_text or pdf_to_word on a scan or photographed document, and set lang when the text is not English. The page images are kept, so the output is about the same size as the input, and pages that already have text are left untouched. Takes roughly 2-10 seconds per page. Scans at 300 DPI or higher read well; below 150 DPI accuracy degrades badly. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the scanned PDF. |
| lang | string | – | Language of the document's text as a Tesseract code: eng (English), rus (Russian), spa (Spanish), ita (Italian), uzb (Uzbek, Latin script), uzb_cyrl (Uzbek, Cyrillic) or kaz (Kazakh). For mixed docum… |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
No output schema declared.
No examples provided.
office_to_pdf ~254
Convert a Word (.doc, .docx, .odt), PowerPoint (.ppt, .pptx) or Excel (.xls, .xlsx) document to PDF with LibreOffice, keeping fonts, tables, images and page layout; each slide or sheet becomes one or more pages. Use this to turn an Office file into a fixed, shareable PDF, not for files that are already PDFs. Large presentations can take 30 seconds or more. Password-protected Office files are not supported. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the Office document. The extension decides how it is read, so it must be one of .doc, .docx, .odt, .ppt, .pptx, .xls or .xlsx. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
No output schema declared.
No examples provided.
pdf_to_jpg ~154
Render every page of a PDF as a JPG image, returned as a ZIP archive. Use this when the pages are needed as pictures, for a thumbnail, a slide or an image pipeline. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the PDF. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.zip" suffix. |
No output schema declared.
No examples provided.
pdf_to_word ~158
Convert a PDF into an editable Word document. PDFs exported from Word, Google Docs or InDesign come through well. A scanned PDF is a picture of a page, so run ocr_pdf on it first. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the PDF. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.docx" suffix. |
No output schema declared.
No examples provided.
protect_pdf ~160
Encrypt a PDF with AES-256 so it cannot be opened without the password. Use this before sending a document that contains anything private. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the PDF to encrypt. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
| password | string | yes | Password that will be required to open the resulting PDF. |
No output schema declared.
No examples provided.
split_pdf ~145
Separate every page of a PDF into its own file, returned as a ZIP archive. Use this to pull single pages out of a long document. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the PDF to split. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.zip" suffix. |
No output schema declared.
No examples provided.
unlock_pdf ~158
Remove the password from a PDF you already know the password for. This decrypts with the supplied password; it does not break or guess encryption. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Absolute path to the password-protected PDF. |
| output_path | string | – | Absolute path to write the result to. Defaults to the input file with a "-papyrio.pdf" suffix. |
| password | string | yes | The PDF's current password. |
No output schema declared.
No examples provided.
webpage_to_pdf ~153
Fetch a public URL and render the page to PDF in a headless browser. Use this to archive or print a web page. This tool takes a URL rather than a file, so output_path is required. The input is uploaded to the Papyrio API, processed in memory and not stored. The result is written to output_path, replacing any file already there, and the call returns that path and the size in bytes. Inputs are limited to 50 MB, and each call counts as one operation against the daily quota.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Absolute path to write the .pdf result to. Required for this tool. |
| url | string | yes | Publicly reachable page URL, including https://. |
No output schema declared.
No examples provided.
How do I install the Papyrio PDF Tools MCP server?
Papyrio PDF Tools runs locally as an npm package, launched with npx -y papyrio-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 · papyrio-mcp
claude mcp add atabekdemurtaza-papyrio-mcp -- npx -y papyrio-mcp
What is the Papyrio PDF Tools MCP server?
Papyrio PDF Tools is an MCP server listed in the public MCP registry as io.github.atabekdemurtaza/papyrio-mcp. Compress, convert, merge, split and OCR PDFs from an assistant, using local files. This page covers its npm package (papyrio-mcp).
Is the Papyrio PDF Tools MCP server safe to use?
Papyrio PDF Tools scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 Papyrio PDF Tools MCP server expose?
Papyrio PDF Tools exposes 12 tools: compress_pdf, merge_pdfs, extract_pdf_text, ocr_pdf, pdf_to_word, and 7 more. Their descriptions and schemas cost roughly 2,149 tokens of context every time the server is loaded.
Is the Papyrio PDF Tools MCP server still maintained?
Papyrio PDF Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Papyrio PDF Tools MCP server under?
Papyrio PDF Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.