Zovo Shared Checklist
REMOTE · SHARED-CHECKLIST.ZOVO.ONE
Make one checklist page that your whole group works through: moving house, wedding prep.
Available components
Last scanned (12 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_shared_checklist). See how to fix → View diagnostics → Fail
- 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 Usability75
- 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 832 tokens (~208/item across 4 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 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 67
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://shared-checklist.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 shared-checklist.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://shared-checklist.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://shared-checklist.zovo.one/mcp | HTTPS enforced | 301 | https://shared-checklist.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 →
create_shared_checklist Create a shared checklist page ~296
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_assignee | array | yes | – |
| by_assignee_count | object | – | – |
| by_section | array | yes | – |
| by_section_count | object | – | – |
| changes | array | – | – |
| closed | boolean | yes | – |
| done | number | yes | – |
| due_today | array | yes | – |
| due_today_count | number | – | – |
| due_today_shown | object | – | – |
| ended | boolean | yes | – |
| expires_at | string | yes | – |
| full | boolean | – | – |
| manage_url | string | yes | – |
| open_count | number | yes | – |
| open_items | array | yes | – |
| open_items_count | object | – | – |
| overdue | array | yes | – |
| overdue_count | number | yes | – |
| overdue_shown | object | – | – |
| percent_done | number | yes | – |
| public_url | string | yes | – |
| recent | array | yes | – |
| time_zone | string | yes | – |
| title | string | yes | – |
| today | string | yes | – |
| total | number | yes | – |
No examples provided.
show_checklist_results Show checklist progress ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manage_link | string | yes | The private organizer link returned when the checklist was created, e.g. https://shared-checklist.zovo.one/m/AbC.../XyZ... |
| Name | Type | Req | Description |
|---|---|---|---|
| by_assignee | array | yes | – |
| by_assignee_count | object | – | – |
| by_section | array | yes | – |
| by_section_count | object | – | – |
| changes | array | – | – |
| closed | boolean | yes | – |
| done | number | yes | – |
| due_today | array | yes | – |
| due_today_count | number | – | – |
| due_today_shown | object | – | – |
| ended | boolean | yes | – |
| expires_at | string | yes | – |
| full | boolean | – | – |
| manage_url | string | yes | – |
| open_count | number | yes | – |
| open_items | array | yes | – |
| open_items_count | object | – | – |
| overdue | array | yes | – |
| overdue_count | number | yes | – |
| overdue_shown | object | – | – |
| percent_done | number | yes | – |
| public_url | string | yes | – |
| recent | array | yes | – |
| time_zone | string | yes | – |
| title | string | yes | – |
| today | string | yes | – |
| total | number | yes | – |
No examples provided.
update_shared_checklist Change, tick or close a checklist ~318
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| by_assignee | array | yes | – |
| by_assignee_count | object | – | – |
| by_section | array | yes | – |
| by_section_count | object | – | – |
| changes | array | – | – |
| closed | boolean | yes | – |
| done | number | yes | – |
| due_today | array | yes | – |
| due_today_count | number | – | – |
| due_today_shown | object | – | – |
| ended | boolean | yes | – |
| expires_at | string | yes | – |
| full | boolean | – | – |
| manage_url | string | yes | – |
| open_count | number | yes | – |
| open_items | array | yes | – |
| open_items_count | object | – | – |
| overdue | array | yes | – |
| overdue_count | number | yes | – |
| overdue_shown | object | – | – |
| percent_done | number | yes | – |
| public_url | string | yes | – |
| recent | array | yes | – |
| time_zone | string | yes | – |
| title | string | yes | – |
| today | string | yes | – |
| total | number | yes | – |
No examples provided.
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.
remote · shared-checklist.zovo.one
claude mcp add --transport http theluckystrike-shared-checklist 'https://shared-checklist.zovo.one/mcp'
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.