# Zovo Document Compare (remote · text-compare.zovo.one)

Compare two documents for differences and see each word that changed, not a summary.

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

## Components

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

## Channel facts

- Endpoint: `https://text-compare.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**: 70/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 695 tokens (~347/item across 2 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-text-compare:
    url: "https://text-compare.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

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

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

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

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

### 2026-11-13 (score 75, +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-10 (score 74, +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.

### 2026-11-09 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (1)

### `compare_documents` (~530 tokens)

Compare two documents

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.

Input parameters:

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

Output parameters:

- `changes` (array)
- `changes_shown` (object)
- `counts` (object)
- `downloads` (object)
- `identical` (boolean)
- `material_changes` (array)
- `normalized` (string)
- `notes` (array)
- `original` (object)
- `page_size` (string)
- `redline` (string)
- `revised` (object)
- `summary` (string)

## Diagnostics

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

## Score history

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

## Common questions

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

## Links

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