Zovo Document Compare
REMOTE · TEXT-COMPARE.ZOVO.ONE
Compare two documents for differences and see each word that changed, not a summary.
Available components
Last scanned (18 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 Usability70
- 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 695 tokens (~347/item across 2 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
- 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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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.
- 10 Nov 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 Nov 26 0
- 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://text-compare.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 text-compare.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://text-compare.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://text-compare.zovo.one/mcp | HTTPS enforced | 301 | https://text-compare.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 →
compare_documents Compare two documents ~530
Use this when the user wants to compare two documents for differences, compare two versions of a contract, lease, policy or any text, or wants a redline comparison. Put the full text of each version into original_text and revised_text word for word (do not summarize, shorten or fix it); if the user shares screenshots or images of pages, transcribe their text word for word into those fields. For uploaded Word .docx, text PDF or .txt files, pass them in original_file and revised_file. Returns each changed word with the paragraph number, flags changes to numbers, negations and modal verbs (shall, may, must) as material, and makes a redline PDF, an Excel change list and a Word file with tracked changes. Only whitespace and quote style are normalized. Does not read scanned PDFs, does not compare formatting, headers or footers, and does not give legal advice. Do not use for comparing spreadsheets or data tables.
| Name | Type | Req | Description |
|---|---|---|---|
| original_file | object | – | The ORIGINAL version as an uploaded file: Word .docx, text PDF or .txt, e.g. contract-v1.docx. |
| original_name | string|null | – | Optional label for the original, e.g. "Lease v1 (March)". Default: the file name or "Original". |
| original_text | string|null | – | The ORIGINAL (older) version, pasted in full and word for word, e.g. "1. The Tenant shall pay rent of $1,200 on the first day of each month.\n2. ...". Keep paragraphs on separate lines. Leave empty w… |
| page_size | string|null | – | PDF page size: "Letter" (default) or "A4". |
| revised_file | object | – | The REVISED version as an uploaded file: Word .docx, text PDF or .txt, e.g. contract-v2.pdf. |
| revised_name | string|null | – | Optional label for the revised version, e.g. "Lease v2 (landlord edits)". Default: the file name or "Revised". |
| revised_text | string|null | – | The REVISED (newer) version, pasted in full and word for word, e.g. "1. The Tenant may pay rent of $1,250 on the first day of each month.\n2. ...". Leave empty when revised_file is given. |
| show | string|null | – | Redline PDF content: "full" (default, the whole revised document with changes marked) or "changes" (only the changed paragraphs). |
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | – |
| changes_shown | object | – | – |
| counts | object | yes | – |
| downloads | object | yes | – |
| identical | boolean | yes | – |
| material_changes | array | yes | – |
| normalized | string | yes | – |
| notes | array | yes | – |
| original | object | yes | – |
| page_size | string | yes | – |
| redline | string | yes | – |
| revised | object | yes | – |
| summary | string | yes | – |
No examples provided.
How do I install the Zovo Document Compare MCP server?
Zovo Document Compare is a hosted endpoint at https://text-compare.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 · text-compare.zovo.one
claude mcp add --transport http theluckystrike-text-compare 'https://text-compare.zovo.one/mcp'
What is the Zovo Document Compare MCP server?
Zovo Document Compare is an MCP server listed in the public MCP registry as io.github.theluckystrike/text-compare. Compare two documents for differences and see each word that changed, not a summary. This page covers its hosted endpoint (https://text-compare.zovo.one/mcp).
Is the Zovo Document Compare MCP server safe to use?
Zovo Document Compare 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 Document Compare MCP server expose?
Zovo Document Compare exposes 1 tool: compare_documents. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.
Does the Zovo Document Compare MCP server require authentication?
No. We connected to Zovo Document Compare without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zovo Document Compare MCP server still maintained?
Zovo Document Compare 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 Document Compare MCP server?
VerifyMCP ran 14 checks on Zovo Document Compare, 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.