io.github.theluckystrike/kanban-todo-tasks-projects-board
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 20
A local task board per project: columns, due dates, estimates, priorities, overdue, weekly review.
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 Usability88
- 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
- Tool/resource definitions use about 1652 tokens (~86/item across 19 items; 17 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "task_delete" implies "delete" 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 18 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/kanban-todo-tasks-projects-board MCP server?
io.github.theluckystrike/kanban-todo-tasks-projects-board is a hosted endpoint at https://mcp.zovo.one/mcp/kanban, 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-kanban-todo-tasks-projects-board 'https://mcp.zovo.one/mcp/kanban'
{
"mcpServers": {
"theluckystrike-kanban-todo-tasks-projects-board": {
"url": "https://mcp.zovo.one/mcp/kanban"
}
}
} {
"servers": {
"theluckystrike-kanban-todo-tasks-projects-board": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/kanban"
}
}
} [mcp_servers.theluckystrike-kanban-todo-tasks-projects-board] url = "https://mcp.zovo.one/mcp/kanban"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-kanban-todo-tasks-projects-board": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/kanban",
"enabled": true
}
}
} openclaw mcp add theluckystrike-kanban-todo-tasks-projects-board --url 'https://mcp.zovo.one/mcp/kanban' --transport streamable-http
mcp_servers:
theluckystrike-kanban-todo-tasks-projects-board:
url: "https://mcp.zovo.one/mcp/kanban" {
"McpServers": {
"theluckystrike-kanban-todo-tasks-projects-board": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/kanban"
}
}
} assistant mcp add theluckystrike-kanban-todo-tasks-projects-board -t streamable-http -u 'https://mcp.zovo.one/mcp/kanban'
{
"mcpServers": {
"theluckystrike-kanban-todo-tasks-projects-board": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/kanban"
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Server version: 0.21.0 → 0.22.0 functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- Tool “license_activate” rewrote its description, which is the text the model reads security
- New prompt “upgrade_to_pro” functional
- New resource “pricing” functional
- 10 Sept 26 0
- Tool “task_log_time” rewrote its description, which is the text the model reads security
- Tool “project_list” rewrote its description, which is the text the model reads security
- Tool “task_move” rewrote its description, which is the text the model reads security
- Tool “project_delete” rewrote its description, which is the text the model reads security
- Tool “overdue” rewrote its description, which is the text the model reads security
- Tool “license_status” rewrote its description, which is the text the model reads security
- Tool “license_activate” rewrote its description, which is the text the model reads security
- Tool “columns_set” rewrote its description, which is the text the model reads security
- Tool “board” rewrote its description, which is the text the model reads security
- Tool “task_search” rewrote its description, which is the text the model reads security
- Tool “task_start_timer” rewrote its description, which is the text the model reads security
- Tool “task_update” rewrote its description, which is the text the model reads security
- Tool “task_delete” rewrote its description, which is the text the model reads security
- Tool “weekly_review” rewrote its description, which is the text the model reads security
- Tool “task_add” rewrote its description, which is the text the model reads security
- Tool “task_done” rewrote its description, which is the text the model reads security
- Tool “task_list” rewrote its description, which is the text the model reads security
- Schema quality: 63 → 88 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- “license_activate” reworded the description of “key” cosmetic
- 9 Sept 26 +42
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 88 functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: pass functional
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/kanban
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/kanban | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/kanban | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/kanban |
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 →
board Show board ~63
Show one board column by column: tasks, estimate, actual and overdue count in each, then the board totals and the estimate still open. Defaults to your busiest board. Use project_list for every board.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Which board; defaults to your busiest one |
No output schema declared.
No examples provided.
columns_set Set board columns ~96
Replace one board's columns, in order, with 2 to 12 unique names. Tasks in a removed column move to the FIRST column. Blanks are dropped first, so a list normalising below two names is refused. Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | The new column names in order, at most 12, e.g. ['inbox','next','doing','done'] |
| project | string | yes | Which board |
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.
overdue Overdue tasks ~94
List every task whose due day is already past, across all boards, oldest first, in the task_list table. as_of measures against a day you name. A finished task, or one with no due date, never counts.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Measure against this day instead of today (YYYY-MM-DD, 'next Monday', '+7d') |
| limit | integer | – | Rows to print; default 200 |
No output schema declared.
No examples provided.
project_delete Delete project board ~77
Delete an empty board and give its free-tier slot back. A board still holding tasks, open or done, is refused with one named, because task_add creates boards as a side effect and the work would be lost.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Board to remove, e.g. 'Nova Site'. It must hold no tasks at all. |
No output schema declared.
No examples provided.
project_list List projects ~52
List every board with its task-id prefix, open and done counts, estimate still open and overdue count, plus free-tier use (3 boards, 200 open tasks). Use board for one board broken down by column.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
task_add Add task ~221
Add one task to a board and return its id, board and column. The board is created on first use, so pass an existing project or leave it out. An identical open task is refused. Free: 3 boards, 200 open.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | – | Column to start in; defaults to the first column (backlog) |
| due | string | – | Due date: YYYY-MM-DD, 'today', 'tomorrow', 'Friday', 'next Monday' or '+3d' |
| estimate_minutes | integer | – | How long you think it will take, in minutes |
| notes | string | – | Longer notes for the task |
| priority | string | – | Priority; defaults to normal |
| project | string | – | Project or board name. A partial name matching exactly one existing project is used as that project. Defaults to your only board. |
| tags | array | – | Free-form tags, e.g. ['writing','client'] |
| title | string | yes | What the task is, e.g. 'Write the launch email' |
No output schema declared.
No examples provided.
task_delete Delete task ~67
Delete one task by id, permanently; the id is never reused. The answer names any logged minutes lost. time-tracker entries are a separate store and are untouched. Use task_done to keep the record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id, e.g. NOVA-12 |
No output schema declared.
No examples provided.
task_done Complete task ~67
Mark one task finished: it moves to the board's done column (named done, else the last) and is stamped, leaving task_list and the open counts. Returns estimate against actual when both are known.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id, e.g. NOVA-12 |
No output schema declared.
No examples provided.
task_list List tasks ~165
List tasks as a table of id, project, column, title, priority, due, estimate, actual and tags, sorted by due date, with the total estimate. Done tasks are left out unless include_done. 200 rows default.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | – | Only this column, e.g. 'doing' |
| due_before | string | – | Only tasks due on or before this day (YYYY-MM-DD, 'today', 'Friday', '+7d') |
| include_done | boolean | – | Include finished tasks; default false |
| limit | integer | – | Rows to print; default 200 |
| overdue | boolean | – | Only tasks past their due date |
| project | string | – | Only this project |
| tag | string | – | Only tasks carrying this tag |
No output schema declared.
No examples provided.
task_log_time Log time on a task ~90
Add real minutes worked to one task so estimate and actual can be compared. Minutes ADD; a negative corrects an over-count. Below zero or past 100,000 is refused. This counter is the board's own.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id, e.g. NOVA-12 |
| minutes | integer | yes | Minutes to add; a negative number corrects an over-count |
No output schema declared.
No examples provided.
task_move Move task ~82
Move one task to another column of its own board and report the old and new column. An unknown column is refused, listing the real ones. Entering the done column stamps completion; leaving it clears it.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | yes | Target column, e.g. 'doing' |
| id | string | yes | Task id, e.g. NOVA-12 |
No output schema declared.
No examples provided.
task_search Search tasks ~72
Find tasks whose id, title, notes or tags contain the query, across every board, finished ones included. Plain case-insensitive substring, never a regex. Use task_list for structured filters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows to print; default 200 |
| query | string | yes | Text to look for |
No output schema declared.
No examples provided.
task_start_timer Start a timer for a task ~70
Return the exact arguments to pass to the time-tracker's timer_start for one task, and record the link here. It starts nothing itself, and warns when the tracker's own project names would misfile the time.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task id, e.g. NOVA-12 |
No output schema declared.
No examples provided.
task_update Update task ~155
Change a task by id: only the fields you pass are touched. tags REPLACES the whole list, due 'none' clears it, and project moves the task to a board that already exists. Returns the task's new row.
| Name | Type | Req | Description |
|---|---|---|---|
| column | string | – | – |
| due | string | – | New due date, or 'none' to clear it |
| estimate_minutes | integer | – | – |
| id | string | yes | Task id, e.g. NOVA-12 |
| notes | string | – | – |
| priority | string | – | – |
| project | string | – | Move the task to another existing project board |
| tags | array | – | Replaces the whole tag list |
| title | string | – | – |
No output schema declared.
No examples provided.
weekly_review Weekly review ~80
Compare done against planned for one ISO week per project: how many were due, how many of those are finished, how many were completed, and estimate against actual minutes. Any week but this one is Pro.
| Name | Type | Req | Description |
|---|---|---|---|
| week | string | – | ISO week, e.g. '2026-W36'. Defaults to this week. Past weeks are a Pro feature. |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/kanban-todo-tasks-projects-board MCP server?
io.github.theluckystrike/kanban-todo-tasks-projects-board is an MCP server listed in the public MCP registry as io.github.theluckystrike/kanban-todo-tasks-projects-board. A local task board per project: columns, due dates, estimates, priorities, overdue, weekly review. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/kanban).
Is the io.github.theluckystrike/kanban-todo-tasks-projects-board MCP server safe to use?
io.github.theluckystrike/kanban-todo-tasks-projects-board scores 83 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/kanban-todo-tasks-projects-board MCP server expose?
io.github.theluckystrike/kanban-todo-tasks-projects-board exposes 17 tools: license_status, license_activate, task_add, task_list, task_move, and 12 more. Their descriptions and schemas cost roughly 1,582 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/kanban-todo-tasks-projects-board MCP server require authentication?
Yes. io.github.theluckystrike/kanban-todo-tasks-projects-board 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/kanban-todo-tasks-projects-board MCP server still maintained?
io.github.theluckystrike/kanban-todo-tasks-projects-board 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.