# Zovo Spreadsheet Checker (remote · sheet-validate.zovo.one)

Check a spreadsheet for errors before you import it, send it or report from it.

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

## Components

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

## Channel facts

- Endpoint: `https://sheet-validate.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 1189 tokens (~396/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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Spreadsheet Checker MCP server?

Zovo Spreadsheet Checker is a hosted endpoint at https://sheet-validate.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-sheet-validate 'https://sheet-validate.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-sheet-validate:
    url: "https://sheet-validate.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

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

### `check_spreadsheet` (~750 tokens)

Check spreadsheet for errors

Use this when the user wants to check a spreadsheet for errors or validate data before importing or sending it: "check spreadsheet for errors", "data validation excel", "find duplicates in excel", "check this csv for errors", "find invalid dates", "are there bad emails in this list". Attach a CSV, TSV or .xlsx file or paste the table. With no rules it detects column types from the values and checks impossible, ambiguous and mixed-format dates, invalid emails and email typos, phone digit counts, duplicate IDs and duplicate rows, blank cells in mostly filled columns, text in number columns, numbers stored as text, mixed decimal marks, leading/trailing spaces, IDs that lost leading zeros or became 1.2E+15, formula errors and row totals that do not add up. Optional rules: required_columns, unique_columns, allowed_values, ranges, total_rules. Returns each issue with row, column and cell value, counts per check, a column health score, an Excel copy with problem cells highlighted plus an Issues sheet, and an issues CSV. Does not edit or clean the data, does not verify that mailboxes or phone lines exist, and does not compare two files (use a comparison tool for that).

Input parameters:

- `allowed_values`: Allowed values per column, e.g. {"Status":["Open","Closed"]} or "Status: Open, Closed; Region: North, South".
- `date_order` (string): Day/month order for dates like 03/04/2026: auto (default), MDY (US, month first) or DMY (day first).
- `file` (object): The spreadsheet to check: CSV, TSV or Excel .xlsx, e.g. customers.xlsx.
- `header_row`: Only if the headings were detected wrongly: the row number of the header, e.g. 3.
- `ranges`: Numeric limits per column, e.g. {"Age":"0-120","Discount":{"min":0,"max":50}} or "Age: 0-120; Qty: >= 1".
- `required_columns`: Columns that must never be blank, e.g. ["Email","Order ID"] or "Email, Order ID". Default: columns that are almost fully filled are treated as required (blanks reported as warnings).
- `sheet`: Sheet name or number in an Excel workbook, e.g. Orders or 2. Default: the first sheet with data.
- `skip_checks`: Checks to turn off, e.g. ["extra_spaces"]. Options: impossible_date, mixed_date_order, ambiguous_date, mixed_date_format, implausible_date, not_a_date, invalid_email, email_typo, invalid_phone, dupli…
- `table`: Only when no file is attached: the table pasted as CSV, tab-separated or a Markdown table with its header row, e.g. "id,date,email\n1,2026-02-30,ana@example.com". A list of rows also works.
- `total_rules`: Totals that must add up, e.g. "Total = Q1 + Q2 + Q3 + Q4" or "Amount = Qty * Price". Default: total columns are detected and checked automatically.
- `unique_columns`: Columns whose values must not repeat, e.g. "Order ID". Default: the ID column is detected from its header and values.

Output parameters:

- `checks` (array)
- `columns` (array)
- `copy` (string)
- `downloads` (object)
- `file` (object)
- `issues_preview` (array)
- `kind` (string)
- `notes` (array)
- `rules_applied` (array)
- `summary` (object)
- `totals_checked` (array)

### `list_spreadsheet_columns` (~291 tokens)

List spreadsheet columns

Use this when the user wants to see what is in a spreadsheet before validating it, or asks which columns, types or values it has: "what columns are in this file", "profile this csv", "which column is the ID", "suggest validation rules". Attach a CSV, TSV or .xlsx file or paste the table. Returns each column's letter, name, detected type (date, email, phone, ID, ZIP, number, money, percent, text), filled and blank counts, unique values, examples, min/max for numbers, short value lists, and suggested rules to pass to check_spreadsheet. Does not report errors (use check_spreadsheet) and does not change the file.

Input parameters:

- `file` (object): The spreadsheet to check: CSV, TSV or Excel .xlsx, e.g. customers.xlsx.
- `header_row`: Only if the headings were detected wrongly: the row number of the header, e.g. 3.
- `sheet`: Sheet name or number in an Excel workbook, e.g. Orders or 2. Default: the first sheet with data.
- `table`: Only when no file is attached: the table pasted as CSV, tab-separated or a Markdown table with its header row, e.g. "id,date,email\n1,2026-02-30,ana@example.com". A list of rows also works.

Output parameters:

- `columns` (array)
- `file` (object)
- `kind` (string)
- `notes` (array)
- `suggested_rules` (object)

## Diagnostics

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

Zovo Spreadsheet Checker is an MCP server listed in the public MCP registry as io.github.theluckystrike/sheet-validate. Check a spreadsheet for errors before you import it, send it or report from it. This page covers its hosted endpoint (https://sheet-validate.zovo.one/mcp).

### Is the Zovo Spreadsheet Checker MCP server safe to use?

Zovo Spreadsheet Checker 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 Spreadsheet Checker MCP server expose?

Zovo Spreadsheet Checker exposes 2 tools: check_spreadsheet, list_spreadsheet_columns. Their descriptions and schemas cost roughly 1,041 tokens of context every time the server is loaded.

### Does the Zovo Spreadsheet Checker MCP server require authentication?

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

### Is the Zovo Spreadsheet Checker MCP server still maintained?

Zovo Spreadsheet Checker 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 Spreadsheet Checker MCP server?

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