# Utilitly PDF (npm · @utilitly/mcp)

Merge, split, rotate, delete, reorder and duplicate PDF pages on your computer. Nothing is uploaded.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@utilitly/mcp`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-utilitly-mcp/utilitly-mcp.md), [page](https://verifymcp.io/servers/com-utilitly-mcp/utilitly-mcp)

## Channel facts

- Registry: `npm`
- Package: `@utilitly/mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 14 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add com-utilitly-mcp -- npx -y @utilitly/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-utilitly-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@utilitly/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-utilitly-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@utilitly/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-utilitly-mcp -- npx -y @utilitly/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-utilitly-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@utilitly/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-utilitly-mcp --command npx --arg -y --arg @utilitly/mcp
```

### Hermes

```yaml
mcp_servers:
  com-utilitly-mcp:
    command: "npx"
    args: ["-y", "@utilitly/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-utilitly-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@utilitly/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-utilitly-mcp -t stdio -c npx -a -y @utilitly/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-utilitly-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@utilitly/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, +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.

### 2026-11-02 (score 72, +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.

### 2026-10-31 (score 71, +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.

### 2026-10-29 (score 70)

First indexed and scored.

## MCP tools (8)

### `pdf_info` (~56 tokens)

PDF info

Reads a PDF and reports its page count, file size, first page size in points, and whether it is password-protected. Changes nothing.

Input parameters:

- `path` (string, required): Absolute path to a PDF file, or one starting with ~/.

Output parameters:

- `encrypted` (boolean)
- `file_size_bytes` (integer)
- `first_page`
- `pages`: Null when the file is encrypted in a way that hides its page list
- `path` (string)

### `merge_pdfs` (~116 tokens)

Merge PDFs

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.

Input parameters:

- `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, required): Absolute paths of the PDFs to combine, in order

Output parameters:

- `output_path` (string): Where the new PDF was written
- `pages` (integer): Pages in the new PDF

### `split_pdf` (~153 tokens)

Split a PDF

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.

Input parameters:

- `output_folder` (string): Optional absolute path of an existing folder for the files. By default they go next to the input.
- `path` (string, required): Absolute path to a PDF file, or one starting with ~/.
- `ranges` (string, required): Ranges such as "1-2, 3, 4-end": one output file per comma-separated part

Output parameters:

- `output_paths` (array): The new PDFs, one per range
- `pages` (array): Pages in each new PDF

### `extract_pages` (~142 tokens)

Extract pages

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.

Input parameters:

- `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, required): Pages, such as "2", "1-3, 5" or "4-end". Commas separate parts.
- `path` (string, required): Absolute path to a PDF file, or one starting with ~/.

Output parameters:

- `output_path` (string): Where the new PDF was written
- `pages` (integer): Pages in the new PDF

### `rotate_pdf` (~186 tokens)

Rotate pages

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.

Input parameters:

- `angle` (integer, required): 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, required): Absolute path to a PDF file, or one starting with ~/.

Output parameters:

- `output_path` (string): Where the new PDF was written
- `pages` (integer): Pages in the new PDF

### `delete_pages` (~150 tokens)

Delete pages

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.

Input parameters:

- `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, required): Pages to remove, such as "2", "1-3, 5" or "4-end". Commas separate parts.
- `path` (string, required): Absolute path to a PDF file, or one starting with ~/.

Output parameters:

- `output_path` (string): Where the new PDF was written
- `pages` (integer): Pages in the new PDF

### `reorder_pages` (~153 tokens)

Reorder pages

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.

Input parameters:

- `order` (array, required): 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, required): Absolute path to a PDF file, or one starting with ~/.

Output parameters:

- `output_path` (string): Where the new PDF was written
- `pages` (integer): Pages in the new PDF

### `duplicate_pages` (~218 tokens)

Duplicate pages

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.

Input parameters:

- `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, required): Pages to copy, such as "2", "1-3, 5" or "4-end". Commas separate parts.
- `path` (string, required): 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.

Output parameters:

- `output_path` (string): Where the new PDF was written
- `pages` (integer): Pages in the new PDF

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-utilitly-mcp/utilitly-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@utilitly/mcp
- Socket report: https://socket.dev/npm/package/@utilitly/mcp
- Repository: https://github.com/utilitlyPDF/utilitly-mcp
- Website: https://utilitly.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-utilitly-mcp/utilitly-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-utilitly-mcp/utilitly-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-utilitly-mcp/utilitly-mcp