Onboarding Checklist Inspection Runs is answering right now. Last checked 4 min ago. It exposes 16 tools. Last commit 6 Nov 2026.
Onboarding and inspection checklists you reuse: dated runs, who ticked what, and a sign-off.
Uptime history
46 days of history · worst day 94%
46 days agonow
100.0%
Uptime 24h
92 of 92 checks
16
Tools
read from the server
173 ms
Response time
average over 24h
2
Stars
last commit 6 Nov 2026
What changed 31
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.
6 Nov
15 tools changed the parameters they ask for30 times that day
checklist_create, checklist_delete, checklist_item_add and 12 more
15 Oct
a tool changed version
and 15 more, back to 15 October 2026
What the code does
We read the source, 3 h ago · tools taken from the live server · rules 995398eba69f
Capabilities
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
Hidden recipient in outgoing message
billing/src/index.js:1340
reply_to: "[email protected]" }),
Touches key and credential files
data/npm_unblock.json:34
"confound": "actions/setup-node with registry-url wrote NPM_CONFIG_USERCONFIG=$RUNNER_TEMP/.npmrc containing //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}; with no NODE_AUTH_TOKEN secret this expanded to the literal placeholder XXXXX-XXXXX-XXXXX-XXXXX, so npm authen…
Page loads a third-party script
telegram/public/index.html:11
<script src="https://telegram.org/js/telegram-web-app.js"></script>
Sends data to a third-party sink
telegram/src/bot.ts:205
console.error("Bot started; polling https://api.telegram.org");
Dumps the whole environment
servers/office-suite/src/index.ts:141
for (const [k, v] of Object.entries(process.env)) if (v !== undefined) env[k] = v;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.
run in your terminal
claude mcp add onboarding-checklist-inspection-runs --transport http https://mcp.zovo.one/mcp/onboarding-checklist-inspection-runsSettings → Connectors → Add custom connector, then paste this address
https://mcp.zovo.one/mcp/onboarding-checklist-inspection-runs~/.codex/config.toml
[mcp_servers.onboarding-checklist-inspection-runs]
url = "https://mcp.zovo.one/mcp/onboarding-checklist-inspection-runs".cursor/mcp.json
{
"mcpServers": {
"onboarding-checklist-inspection-runs": {
"url": "https://mcp.zovo.one/mcp/onboarding-checklist-inspection-runs"
}
}
}.vscode/mcp.json
{
"servers": {
"onboarding-checklist-inspection-runs": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/onboarding-checklist-inspection-runs"
}
}
}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/onboarding-checklist-inspection-runs | streamable-http | answering | 84 ms | 4 min ago |
Alternatives to Onboarding Checklist Inspection Runs
same job, measured the same wayOnboarding Goods Receipt Inspection Runs
by theluckystrike
Onboarding and inspection goods-receipts you reuse: dated runs, who ticked what, and a sign-off.
McpStamp Checklists
by theluckystrike
Reusable checklists with dated runs: pass, fail or N/A per step, then a frozen sign-off.
craaft
by craaft
Read and update your craaft kanban boards: add and move cards, comment, and tick off checklists.
McpStamp Purchase Requisitions
by theluckystrike
Purchase requisitions as reusable step lists: dated runs, pass or fail per step, and sign-off.
Usertour MCP Server
by usertour
Official Usertour MCP Server for in-app onboarding: flows, checklists, surveys, and analytics.
Purchase Requisition
by theluckystrike
Reusable purchase-requisitions and dated runs of them: pass, fail, not applicable, and a sign-off.
New Hire Onboarding Tasks
by theluckystrike
New-hire onboarding: role-based task templates, day-one to day-ninety checklists, completion.
CheckedCare
by checkedcare
Official state child care licensing and inspection records, verbatim and cited. Never graded.
Onboarding Checklist Inspection Runs — questions
Answers built from our own checks of this server.
What can Onboarding Checklist Inspection Runs 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 Onboarding Checklist Inspection Runs 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 Onboarding Checklist Inspection Runs working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 173 ms. The bar chart above shows every period we have measured.
How do I connect Onboarding Checklist Inspection Runs?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Onboarding Checklist Inspection Runs need an API key?
No. Onboarding Checklist Inspection Runs 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 Onboarding Checklist Inspection Runs?
It answers our handshake in 173 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Onboarding Checklist Inspection Runs open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 2 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.