# Zovo PDF Sign (remote · pdf-sign.zovo.one)

Puts a visible signature, initials and a date on a PDF document you attach.

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

## Components

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

## Channel facts

- Endpoint: `https://pdf-sign.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 774 tokens (~258/item across 3 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 PDF Sign MCP server?

Zovo PDF Sign is a hosted endpoint at https://pdf-sign.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-pdf-sign 'https://pdf-sign.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-pdf-sign:
    url: "https://pdf-sign.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-pdf-sign": {
      "type": "http",
      "url": "https://pdf-sign.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 (2)

### `find_signature_spots` (~173 tokens)

Find signature spots

Use this when the user wants to sign a PDF, fill in a signature line, find where to sign, or add initials or a date to a PDF form or contract. It reads the PDF's text positions and lists each place labelled Signature, Sign here, Signed, Initials, Date or Name, each blank ____ line, and each empty signature form field, with page, x, y (points from the top-left as displayed), width and a spot id for sign_pdf. Makes no file. Up to 15 MB; the first 50 pages are searched. Does not read scanned PDFs without a text layer (then give page and position to sign_pdf). Do not use for reading or summarizing a contract.

Input parameters:

- `file` (object, required): The PDF to look in, e.g. contract.pdf.

Output parameters:

- `file` (string)
- `has_text` (boolean)
- `note` (string)
- `page_sizes` (array)
- `pages` (number)
- `pages_scanned` (number)
- `spots` (array)
- `spots_count` (object)
- `warnings` (array)

### `sign_pdf` (~513 tokens)

Sign a PDF

Use this when the user wants to sign a PDF, e-sign a document, add a signature, initials or a date to a PDF, or put their name on a signature line. It draws a visible mark on a copy of the user's PDF at found spots (ids from find_signature_spots) or at a page and position: a drawn signature (SVG path from the widget pad) or a typed name in an italic font, initials, a date in the chosen format from the user's date, or short text. It returns the signed copy as a download kept for about 1 hour and checks that each mark is in the file. It is not a certified digital signature: no certificate, identity check or audit trail. Does not fill form fields with data and does not send the document to anyone. Do not use for certificate-based digital signatures or for signing on someone else's behalf without their consent.

Input parameters:

- `date` (string): The signing date in the user's own calendar, YYYY-MM-DD, e.g. 2026-11-04. Default: today in time_zone.
- `date_format` (string): How the date is printed, e.g. MM/DD/YYYY (default).
- `file` (object, required): The PDF to sign, e.g. lease.pdf.
- `flatten_form` (boolean): true: also flatten the PDF's form fields so their current values print as page content. Default false.
- `initials` (string): Initials to use, e.g. JD. Default: first letters of signer_name.
- `output_name` (string): File name for the signed copy, e.g. lease-signed. Default: the original name plus -signed.
- `placements` (array, required): Where to put each mark, e.g. [{"spot":"s1","kind":"signature"},{"spot":"s2","kind":"date"}].
- `signature_svg` (string): A drawn signature as SVG path data with absolute M, L, C, Q, Z only (max 20 KB), e.g. M10 40 C20 10 40 10 50 40. The widget pad sends this.
- `signer_name` (string): The signer's name, up to 80 characters, e.g. Jane Doe. Typed signatures are drawn in an italic font; also used for initials.
- `time_zone` (string): The user's IANA time zone for today's date when no date is given, e.g. Europe/Berlin. Default America/New_York.

Output parameters:

- `date_used` (string)
- `downloads` (object)
- `file` (string)
- `flattened` (boolean)
- `marks` (array)
- `marks_count` (object)
- `marks_found` (number)
- `note` (string)
- `pages` (number)
- `text_expected` (number)
- `text_found` (number)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-pdf-sign/pdf-sign#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 PDF Sign MCP server?

Zovo PDF Sign is an MCP server listed in the public MCP registry as io.github.theluckystrike/pdf-sign. Puts a visible signature, initials and a date on a PDF document you attach. This page covers its hosted endpoint (https://pdf-sign.zovo.one/mcp).

### Is the Zovo PDF Sign MCP server safe to use?

Zovo PDF Sign 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 PDF Sign MCP server expose?

Zovo PDF Sign exposes 2 tools: find_signature_spots, sign_pdf. Their descriptions and schemas cost roughly 686 tokens of context every time the server is loaded.

### Does the Zovo PDF Sign MCP server require authentication?

No. We connected to Zovo PDF Sign without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo PDF Sign MCP server still maintained?

Zovo PDF Sign 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 Sign MCP server?

VerifyMCP ran 14 checks on Zovo PDF Sign, 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://pdf-sign.zovo.one/mcp
- Website: https://pdf-sign.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-pdf-sign/pdf-sign.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-pdf-sign/pdf-sign/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-pdf-sign/pdf-sign.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-pdf-sign/pdf-sign
