io.github.theluckystrike/checklist
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. 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 Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2146 tokens (~119/item across 18 items; 16 tools + 2 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "checklist_item_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 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
How do I install the io.github.theluckystrike/checklist MCP server?
io.github.theluckystrike/checklist is a hosted endpoint at https://mcp.zovo.one/mcp/checklist, 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 · mcp.zovo.one
claude mcp add --transport http theluckystrike-checklist 'https://mcp.zovo.one/mcp/checklist'
{
"mcpServers": {
"theluckystrike-checklist": {
"url": "https://mcp.zovo.one/mcp/checklist"
}
}
} {
"servers": {
"theluckystrike-checklist": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/checklist"
}
}
} [mcp_servers.theluckystrike-checklist] url = "https://mcp.zovo.one/mcp/checklist"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-checklist": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/checklist",
"enabled": true
}
}
} openclaw mcp add theluckystrike-checklist --url 'https://mcp.zovo.one/mcp/checklist' --transport streamable-http
mcp_servers:
theluckystrike-checklist:
url: "https://mcp.zovo.one/mcp/checklist" {
"McpServers": {
"theluckystrike-checklist": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/checklist"
}
}
} assistant mcp add theluckystrike-checklist -t streamable-http -u 'https://mcp.zovo.one/mcp/checklist'
{
"mcpServers": {
"theluckystrike-checklist": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/checklist"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 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.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 78
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 20 Sept 2026 · Probed https://mcp.zovo.one/mcp/checklist
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 | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.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 mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token"
Bearer realm="mcp.zovo.one", error="invalid_token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/checklist | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/checklist | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/checklist |
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 →
checklist_create Create a checklist ~132
Create a reusable checklist and return its CL-NNNN id: a name, a category and an optional description. Add the steps with checklist_item_add. Free tier: 3 checklists, and unlimited runs of them.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A grouping key, lower-cased and hyphenated, e.g. handover or safety. Default general |
| description | string | – | What this checklist is for and when to run it, printed at the top of a blank copy |
| name | string | yes | What the checklist is, e.g. Pre-delivery vehicle check or Site handover |
No output schema declared.
No examples provided.
checklist_delete Delete a checklist ~97
Delete a checklist and its steps for good. Runs already started from it are untouched and stay readable: a run carries its own copy of the steps, so deleting the checklist does not erase what anybody signed.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | string | yes | The checklist id, e.g. CL-0001, or its name when only one carries it |
| confirm | boolean | yes | Must be true. There is no undo and nothing is copied anywhere first |
No output schema declared.
No examples provided.
checklist_item_add Add a step to a checklist ~212
Add one step to a checklist and return its I01-style id: the text, an optional section heading, and whether it is required. A required step that is unanswered or failed blocks sign-off; an optional one does not.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | string | yes | The checklist id, e.g. CL-0001, or its name when only one carries it |
| note | string | – | Guidance printed under the step, e.g. the tolerance or the standard it is checked against |
| position | integer | – | Insert at this 1-based position instead of at the end. Existing steps keep their ids |
| required | boolean | – | Whether sign-off is blocked while this step is unanswered or failed. Default true |
| section | string | – | A heading to group this step under, e.g. Exterior. Steps keep the order they were added within a section |
| text | string | yes | The step, as the person doing it will read it, e.g. Tyre pressures checked and recorded |
No output schema declared.
No examples provided.
checklist_item_remove Remove a step from a checklist ~96
Remove one step from a checklist by its I01-style id and bump the checklist version. Runs already under way keep the step they started with, so nothing anybody already ticked is rewritten.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | string | yes | The checklist id, e.g. CL-0001, or its name when only one carries it |
| item | string | yes | The step id, e.g. I03, as shown by checklist_show |
No output schema declared.
No examples provided.
checklist_list List checklists ~96
Every checklist with its category, version, step count and how many runs came from it. Filter by category or by a word in the name. Returns at most 500 rows, newest change first.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only checklists in this category, matched after the same lower-case hyphenation applied on create |
| contains | string | – | Only checklists whose name contains this text, matched case-insensitively |
No output schema declared.
No examples provided.
checklist_show Show one checklist ~102
One checklist with its steps in order, grouped by section, plus how many are required and how many runs have been started from it. Pass as_text for a blank printable copy with a box against each step.
| Name | Type | Req | Description |
|---|---|---|---|
| as_text | boolean | – | Return a blank printable copy as plain text as well as the structured view. Default false |
| checklist | string | yes | The checklist id, e.g. CL-0001, or its name when only one carries it |
No output schema declared.
No examples provided.
license_activate Activate license ~76
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_check Answer a step in a run ~202
Mark one step pass, fail or na, with who did it and when. na means the step did not apply; it counts as answered and never as passed. A step can be answered again while the run is open, and the last answer stands.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | The day it was answered, YYYY-MM-DD. Default the run's own date |
| by | string | – | Who answered it. Printed against the step on the report |
| item | string | yes | The step id, e.g. I03, as shown by run_show |
| note | string | – | What was found. Say why on a fail: the report prints this under the step |
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
| state | string | yes | pass, fail, na for did not apply, or pending to put the step back to unanswered |
No output schema declared.
No examples provided.
run_delete Delete a run ~105
Delete a run for good, with every answer on it. A signed-off run is refused: it is the record of what somebody put their name to. Abandon a run you no longer want instead of deleting a signed one.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Must be true. There is no undo and nothing is copied anywhere first |
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_list List runs ~139
Runs newest first, with their checklist, progress and sign-off state. Filter by checklist, by status, by reference or to open runs only. Returns at most 500 rows.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | string | – | Only runs of this checklist, by id or name |
| open_only | boolean | – | Only open and complete runs, the ones still editable. Default false |
| reference | string | – | Only runs against this job, order or asset id, matched case-insensitively |
| status | string | – | Only runs in this status |
| with_failures | boolean | – | Only runs that have at least one failed step. Default false |
No output schema declared.
No examples provided.
run_report Produce the run report ~177
The run as plain text on every tier: every step with its mark, who answered it, the notes, the counts and a signature block or the recorded signature. Pro also gets it back as a .txt download link valid for one hour, named by out_path.
| Name | Type | Req | Description |
|---|---|---|---|
| out_path | string | – | Name for the downloaded .txt file, e.g. site-handover-run. Pro only. Omit to get the report back as text, which every tier can do; the file comes back as a download link valid for one hour |
| overwrite | boolean | – | Replace out_path if a file is already there. Default false, and an existing file is refused with nothing written |
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_show Show one run ~83
The whole run: every step with its answer, who answered it and when, grouped by section, plus the pass, fail and outstanding counts, the failures in full, and whether it can be signed off and why not.
| Name | Type | Req | Description |
|---|---|---|---|
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_sign_off Sign off a run ~169
Sign off a completed run with a name and a date, which freezes it. Refused while a required step is unanswered or failed, unless force is true, and either way the exceptions stay on the record and print on the report.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | yes | Who is signing it off, as it should read on the document |
| date | string | – | The day it was signed, YYYY-MM-DD. Default today |
| force | boolean | – | Sign off even though required steps are unanswered or failed. Default false; the reasons come back either way |
| note | string | – | What the signature covers, or the exception being accepted |
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
No output schema declared.
No examples provided.
run_start Start a run of a checklist ~170
Start a dated run of a checklist and return its RUN-YYYY-NNNN id. The steps are COPIED into the run, so editing the checklist afterwards never changes a run already under way. Runs are free and never capped.
| Name | Type | Req | Description |
|---|---|---|---|
| checklist | string | yes | The checklist id, e.g. CL-0001, or its name when only one carries it |
| date | string | – | The day the run happened, YYYY-MM-DD. Default today |
| note | string | – | – |
| reference | string | – | The job, order or asset id this run belongs to, e.g. WO-2026-0044. Named only; no sibling store is opened |
| title | string | yes | What this run is against, e.g. Van BX21 KLM, February service |
No output schema declared.
No examples provided.
run_status Reopen or abandon a run ~142
Move a run back to open so a step can be answered again, or abandon it when the job did not happen. A signed-off run is refused: a signature is the point at which a run stops moving.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The day the step happened, YYYY-MM-DD. Default today |
| note | string | – | Why. Kept on the run's history and printed nowhere else |
| run | string | yes | The run id, e.g. RUN-2026-0001, or its title when only one carries it |
| status | string | yes | open puts a complete run back into edit; abandoned closes it without a signature |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/checklist MCP server?
io.github.theluckystrike/checklist is an MCP server listed in the public MCP registry as io.github.theluckystrike/checklist. Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/checklist).
Is the io.github.theluckystrike/checklist MCP server safe to use?
io.github.theluckystrike/checklist 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 io.github.theluckystrike/checklist MCP server expose?
io.github.theluckystrike/checklist exposes 16 tools: checklist_create, checklist_item_add, checklist_item_remove, checklist_show, checklist_list, and 11 more. Their descriptions and schemas cost roughly 2,053 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/checklist MCP server require authentication?
Yes. io.github.theluckystrike/checklist asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.theluckystrike/checklist MCP server still maintained?
io.github.theluckystrike/checklist is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.