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

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

## Components

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

## Channel facts

- Endpoint: `https://page-numbers.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**: 73/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 1229 tokens (~307/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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-page-numbers 'https://page-numbers.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-page-numbers:
    url: "https://page-numbers.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-page-numbers": {
      "type": "http",
      "url": "https://page-numbers.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-20 (score 79, +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.

### 2026-11-18 (score 78, +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.

### 2026-11-16 (score 77, +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.

### 2026-11-13 (score 76, +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 75, +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 74, +1)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (3)

### `stamp_page_numbers` (~375 tokens)

Number PDF pages

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

Input parameters:

- `file` (object, required): 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).

Output parameters:

- `check` (object)
- `downloads` (object)
- `expires_in_hours` (number)
- `file` (string)
- `first_stamp` (object)
- `font_size` (number)
- `format` (string)
- `last_stamp` (object)
- `notes` (array)
- `output_name` (string)
- `output_size_kb` (number)
- `pages` (number)
- `position` (string)
- `skipped_pages` (string)
- `stamped_pages` (number)

### `stamp_bates_numbers` (~374 tokens)

Bates number a PDF

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

Input parameters:

- `digits` (integer): Zero-pad the number to this many digits, 1 to 10, e.g. 6 gives 000101. Default 6.
- `file` (object, required): 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.

Output parameters:

- `check` (object)
- `downloads` (object)
- `expires_in_hours` (number)
- `file` (string)
- `first_bates` (string)
- `first_stamp` (object)
- `font_size` (number)
- `last_bates` (string)
- `last_stamp` (object)
- `notes` (array)
- `output_name` (string)
- `output_size_kb` (number)
- `pages` (number)
- `position` (string)
- `stamped_pages` (number)

### `stamp_watermark` (~332 tokens)

Watermark a PDF

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.

Input parameters:

- `angle` (number): Angle in degrees counter-clockwise, -90 to 90, e.g. 45 (default) or 0 for flat.
- `file` (object, required): 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, required): Watermark text, e.g. "DRAFT" or "CONFIDENTIAL".

Output parameters:

- `angle` (number)
- `check` (object)
- `downloads` (object)
- `expires_in_hours` (number)
- `file` (string)
- `first_stamp` (object)
- `font_size` (number)
- `last_stamp` (object)
- `notes` (array)
- `opacity` (number)
- `output_name` (string)
- `output_size_kb` (number)
- `page_list` (string)
- `pages` (number)
- `position` (string)
- `stamped_pages` (number)
- `text` (string)

## Diagnostics

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

## Score history

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

## Common questions

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

## Links

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