Zovo PDF Sign
REMOTE · PDF-SIGN.ZOVO.ONE
Puts a visible signature, initials and a date on a PDF document you attach.
Available components
Last scanned (20 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 774 tokens (~258/item across 3 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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://pdf-sign.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 pdf-sign.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://pdf-sign.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://pdf-sign.zovo.one/mcp | HTTPS enforced | 301 | https://pdf-sign.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 →
find_signature_spots Find signature spots ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | The PDF to look in, e.g. contract.pdf. |
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | – |
| has_text | boolean | yes | – |
| note | string | yes | – |
| page_sizes | array | yes | – |
| pages | number | yes | – |
| pages_scanned | number | yes | – |
| spots | array | yes | – |
| spots_count | object | – | – |
| warnings | array | yes | – |
No examples provided.
sign_pdf Sign a PDF ~513
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| date_used | string | – | – |
| downloads | object | yes | – |
| file | string | yes | – |
| flattened | boolean | yes | – |
| marks | array | yes | – |
| marks_count | object | – | – |
| marks_found | number | yes | – |
| note | string | yes | – |
| pages | number | yes | – |
| text_expected | number | yes | – |
| text_found | number | yes | – |
| warnings | array | yes | – |
No examples provided.
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.
remote · pdf-sign.zovo.one
claude mcp add --transport http theluckystrike-pdf-sign 'https://pdf-sign.zovo.one/mcp'
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.