Utilitly PDF
NPM · @UTILITLY/MCP
Merge, split, rotate, delete, reorder and duplicate PDF pages on your computer. Nothing is uploaded.
Available components
Last scanned (4 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 Security99
- 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
- 3 of 14 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 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1174 tokens (~146/item across 8 items; 8 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 Management23
- Stability observed for 7 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 70
First indexed and scored.
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/@utilitly/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 14 packages
| Packages resolved | 14 |
|---|---|
| Stale | 3 |
| 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 →
delete_pages Delete pages ~150
Removes the selected pages and keeps the rest in order, named with -trimmed. At least one page must remain. Writes the result as a new file next to the input (or to output_path) and never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Optional absolute path for the new PDF, ending in .pdf. It must not exist yet. By default the result goes next to the input. |
| pages | string | yes | Pages to remove, such as "2", "1-3, 5" or "4-end". Commas separate parts. |
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Where the new PDF was written |
| pages | integer | yes | Pages in the new PDF |
No examples provided.
duplicate_pages Duplicate pages ~218
Adds copies of the selected pages, right after each one or all at the end, named with -duplicated. Copies share the page's images, so the file barely grows. One call can add at most 10,000 pages. Writes the result as a new file next to the input (or to output_path) and never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| copies | integer | – | Extra copies of each page. Default 1. |
| output_path | string | – | Optional absolute path for the new PDF, ending in .pdf. It must not exist yet. By default the result goes next to the input. |
| pages | string | yes | Pages to copy, such as "2", "1-3, 5" or "4-end". Commas separate parts. |
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| placement | string | – | "after" (default) puts copies right after each page; "end" adds them at the end. |
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Where the new PDF was written |
| pages | integer | yes | Pages in the new PDF |
No examples provided.
extract_pages Extract pages ~142
Copies the selected pages into one new PDF, in page order, named with -pages. Writes the result as a new file next to the input (or to output_path) and never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Optional absolute path for the new PDF, ending in .pdf. It must not exist yet. By default the result goes next to the input. |
| pages | string | yes | Pages, such as "2", "1-3, 5" or "4-end". Commas separate parts. |
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Where the new PDF was written |
| pages | integer | yes | Pages in the new PDF |
No examples provided.
merge_pdfs Merge PDFs ~116
Combines PDFs into one, in the order given. The result is named after the first file, with -merged. Writes the result as a new file next to the input (or to output_path) and never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | – | Optional absolute path for the new PDF, ending in .pdf. It must not exist yet. By default the result goes next to the input. |
| paths | array | yes | Absolute paths of the PDFs to combine, in order |
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Where the new PDF was written |
| pages | integer | yes | Pages in the new PDF |
No examples provided.
pdf_info PDF info ~56
Reads a PDF and reports its page count, file size, first page size in points, and whether it is password-protected. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| Name | Type | Req | Description |
|---|---|---|---|
| encrypted | boolean | yes | – |
| file_size_bytes | integer | yes | – |
| first_page | – | yes | – |
| pages | – | yes | Null when the file is encrypted in a way that hides its page list |
| path | string | yes | – |
No examples provided.
reorder_pages Reorder pages ~153
Puts the pages in a new order, named with -reordered. The order must list every page exactly once; use pdf_info for the page count. Writes the result as a new file next to the input (or to output_path) and never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| order | array | yes | Every page number once, in the new order, e.g. [3, 1, 2] |
| output_path | string | – | Optional absolute path for the new PDF, ending in .pdf. It must not exist yet. By default the result goes next to the input. |
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Where the new PDF was written |
| pages | integer | yes | Pages in the new PDF |
No examples provided.
rotate_pdf Rotate pages ~186
Turns pages clockwise by a multiple of 90 degrees (negative turns counter-clockwise), every page unless pages is given. Named with -rotated. Writes the result as a new file next to the input (or to output_path) and never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | integer | yes | Degrees clockwise: 90, 180, 270, or -90 for counter-clockwise |
| output_path | string | – | Optional absolute path for the new PDF, ending in .pdf. It must not exist yet. By default the result goes next to the input. |
| pages | string | – | Pages, such as "2", "1-3, 5" or "4-end". Commas separate parts. Every page when left out. |
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| Name | Type | Req | Description |
|---|---|---|---|
| output_path | string | yes | Where the new PDF was written |
| pages | integer | yes | Pages in the new PDF |
No examples provided.
split_pdf Split a PDF ~153
Splits a PDF into one new file per comma-separated range, named -part1, -part2 and so on. "1-2, 3-end" gives two files, and one call writes at most 1,000 (or one per page for longer PDFs). Never replaces an existing file; the input is left unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| output_folder | string | – | Optional absolute path of an existing folder for the files. By default they go next to the input. |
| path | string | yes | Absolute path to a PDF file, or one starting with ~/. |
| ranges | string | yes | Ranges such as "1-2, 3, 4-end": one output file per comma-separated part |
| Name | Type | Req | Description |
|---|---|---|---|
| output_paths | array | yes | The new PDFs, one per range |
| pages | array | yes | Pages in each new PDF |
No examples provided.
How do I install the Utilitly PDF MCP server?
Utilitly PDF runs locally as an npm package, launched with npx -y @utilitly/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 · @utilitly/mcp
claude mcp add com-utilitly-mcp -- npx -y @utilitly/mcp
What is the Utilitly PDF MCP server?
Utilitly PDF is an MCP server listed in the public MCP registry as com.utilitly/mcp. Merge, split, rotate, delete, reorder and duplicate PDF pages on your computer. Nothing is uploaded. This page covers its npm package (@utilitly/mcp).
Is the Utilitly PDF MCP server safe to use?
Utilitly PDF scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting 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 Utilitly PDF MCP server expose?
Utilitly PDF exposes 8 tools: pdf_info, merge_pdfs, split_pdf, extract_pages, rotate_pdf, and 3 more. Their descriptions and schemas cost roughly 1,174 tokens of context every time the server is loaded.
Is the Utilitly PDF MCP server still maintained?
Utilitly PDF 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 Utilitly PDF MCP server under?
Utilitly PDF declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.