# Zovo PDF Merge (remote · pdf-merge.zovo.one)

Merge PDF files into one document right in the chat.

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

## Components

- remote · `pdf-merge.zovo.one`: 78/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge.md), [page](https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge)

## Channel facts

- Endpoint: `https://pdf-merge.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 760 tokens (~190/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_pdfs" implies "merge" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 5 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).
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo PDF Merge MCP server?

Zovo PDF Merge is a hosted endpoint at https://pdf-merge.zovo.one/mcp, so there is nothing to install locally. 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 --transport http theluckystrike-pdf-merge 'https://pdf-merge.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-pdf-merge": {
      "url": "https://pdf-merge.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-pdf-merge": {
      "type": "http",
      "url": "https://pdf-merge.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-pdf-merge]
url = "https://pdf-merge.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-pdf-merge": {
      "type": "remote",
      "url": "https://pdf-merge.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-pdf-merge --url 'https://pdf-merge.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-pdf-merge:
    url: "https://pdf-merge.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-pdf-merge": {
      "Transport": "http",
      "Url": "https://pdf-merge.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-pdf-merge -t streamable-http -u 'https://pdf-merge.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-pdf-merge": {
      "type": "http",
      "url": "https://pdf-merge.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-19 (score 78, +1)

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

### 2026-11-17 (score 77, +1)

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

### 2026-11-15 (score 76, +1)

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

### 2026-11-13 (score 75, +1)

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

### 2026-11-11 (score 74, +1)

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

### 2026-11-09 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 72)

First indexed and scored.

## MCP tools (3)

### `merge_pdfs` (~285 tokens)

Merge PDFs

Use this when the user wants to merge PDF files, combine PDFs into one, join PDF pages, reorder PDF pages, take only some pages of each PDF, delete pages from a PDF, or rotate PDF pages. Takes 1 to 20 attached PDFs in attach order and an optional list of parts (file number, page ranges like "1-3, 7, 10-end", pages to skip, rotation 90/180/270), and returns one new PDF with the page plan and a check that the output page count, order, sizes and rotation match the plan. With one file, it can delete, reorder or rotate pages. Does not open password-protected PDFs, does not keep form fields editable (they are flattened), and does not edit text. Do not use for splitting one PDF into several files (use split_pdf).

Input parameters:

- `files` (array, required): The PDFs to merge, in order, e.g. cover.pdf, report.pdf, appendix.pdf.
- `output_name` (string): File name for the result, e.g. contract-signed-set.pdf. Default: merged.pdf.
- `parts` (array): Optional page plan, in output order, e.g. [{"file":2,"pages":"1-3"},{"file":1,"pages":"all","rotate":90}]. Default: all pages of all files in attach order.

Output parameters:

- `check` (object)
- `downloads` (object)
- `expires_in_hours` (number)
- `files` (array)
- `notes` (array)
- `output_name` (string)
- `output_pages` (number)
- `output_size_kb` (number)
- `plan` (array)
- `plan_count` (object)

### `split_pdf` (~248 tokens)

Split a PDF

Use this when the user wants to split a PDF into several files, break a PDF into parts, extract page ranges as separate PDFs, split in groups of N pages, or save each page as its own PDF. Takes one attached PDF and one of: ranges (each item becomes one file, e.g. ["1-3", "4-end"]), every_n_pages, or each_page. Returns a ZIP of up to 50 PDFs, plus separate links when there are 10 parts or fewer, and checks each part's page count. Does not open password-protected PDFs and flattens form fields. Do not use for combining several PDFs (use merge_pdfs).

Input parameters:

- `each_page` (boolean): true: one PDF per page, e.g. true.
- `every_n_pages` (integer): Make a new file in groups of N pages, e.g. 2.
- `file` (object, required): The PDF to split, e.g. handbook.pdf.
- `ranges` (array): One item per output file, e.g. ["1-4", "5-12", "13-end"]. An item may list several ranges: "1-2, 9".

Output parameters:

- `check` (object)
- `downloads` (object)
- `expires_in_hours` (number)
- `file` (string)
- `notes` (array)
- `parts` (array)
- `parts_count` (number)
- `parts_shown` (object)
- `source_pages` (number)

### `inspect_pdf` (~117 tokens)

Inspect a PDF

Use this when the user wants to know how many pages a PDF has, its page sizes (Letter, A4, landscape), which pages are rotated or cropped, whether it is password-protected, whether it has form fields, or whether it has selectable text, before merging or splitting it. Takes one attached PDF and returns these facts with no new file. Does not read or summarize the text, does not run OCR, and does not change the file.

Input parameters:

- `file` (object, required): The PDF to inspect, e.g. contract.pdf.

Output parameters:

- `cropped_pages` (number)
- `encrypted` (boolean)
- `file` (string)
- `form_fields` (number)
- `has_text` (string)
- `notes` (array)
- `page_sizes` (array)
- `pages` (number)
- `rotated_pages` (array)
- `size_mb` (number)
- `text_check` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 73
- 2026-11-09: 73
- 2026-11-08: 72

## Common questions

### What is the Zovo PDF Merge MCP server?

Zovo PDF Merge is an MCP server listed in the public MCP registry as io.github.theluckystrike/pdf-merge. Merge PDF files into one document right in the chat. This page covers its hosted endpoint (https://pdf-merge.zovo.one/mcp).

### Is the Zovo PDF Merge MCP server safe to use?

Zovo PDF Merge scores 78 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 Zovo PDF Merge MCP server expose?

Zovo PDF Merge exposes 3 tools: merge_pdfs, split_pdf, inspect_pdf. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.

### Does the Zovo PDF Merge MCP server require authentication?

No. We connected to Zovo PDF Merge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo PDF Merge MCP server still maintained?

Zovo PDF Merge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zovo PDF Merge MCP server?

VerifyMCP ran 14 checks on Zovo PDF Merge, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pdf-merge.zovo.one/mcp
- Website: https://pdf-merge.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-pdf-merge/pdf-merge
