Zovo Page Numbers
REMOTE · PAGE-NUMBERS.ZOVO.ONE
Add page numbers, Bates numbers or a text watermark to a PDF document right in the chat.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 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 1229 tokens (~307/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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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 →
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 Nov 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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 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 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 73
First indexed and scored.
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://page-numbers.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 page-numbers.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://page-numbers.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://page-numbers.zovo.one/mcp | HTTPS enforced | 301 | https://page-numbers.zovo.one/mcp |
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 →
stamp_bates_numbers Bates number a PDF ~374
Use this when the user wants to Bates number a PDF, Bates stamp documents for a legal production, or add sequential document control numbers such as ACME000101 to each page. Takes one attached PDF, a prefix, start number, zero-padding digits (1-10), optional suffix and one of six positions, and returns a new PDF plus a CSV log of page number to Bates number, with the first and last Bates number. Each stamp is checked again in the new file before the link is given. Does not open password-protected PDFs, does not number across several files in one call (pass the next start number yourself), and does not draw non-Latin scripts. Do not use for simple page numbers (use stamp_page_numbers).
| Name | Type | Req | Description |
|---|---|---|---|
| digits | integer | – | Zero-pad the number to this many digits, 1 to 10, e.g. 6 gives 000101. Default 6. |
| file | object | yes | The PDF to Bates number, e.g. production-vol1.pdf. |
| font_size | number | – | Font size in points from 6 to 36, e.g. 10 (default). |
| margin_pt | number | – | Distance from the page edge in points from 6 to 144, e.g. 24 (default). |
| position | string | – | Where the text goes on each page as viewed: top-left, top-center, top-right, bottom-left, bottom-center, bottom-right. Default bottom-right. |
| prefix | string | – | Text before the number, e.g. "ACME" or "SMITH-". Default none. |
| start | integer | – | First Bates number, e.g. 101. Default 1. |
| suffix | string | – | Text after the number, e.g. "-CONF". Default none. |
| Name | Type | Req | Description |
|---|---|---|---|
| check | object | yes | – |
| downloads | object | yes | – |
| expires_in_hours | number | yes | – |
| file | string | yes | – |
| first_bates | string | yes | – |
| first_stamp | object | yes | – |
| font_size | number | yes | – |
| last_bates | string | yes | – |
| last_stamp | object | yes | – |
| notes | array | yes | – |
| output_name | string | yes | – |
| output_size_kb | number | yes | – |
| pages | number | yes | – |
| position | string | yes | – |
| stamped_pages | number | yes | – |
No examples provided.
stamp_page_numbers Number PDF pages ~375
Use this when the user wants to add page numbers to a PDF, number the pages of a PDF, put "Page 1 of 10" in a footer or header, or skip numbering the cover page. Takes one attached PDF, a format with {n} (this page's number) and optional {total} (the last number), one of six positions, start number, pages to skip at the start, font size and margin, and returns a new PDF. Each stamp is checked again in the new file before the link is given. Does not open password-protected PDFs, does not draw non-Latin scripts or emoji, and does not change the page content under the number. Do not use for Bates numbers (use stamp_bates_numbers).
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | The PDF to number, e.g. report.pdf. |
| font_size | number | – | Font size in points from 6 to 36, e.g. 10 (default). |
| format | string | – | Text with {n} and optional {total}, e.g. "Page {n} of {total}" (default), "{n}", "{n}/{total}" or "- {n} -". |
| margin_pt | number | – | Distance from the page edge in points from 6 to 144, e.g. 36 (half an inch, default). |
| position | string | – | Where the text goes on each page as viewed: top-left, top-center, top-right, bottom-left, bottom-center, bottom-right. Default bottom-center. |
| skip_first | integer | – | How many pages at the start get no number, e.g. 1 for a cover page. Default 0. |
| start_number | integer | – | Number for the first numbered page, e.g. 1 (default). |
| Name | Type | Req | Description |
|---|---|---|---|
| check | object | yes | – |
| downloads | object | yes | – |
| expires_in_hours | number | yes | – |
| file | string | yes | – |
| first_stamp | object | yes | – |
| font_size | number | yes | – |
| format | string | yes | – |
| last_stamp | object | yes | – |
| notes | array | yes | – |
| output_name | string | yes | – |
| output_size_kb | number | yes | – |
| pages | number | yes | – |
| position | string | yes | – |
| skipped_pages | string | yes | – |
| stamped_pages | number | yes | – |
No examples provided.
stamp_watermark Watermark a PDF ~332
Use this when the user wants to add a watermark to a PDF, stamp DRAFT, CONFIDENTIAL, COPY or SAMPLE across the pages, or mark only some pages. Takes one attached PDF, the watermark text (up to 40 characters), opacity from 0.05 to 0.5, angle from -90 to 90 degrees, optional pages such as "1-3, 8" and optional font size, and returns a new PDF with the text centered on each chosen page. Each stamp is checked again in the new file before the link is given. Does not add image or logo watermarks, does not open password-protected PDFs, and the text can be removed with PDF editing software. Do not use for page numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| angle | number | – | Angle in degrees counter-clockwise, -90 to 90, e.g. 45 (default) or 0 for flat. |
| file | object | yes | The PDF to watermark, e.g. proposal.pdf. |
| font_size | number | – | Font size in points, 8 to 300, e.g. 72. Default: fit the page. |
| opacity | number | – | How strong the text is, 0.05 (faint) to 0.5, e.g. 0.15 (default). |
| pages | string | – | Pages to mark, e.g. "all" (default) or "1-3, 8, 10-end". |
| text | string | yes | Watermark text, e.g. "DRAFT" or "CONFIDENTIAL". |
| Name | Type | Req | Description |
|---|---|---|---|
| angle | number | yes | – |
| check | object | yes | – |
| downloads | object | yes | – |
| expires_in_hours | number | yes | – |
| file | string | yes | – |
| first_stamp | object | yes | – |
| font_size | number | yes | – |
| last_stamp | object | yes | – |
| notes | array | yes | – |
| opacity | number | yes | – |
| output_name | string | yes | – |
| output_size_kb | number | yes | – |
| page_list | string | yes | – |
| pages | number | yes | – |
| position | string | yes | – |
| stamped_pages | number | yes | – |
| text | string | yes | – |
No examples provided.
How do I install the Zovo Page Numbers MCP server?
Zovo Page Numbers is a hosted endpoint at https://page-numbers.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 · page-numbers.zovo.one
claude mcp add --transport http theluckystrike-page-numbers 'https://page-numbers.zovo.one/mcp'
What is the Zovo Page Numbers MCP server?
Zovo Page Numbers is an MCP server listed in the public MCP registry as io.github.theluckystrike/page-numbers. Add page numbers, Bates numbers or a text watermark to a PDF document right in the chat. This page covers its hosted endpoint (https://page-numbers.zovo.one/mcp).
Is the Zovo Page Numbers MCP server safe to use?
Zovo Page Numbers scores 79 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 Page Numbers MCP server expose?
Zovo Page Numbers exposes 3 tools: stamp_page_numbers, stamp_bates_numbers, stamp_watermark. Their descriptions and schemas cost roughly 1,081 tokens of context every time the server is loaded.
Does the Zovo Page Numbers MCP server require authentication?
No. We connected to Zovo Page Numbers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Page Numbers MCP server still maintained?
Zovo Page Numbers 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 Page Numbers MCP server?
VerifyMCP ran 14 checks on Zovo Page Numbers, 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.