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.

Zovo PDF Merge

REMOTE · PDF-MERGE.ZOVO.ONE

Merge PDF files into one document right in the chat.

+3 this week 78 Trust /100

Last scanned (16 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 5 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
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 72

    First indexed and scored.

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 21 Nov 2026 · Probed https://pdf-merge.zovo.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 1a6be51dae225a780e14b5b59cd24fa3
SANs: zovo.one, *.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pdf-merge.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pdf-merge.zovo.one/mcp Verified 200
http (plaintext) http://pdf-merge.zovo.one/mcp HTTPS enforced 301 https://pdf-merge.zovo.one/mcp
MCP tools · 3 exposed · ~650 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
inspect_pdf ~117

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.

NameTypeReqDescription
fileobjectyesThe PDF to inspect, e.g. contract.pdf.
NameTypeReqDescription
cropped_pagesnumberyes–
encryptedbooleanyes–
filestringyes–
form_fieldsnumberyes–
has_textstringyes–
notesarrayyes–
page_sizesarrayyes–
pagesnumberyes–
rotated_pagesarrayyes–
size_mbnumberyes–
text_checkstringyes–

No examples provided.

merge_pdfs ~285

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

NameTypeReqDescription
filesarrayyesThe PDFs to merge, in order, e.g. cover.pdf, report.pdf, appendix.pdf.
output_namestring–File name for the result, e.g. contract-signed-set.pdf. Default: merged.pdf.
partsarray–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.
NameTypeReqDescription
checkobjectyes–
downloadsobjectyes–
expires_in_hoursnumberyes–
filesarrayyes–
notesarrayyes–
output_namestringyes–
output_pagesnumberyes–
output_size_kbnumberyes–
planarrayyes–
plan_countobject––

No examples provided.

split_pdf ~248

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

NameTypeReqDescription
each_pageboolean–true: one PDF per page, e.g. true.
every_n_pagesinteger–Make a new file in groups of N pages, e.g. 2.
fileobjectyesThe PDF to split, e.g. handbook.pdf.
rangesarray–One item per output file, e.g. ["1-4", "5-12", "13-end"]. An item may list several ranges: "1-2, 9".
NameTypeReqDescription
checkobjectyes–
downloadsobjectyes–
expires_in_hoursnumberyes–
filestringyes–
notesarrayyes–
partsarrayyes–
parts_countnumberyes–
parts_shownobject––
source_pagesnumberyes–

No examples provided.

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.

remote · pdf-merge.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-pdf-merge 'https://pdf-merge.zovo.one/mcp'
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.