Checklist is answering right now. Last checked 13 min ago. It exposes 16 tools. Last commit 18 Sep 2026.
Reusable checklists and dated runs of them: pass, fail, not applicable, and a sign-off.
Uptime history
21 hours of history
21 hours agonow
100.0%
Uptime 24h
77 of 77 checks
16
Tools
read from the server
277 ms
Response time
average over 24h
0
Stars
last commit 18 Sep 2026
Nothing serious here today
Today is the operative word: we check Checklist every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
run in your terminal
claude mcp add checklist --transport http https://mcp.zovo.one/mcp/checklist~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"checklist": {
"url": "https://mcp.zovo.one/mcp/checklist"
}
}
}~/.codex/config.toml
[mcp_servers.checklist]
url = "https://mcp.zovo.one/mcp/checklist".cursor/mcp.json
{
"mcpServers": {
"checklist": {
"url": "https://mcp.zovo.one/mcp/checklist"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"checklist": {
"url": "https://mcp.zovo.one/mcp/checklist"
}
}
}Available tools 16
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
checklist
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_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 signed.
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 one does not.
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_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_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.
run
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 answer stands.
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.
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.
license
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_status confirms it.
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.
report
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.
show
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.
sign
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 print on the report.
start
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 capped.
status
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zovo.one/mcp/checklist | streamable-http | answering | 45 ms | 13 min ago |
Alternatives to Checklist
same job, measured the same wayOnboarding Checklist Inspection Runs
by theluckystrike
Onboarding and inspection checklists you reuse: dated runs, who ticked what, and a sign-off.
Slack Lists MCP
by justadityaraj
Full read + write access to Slack Lists for AI: create, update, check off, reassign, delete.
Vue Harvest
by virgilvox
Extract reusable component libraries and design tokens from Vue applications
ScreenVerity
by williamblakecunningham-max
Free U.S. exclusion, debarment and licence screening with a signed receipt of the lists checked.
Analytics
by mcpanalytics
The statistical analyst in your AI chat — validated, citable, re-runnable analysis of your data.
APISign
by apisign
Send documents for legally binding e-signature and manage the reusable templates behind them.
Site
by caspchecklist
CASP Checklist: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
Interpol
by mcp-dir
Checks whether a name is on Interpol notices, from the name, surname, and date of birth, for complia
Checklist — questions
Answers built from our own checks of this server.
What can Checklist do?
It exposes 16 tools, read directly from the server on our last check. Among them: checklist_create, checklist_delete, checklist_item_add, checklist_item_remove, checklist_list, checklist_show and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Checklist mostly used for?
Its tools cluster around checklist, run and license. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Checklist working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 77 of 77 checks got a reply (100.0%), average response time 277 ms. The bar chart above shows every period we have measured.
How do I connect Checklist?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Checklist need an API key?
No. Checklist completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Checklist?
It answers our handshake in 277 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Checklist open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.