# io.github.theluckystrike/kanban-todo-tasks-projects-board (remote · mcp.zovo.one)

A local task board per project: columns, due dates, estimates, priorities, overdue, weekly review.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

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

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/kanban`
- 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**: 88/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).
  - Tool/resource definitions use about 1652 tokens (~86/item across 19 items; 17 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% 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 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.
  - An AI judge read all 18 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/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.

### Claude

```bash
claude mcp add --transport http theluckystrike-kanban-todo-tasks-projects-board 'https://mcp.zovo.one/mcp/kanban'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-kanban-todo-tasks-projects-board": {
      "url": "https://mcp.zovo.one/mcp/kanban"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-kanban-todo-tasks-projects-board": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/kanban"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-kanban-todo-tasks-projects-board]
url = "https://mcp.zovo.one/mcp/kanban"
```

### opencode

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

```bash
openclaw mcp add theluckystrike-kanban-todo-tasks-projects-board --url 'https://mcp.zovo.one/mcp/kanban' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-kanban-todo-tasks-projects-board:
    url: "https://mcp.zovo.one/mcp/kanban"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-kanban-todo-tasks-projects-board": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/kanban"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-kanban-todo-tasks-projects-board -t streamable-http -u 'https://mcp.zovo.one/mcp/kanban'
```

### Other

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

## 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-20 (score 83, +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.

### 2026-09-18 (score 82, +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.

### 2026-09-17 (score 81, 0)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-16 (score 81, +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.

### 2026-09-14 (score 80, +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.

### 2026-09-11 (score 79, +1)

- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 78, 0)

- [security] 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
- [functional regression] Schema quality: 63 → 88
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 78, +42)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] 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

## MCP tools (17)

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

### `task_add` (~221 tokens)

Add task

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.

Input parameters:

- `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, required): What the task is, e.g. 'Write the launch email'

### `task_list` (~165 tokens)

List tasks

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.

Input parameters:

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

### `task_move` (~82 tokens)

Move task

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.

Input parameters:

- `column` (string, required): Target column, e.g. 'doing'
- `id` (string, required): Task id, e.g. NOVA-12

### `task_update` (~155 tokens)

Update task

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.

Input parameters:

- `column` (string)
- `due` (string): New due date, or 'none' to clear it
- `estimate_minutes` (integer)
- `id` (string, required): 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)

### `task_done` (~67 tokens)

Complete task

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.

Input parameters:

- `id` (string, required): Task id, e.g. NOVA-12

### `task_delete` (~67 tokens)

Delete task

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.

Input parameters:

- `id` (string, required): Task id, e.g. NOVA-12

### `task_search` (~72 tokens)

Search tasks

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.

Input parameters:

- `limit` (integer): Rows to print; default 200
- `query` (string, required): Text to look for

### `board` (~63 tokens)

Show board

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.

Input parameters:

- `project` (string): Which board; defaults to your busiest one

### `task_start_timer` (~70 tokens)

Start a timer for a task

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.

Input parameters:

- `id` (string, required): Task id, e.g. NOVA-12

### `task_log_time` (~90 tokens)

Log time on a task

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.

Input parameters:

- `id` (string, required): Task id, e.g. NOVA-12
- `minutes` (integer, required): Minutes to add; a negative number corrects an over-count

### `project_list` (~52 tokens)

List projects

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.

### `project_delete` (~77 tokens)

Delete project board

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.

Input parameters:

- `project` (string, required): Board to remove, e.g. 'Nova Site'. It must hold no tasks at all.

### `overdue` (~94 tokens)

Overdue tasks

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.

Input parameters:

- `as_of` (string): Measure against this day instead of today (YYYY-MM-DD, 'next Monday', '+7d')
- `limit` (integer): Rows to print; default 200

### `weekly_review` (~80 tokens)

Weekly review

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.

Input parameters:

- `week` (string): ISO week, e.g. '2026-W36'. Defaults to this week. Past weeks are a Pro feature.

### `columns_set` (~96 tokens)

Set board columns

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.

Input parameters:

- `columns` (array, required): The new column names in order, at most 12, e.g. ['inbox','next','doing','done']
- `project` (string, required): Which board

## Diagnostics

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

## Score history

- 2026-09-20: 83
- 2026-09-19: 82
- 2026-09-18: 82
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36

## Common questions

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

## Links

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