Skip to content

Zovo PDF Merge MCP server

io.github.theluckystrike/pdf-mergetheluckystrikestreamable-httpv1.0.0Scanned

Merge PDF files into one document right in the chat.

3 tools: 1 do something that can't be undone, 1 change things and 1 only read.

Tools: 0 delete, 1 irreversible, 1 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Zovo PDF Merge MCP server can do

The Zovo PDF Merge MCP server is published by the GitHub account theluckystrike. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (merge_pdfs) and create or change data (1 tool: split_pdf), but cannot delete data. 1 tool only reads.

1 tool reads private data (inspect_pdf).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Can't be undone 1Claude Code: ask
  • merge_pdfsUse 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 …1 finding

    Why it is in this group

    • The name "merge_pdfs" says "merge": a word for a change that another call does not undo.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "merge_pdfs" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "merge_pdfs" says "merge": a word for a change that another call does not undo.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Merge PDFs
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Changes things 1Claude Code: ask
  • split_pdfUse 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 o…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Split a PDF
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • inspect_pdfUse 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…Reads private dataNo findings

    Why it is in this group

    • The name "inspect_pdf" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "password": it reads secrets.
    • private-dataThe input names a file (input.file), and the tool reads: it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Inspect a PDF
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:23 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pdf-merge.zovo.one/mcp: tools/list returned 3 tools to an anonymous client, including merge_pdfs (irreversible), split_pdf (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "merge_pdfs" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "merge_pdfs" says "merge": a word for a change that another call does not undo.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pdf-merge https://pdf-merge.zovo.one/mcp
claude mcp add --transport http pdf-merge https://pdf-merge.zovo.one/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pdf-merge__inspect_pdf"
    ],
    "ask": [
      "mcp__pdf-merge__merge_pdfs",
      "mcp__pdf-merge__split_pdf"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pdf-merge. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pdf-merge__inspect_pdf private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/pdf-merge/verify?hash=39e52db8b0f8c9a7f6dda09ead073950f58c1192bfbb92a222b83aa440088040" | jq -e '.changed == false'

Pinned hash 39e52db8b0f8, from Nov 8, 2026, 02:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/pdf-merge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/pdf-merge
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/pdf-merge.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/pdf-merge)

Source: MCP Registry. Synced Nov 8, 2026, 03:18 UTC.

Zovo PDF Merge MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zovo PDF Merge MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Zovo PDF Merge MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Zovo PDF Merge MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: merge_pdfs.

What tools does the Zovo PDF Merge MCP server have?

3 tools: 1 irreversible, 1 write, 1 read. merge_pdfs, split_pdf and inspect_pdf.

Does the Zovo PDF Merge MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Zovo PDF Merge MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Zovo PDF Merge MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.