# io.github.theluckystrike/checklist (remote · mcp.zovo.one)

Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-checklist/mcp-checklist.md), [page](https://verifymcp.io/servers/theluckystrike-checklist/mcp-checklist)
- mcpb · `checklist.mcpb`: 48/100, [markdown](https://verifymcp.io/servers/theluckystrike-checklist/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-checklist.md), [page](https://verifymcp.io/servers/theluckystrike-checklist/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-checklist)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/checklist`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.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-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 17 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.

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "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.

## 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-09-19 (score 79, +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-09-18 (score 78, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 78)

First indexed and scored.

## MCP tools (16)

### `checklist_create` (~132 tokens)

Create a checklist

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.

Input parameters:

- `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, required): What the checklist is, e.g. Pre-delivery vehicle check or Site handover

### `checklist_item_add` (~212 tokens)

Add a step to a checklist

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.

Input parameters:

- `checklist` (string, required): 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, required): The step, as the person doing it will read it, e.g. Tyre pressures checked and recorded

### `checklist_item_remove` (~96 tokens)

Remove a step from a checklist

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.

Input parameters:

- `checklist` (string, required): The checklist id, e.g. CL-0001, or its name when only one carries it
- `item` (string, required): The step id, e.g. I03, as shown by checklist_show

### `checklist_show` (~102 tokens)

Show one checklist

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.

Input parameters:

- `as_text` (boolean): Return a blank printable copy as plain text as well as the structured view. Default false
- `checklist` (string, required): The checklist id, e.g. CL-0001, or its name when only one carries it

### `checklist_list` (~96 tokens)

List checklists

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.

Input parameters:

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

### `checklist_delete` (~97 tokens)

Delete a checklist

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.

Input parameters:

- `checklist` (string, required): The checklist id, e.g. CL-0001, or its name when only one carries it
- `confirm` (boolean, required): Must be true. There is no undo and nothing is copied anywhere first

### `run_start` (~170 tokens)

Start a run of a checklist

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.

Input parameters:

- `checklist` (string, required): 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, required): What this run is against, e.g. Van BX21 KLM, February service

### `run_check` (~202 tokens)

Answer a step in a run

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.

Input parameters:

- `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, required): 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, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it
- `state` (string, required): pass, fail, na for did not apply, or pending to put the step back to unanswered

### `run_show` (~83 tokens)

Show one run

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.

Input parameters:

- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `run_list` (~139 tokens)

List runs

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.

Input parameters:

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

### `run_sign_off` (~169 tokens)

Sign off a run

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.

Input parameters:

- `by` (string, required): 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, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `run_status` (~142 tokens)

Reopen or abandon a run

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.

Input parameters:

- `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, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it
- `status` (string, required): open puts a complete run back into edit; abandoned closes it without a signature

### `run_report` (~177 tokens)

Produce the run report

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.

Input parameters:

- `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, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `run_delete` (~105 tokens)

Delete a run

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.

Input parameters:

- `confirm` (boolean, required): Must be true. There is no undo and nothing is copied anywhere first
- `run` (string, required): The run id, e.g. RUN-2026-0001, or its title when only one carries it

### `license_status` (~55 tokens)

License status

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.

### `license_activate` (~76 tokens)

Activate license

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.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

## Diagnostics

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

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78

## Common questions

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

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/checklist
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/checklist
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/checklist
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-checklist/mcp-checklist.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-checklist/mcp-checklist.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-checklist/mcp-checklist