io.github.theluckystrike/pdf-merge-split-stamp-extract-pages
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Merge, split, extract, rotate, reorder and stamp PDF pages from your AI chat, all offline.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2139 tokens (~125/item across 17 items; 15 tools + 2 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pdf_merge" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.theluckystrike/pdf-merge-split-stamp-extract-pages MCP server?
io.github.theluckystrike/pdf-merge-split-stamp-extract-pages is a hosted endpoint at https://mcp.zovo.one/mcp/pdf, 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 · mcp.zovo.one
claude mcp add --transport http theluckystrike-pdf-merge-split-stamp-extract-pag 'https://mcp.zovo.one/mcp/pdf'
{
"mcpServers": {
"theluckystrike-pdf-merge-split-stamp-extract-pag": {
"url": "https://mcp.zovo.one/mcp/pdf"
}
}
} {
"servers": {
"theluckystrike-pdf-merge-split-stamp-extract-pag": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/pdf"
}
}
} [mcp_servers.theluckystrike-pdf-merge-split-stamp-extract-pag] url = "https://mcp.zovo.one/mcp/pdf"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-pdf-merge-split-stamp-extract-pag": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/pdf",
"enabled": true
}
}
} openclaw mcp add theluckystrike-pdf-merge-split-stamp-extract-pag --url 'https://mcp.zovo.one/mcp/pdf' --transport streamable-http
mcp_servers:
theluckystrike-pdf-merge-split-stamp-extract-pag:
url: "https://mcp.zovo.one/mcp/pdf" {
"McpServers": {
"theluckystrike-pdf-merge-split-stamp-extract-pag": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/pdf"
}
}
} assistant mcp add theluckystrike-pdf-merge-split-stamp-extract-pag -t streamable-http -u 'https://mcp.zovo.one/mcp/pdf'
{
"mcpServers": {
"theluckystrike-pdf-merge-split-stamp-extract-pag": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/pdf"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +57
- Authorization: unverified → fail ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.33 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 17 Sept 26 −56
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.27 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Server version: 0.21.0 → 0.22.0 functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 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.
- 9 Sept 26 0
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “pdf_count” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/pdf
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 | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.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 mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/pdf | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/pdf | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/pdf |
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 →
license_activate Activate license ~76
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pdf_count Count pages in several PDFs ~67
Page count per file plus the total, for any number of PDFs, with how many were readable. A file that cannot be read is reported on its own row and the others still count. Read-only. Free and unlimited.
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | Names of PDFs uploaded with pdf_upload |
No output schema declared.
No examples provided.
pdf_delete_upload Delete a stored PDF ~28
Delete one PDF stored for your token, uploaded or generated.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
pdf_files List uploaded and generated PDFs ~31
List the PDFs stored for your token: what you uploaded, and what this server has written, with their sizes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pdf_info Inspect a PDF ~79
Call this tool to inspect a PDF: page count, page sizes in points/mm, paper name, metadata (title, author, producer, dates) and whether it is encrypted. Read-only, never modifies the file. Free tier: unlimited.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Name of a PDF uploaded with pdf_upload, or one this server wrote earlier |
No output schema declared.
No examples provided.
pdf_merge Merge PDFs into one file ~133
Call this tool to join several PDFs into one, in the order given. Page sizes are kept as-is, so a merged file may have mixed sizes, and the answer says so. Inputs are never modified. Free tier: up to 5 files per merge.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | yes | Name for the merged PDF; it comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if a file is already there. Default false: an existing file is never overwritten |
| paths | array | yes | Names of the uploaded PDFs to join, in the order they should appear |
No output schema declared.
No examples provided.
pdf_pages Extract pages into a new PDF ~161
Call this tool to pull selected pages into one new PDF, in the order written: "2,4-6" gives four pages. Asking for a page twice copies it twice. The input is never modified. Free tier: files up to 30 pages.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | yes | Name for the extracted PDF; it comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if it exists. Default false |
| pages | string | yes | 1-based pages and ranges to keep, in output order, e.g. "2,4-6" or "5,1,1" |
| path | string | yes | Name of an uploaded PDF (pdf_upload), or one this server wrote earlier |
No output schema declared.
No examples provided.
pdf_reorder Reorder the pages of a PDF ~152
Call this tool to write a new PDF with pages in the order you give. The order must name every page exactly once, so nothing drops by accident; use pdf_pages for a subset. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| order | array | yes | The 1-based page numbers in their new order, e.g. [3,1,2] for a three-page file. Every page must appear exactly once |
| out_path | string | yes | Name for the reordered PDF; it comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if it exists. Default false |
| path | string | yes | Name of an uploaded PDF (pdf_upload), or one this server wrote earlier |
No output schema declared.
No examples provided.
pdf_rotate Rotate pages ~180
Call this tool to turn pages by a multiple of 90 degrees, clockwise for positive. Rotation is added to whatever the page already had, for a sideways scan. Writes a new file. Free tier: files up to 30 pages.
| Name | Type | Req | Description |
|---|---|---|---|
| degrees | integer | yes | 90, 180, 270 or -90. Positive turns clockwise. Added to the page's existing rotation |
| out_path | string | yes | Name for the rotated PDF; it comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if it exists. Default false |
| pages | string | – | Which pages to turn, e.g. "1" or "2,4-6". Omit for every page |
| path | string | yes | Name of an uploaded PDF (pdf_upload), or one this server wrote earlier |
No output schema declared.
No examples provided.
pdf_split Split a PDF into several files ~229
Call this tool to write one new PDF per range. Ranges are 1-based and may be open-ended: "1-3,5,7-" gives pages 1-3, page 5, and 7 to the end. The input is never modified. Free tier: files up to 30 pages.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path_pattern | string | yes | Name pattern for the parts: {n} is the part number (1, 2, 3...), {range} is the range itself (e.g. 1-3), {name} is the input name. Example: {name}-{range}.pdf. Each part comes back as a download link… |
| overwrite | boolean | – | Replace existing outputs. Default false: nothing is overwritten and nothing is written at all if any target exists |
| path | string | yes | Name of the uploaded PDF to split |
| ranges | string | yes | Comma-separated 1-based page ranges, e.g. "1-3,5,7-". An open-ended range runs to the last page |
No output schema declared.
No examples provided.
pdf_stamp Stamp text on a PDF ~296
Call this tool to draw a word such as PAID or DRAFT across the pages, in a colour and position you choose. Writes a new file; input untouched. Free tier: the PAID and DRAFT presets in their preset colours.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Hex code such as #1b7f3b, or a name: red, green, blue, black, gray, orange, purple. Pro |
| font_size | number | – | Point size. By default the stamp is sized to fit the page width |
| opacity | number | – | 0 to 1. Default 0.35 in the centre, 0.85 in a corner |
| out_path | string | yes | Name for the stamped PDF; it comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if it exists. Default false |
| pages | string | – | Which pages to stamp, e.g. "1" or "2,4-6". Omit for every page |
| path | string | yes | Name of an uploaded PDF (pdf_upload), or one this server wrote earlier |
| position | string | – | Where on the page. Default center, which is drawn on the 45-degree diagonal like a real stamp |
| text | string | yes | What to stamp. PAID and DRAFT are presets with their own colour; any other text is Pro |
No output schema declared.
No examples provided.
pdf_text Read the text of a PDF ~97
Call this tool for best-effort text extraction from standard-font PDFs. Returns nothing for a scan (no OCR), or glyph indices for a custom-encoded font, and says which case applies. Read-only. Free tier: unlimited.
| Name | Type | Req | Description |
|---|---|---|---|
| pages | string | – | Which pages, e.g. "1" or "2,4-6". Omit for every page |
| path | string | yes | Name of the PDF to read |
No output schema declared.
No examples provided.
pdf_upload Upload a PDF to work on ~339
Send a PDF to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with pdf_upload and then pass its name as `path` (or inside `paths`) to pdf_info, pdf_count, pdf_merge, pdf_split, pdf_pages, pdf_rotate, pdf_stamp, pdf_reorder and pdf_text. Give exactly one of pdf_base64 or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): pasting a large base64 payload is slow to write out and can stall the turn before the call is ever sent, while a url costs one line and the fetch happens here. Uploads are kept for your token between calls; pdf_files lists them and pdf_delete_upload removes one. A file this server writes is named the same way and comes back as a download link valid for one hour. The request body cap is 256 KB, which is about 190 KB of PDF once base64-encoded; a url is fetched with a 10 second timeout, at most 3 redirects, public http(s) hosts only, and is capped at 2 MB.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name to refer to this PDF by: 1-64 characters of letters, digits, underscore or dash, e.g. "invoice" |
| pdf_base64 | string | – | The PDF file, base64-encoded |
| url | string | – | url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused |
No output schema declared.
No examples provided.
pdf_watermark_business Stamp your business details in the footer ~138
Call this tool to put your business name and VAT id in the footer of every page, from the shared profile mcp-invoice and mcp-docx write. Use it before sending a document out. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | yes | Name for the footed PDF; it comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if it exists. Default false |
| pages | string | – | Which pages, e.g. "1". Omit for every page |
| path | string | yes | Name of an uploaded PDF (pdf_upload), or one this server wrote earlier |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/pdf-merge-split-stamp-extract-pages MCP server?
io.github.theluckystrike/pdf-merge-split-stamp-extract-pages is an MCP server listed in the public MCP registry as io.github.theluckystrike/pdf-merge-split-stamp-extract-pages. Merge, split, extract, rotate, reorder and stamp PDF pages from your AI chat, all offline. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/pdf).
Is the io.github.theluckystrike/pdf-merge-split-stamp-extract-pages MCP server safe to use?
io.github.theluckystrike/pdf-merge-split-stamp-extract-pages scores 83 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 io.github.theluckystrike/pdf-merge-split-stamp-extract-pages MCP server expose?
io.github.theluckystrike/pdf-merge-split-stamp-extract-pages exposes 15 tools: pdf_info, pdf_count, pdf_merge, pdf_split, pdf_pages, and 10 more. Their descriptions and schemas cost roughly 2,061 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/pdf-merge-split-stamp-extract-pages MCP server require authentication?
Yes. io.github.theluckystrike/pdf-merge-split-stamp-extract-pages asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.theluckystrike/pdf-merge-split-stamp-extract-pages MCP server still maintained?
io.github.theluckystrike/pdf-merge-split-stamp-extract-pages is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.