# Zovo Shared Checklist (remote · shared-checklist.zovo.one)

Make one checklist page that your whole group works through: moving house, wedding prep.

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

## Components

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

## Channel facts

- Endpoint: `https://shared-checklist.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_shared_checklist).
  - 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**: 75/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 832 tokens (~208/item across 4 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Shared Checklist MCP server?

Zovo Shared Checklist is a hosted endpoint at https://shared-checklist.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-shared-checklist 'https://shared-checklist.zovo.one/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  theluckystrike-shared-checklist:
    url: "https://shared-checklist.zovo.one/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "theluckystrike-shared-checklist": {
      "type": "http",
      "url": "https://shared-checklist.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 73, +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 72, +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 71, +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-14 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 68, +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 67, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (3)

### `create_shared_checklist` (~296 tokens)

Create a shared checklist page

Use this when a group needs to work through a list together (moving house, wedding prep, event setup, onboarding a new teammate) and wants one link everyone can tick off. Publishes a page and returns a public link to share and a private organizer link. 1-150 items, each with an optional section, assignee first name and due date (YYYY-MM-DD, checked in the given time zone). Total text is limited to 64 KB: plenty for 150 items in English, about 130 items of 140 characters in Chinese, Japanese or Korean. Does not send reminders or notifications. Do not use for a private to-do list nobody else needs to see.

Input parameters:

- `items` (array, required): The items, as text or objects, e.g. ["Book the van", {"text": "Pack the kitchen", "section": "Kitchen", "assignee": "Sam", "due": "2026-11-20"}].
- `note` (string): Optional note shown at the top of the page, e.g. Tick an item when it is done.
- `time_zone` (string, required): IANA time zone of the group (Area/City, not an abbreviation like EST), used for due dates and tick times, e.g. Europe/London or America/Chicago.
- `title` (string): Name of the checklist, e.g. Moving day, Flat 4B.

Output parameters:

- `by_assignee` (array)
- `by_assignee_count` (object)
- `by_section` (array)
- `by_section_count` (object)
- `changes` (array)
- `closed` (boolean)
- `done` (number)
- `due_today` (array)
- `due_today_count` (number)
- `due_today_shown` (object)
- `ended` (boolean)
- `expires_at` (string)
- `full` (boolean)
- `manage_url` (string)
- `open_count` (number)
- `open_items` (array)
- `open_items_count` (object)
- `overdue` (array)
- `overdue_count` (number)
- `overdue_shown` (object)
- `percent_done` (number)
- `public_url` (string)
- `recent` (array)
- `time_zone` (string)
- `title` (string)
- `today` (string)
- `total` (number)

### `show_checklist_results` (~133 tokens)

Show checklist progress

Use this when the organizer asks how far along a shared checklist is, what is overdue, who did what, or what is left, for a checklist made with create_shared_checklist. Takes the private organizer link and returns progress by section and by person, overdue and due-today items in the checklist's time zone, open items and recent ticks. Does not change the checklist. Do not use without the organizer link.

Input parameters:

- `manage_link` (string, required): The private organizer link returned when the checklist was created, e.g. https://shared-checklist.zovo.one/m/AbC.../XyZ...

Output parameters:

- `by_assignee` (array)
- `by_assignee_count` (object)
- `by_section` (array)
- `by_section_count` (object)
- `changes` (array)
- `closed` (boolean)
- `done` (number)
- `due_today` (array)
- `due_today_count` (number)
- `due_today_shown` (object)
- `ended` (boolean)
- `expires_at` (string)
- `full` (boolean)
- `manage_url` (string)
- `open_count` (number)
- `open_items` (array)
- `open_items_count` (object)
- `overdue` (array)
- `overdue_count` (number)
- `overdue_shown` (object)
- `percent_done` (number)
- `public_url` (string)
- `recent` (array)
- `time_zone` (string)
- `title` (string)
- `today` (string)
- `total` (number)

### `update_shared_checklist` (~318 tokens)

Change, tick or close a checklist

Use this when the organizer wants to add items, change an item's text, section, assignee or due date, remove items, tick or untick items by number, rename the list, change the note, or close or reopen the page. Takes the private organizer link. Removing an item also removes its tick history. Does not send messages to anyone.

Input parameters:

- `add_items` (array): New items, e.g. ["Buy tape", {"text": "Return keys", "due": "2026-11-30"}].
- `done_by` (string): Name shown for ticks made from the chat, e.g. Priya. Default Organizer.
- `edit_items` (array): Changes to existing items, by number.
- `manage_link` (string, required): The private organizer link returned when the checklist was created, e.g. https://shared-checklist.zovo.one/m/AbC.../XyZ...
- `mark_done` (array): Numbers of items to tick as done, e.g. [1, 2].
- `mark_not_done` (array): Numbers of items to untick, e.g. [5].
- `note` (string): New note shown on the page; empty text removes it.
- `remove_items` (array): Numbers of items to remove, e.g. [4, 7].
- `status` (string): closed stops ticking (the list stays visible); open allows it again.
- `title` (string): New title, e.g. Moving day (final).

Output parameters:

- `by_assignee` (array)
- `by_assignee_count` (object)
- `by_section` (array)
- `by_section_count` (object)
- `changes` (array)
- `closed` (boolean)
- `done` (number)
- `due_today` (array)
- `due_today_count` (number)
- `due_today_shown` (object)
- `ended` (boolean)
- `expires_at` (string)
- `full` (boolean)
- `manage_url` (string)
- `open_count` (number)
- `open_items` (array)
- `open_items_count` (object)
- `overdue` (array)
- `overdue_count` (number)
- `overdue_shown` (object)
- `percent_done` (number)
- `public_url` (string)
- `recent` (array)
- `time_zone` (string)
- `title` (string)
- `today` (string)
- `total` (number)

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69
- 2026-11-12: 69
- 2026-11-11: 68
- 2026-11-10: 68
- 2026-11-09: 67
- 2026-11-08: 67

## Common questions

### What is the Zovo Shared Checklist MCP server?

Zovo Shared Checklist is an MCP server listed in the public MCP registry as io.github.theluckystrike/shared-checklist. Make one checklist page that your whole group works through: moving house, wedding prep. This page covers its hosted endpoint (https://shared-checklist.zovo.one/mcp).

### Is the Zovo Shared Checklist MCP server safe to use?

Zovo Shared Checklist scores 73 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 Shared Checklist MCP server expose?

Zovo Shared Checklist exposes 3 tools: create_shared_checklist, show_checklist_results, update_shared_checklist. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

### Does the Zovo Shared Checklist MCP server require authentication?

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

### Is the Zovo Shared Checklist MCP server still maintained?

Zovo Shared Checklist 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 Shared Checklist MCP server?

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