Skip to content
Back to search
100
MCP live MCP 2025-11-25 streamable-http

io.github.theluckystrike/checklist

io.github.theluckystrike/checklist

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

Watch this dependency Share evidence report
Uptime
100.0%
4 direct probes · 30d
Response
1071ms
last probe
Tools
16
callable
Resources
2
readable
Prompts
2
available
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
16 tools, 2 resources, 2 prompts returned.
pass 3 or more catalogue items 10/10
20 items in total; 3 or more earns these points.
pass Describes itself 10/10
87 characters; more than 30 earns these points.

Tools · 16

checklist_create

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.

checklist_item_add

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 on…

checklist_item_remove

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.

checklist_show

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.

checklist_list

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.

checklist_delete

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 …

run_start

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 …

run_check

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 a…

run_show

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.

run_list

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.

run_sign_off

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 pri…

run_status

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.

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 val…

run_delete

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.

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 c…

license_activate

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_…

Resources · 2

contract

Why a run copies its checklist, the four item states and what na means, the run status machine, what blocks a sign-off, the free-tier limits and the one document this server writes.

checklist://contract
pricing

What checklist costs, what Pro unlocks, the checkout link that carries this connection's token, and the one step a person has to take. Machine-readable; read it before telling a user how to lift a fre…

pricing://checklist

Prompts · 2

run_the_checklist

Pick or build the checklist, start a dated run against a job, answer every step with who and when, and sign it off with the exceptions on the record.

upgrade_to_pro

Explain what Pro on the checklist server costs and exactly what the user has to do, without leaving the conversation.

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://mcp.zovo.one/mcp/checklist

Cursor or Cline: add to your MCP config:

{
  "mcpServers": {
    "io.github.theluckystrike/checklist": {
      "url": "https://mcp.zovo.one/mcp/checklist",
      "transport": "streamable-http"
    }
  }
}