Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/task-board-todo-kanban

REMOTE · MCP.ZOVO.ONE · SCANNED SEP 30

A todo and task board in kanban form, driven from chat with full CRUD.

Available components

83 Trust /100
Trust breakdown (7 categories)

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 Security94
Transport & Reachability100
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 Management13
  • Stability observed for 4 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • 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
Install

How do I install the io.github.theluckystrike/task-board-todo-kanban MCP server?

io.github.theluckystrike/task-board-todo-kanban is a hosted endpoint at https://mcp.zovo.one/mcp/task-board-todo-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

# add to Claude Code
claude mcp add --transport http theluckystrike-task-board-todo-kanban 'https://mcp.zovo.one/mcp/task-board-todo-kanban'
// .cursor/mcp.json
{
  "mcpServers": {
    "theluckystrike-task-board-todo-kanban": {
      "url": "https://mcp.zovo.one/mcp/task-board-todo-kanban"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "theluckystrike-task-board-todo-kanban": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/task-board-todo-kanban"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.theluckystrike-task-board-todo-kanban]
url = "https://mcp.zovo.one/mcp/task-board-todo-kanban"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-task-board-todo-kanban": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/task-board-todo-kanban",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add theluckystrike-task-board-todo-kanban --url 'https://mcp.zovo.one/mcp/task-board-todo-kanban' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  theluckystrike-task-board-todo-kanban:
    url: "https://mcp.zovo.one/mcp/task-board-todo-kanban"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "theluckystrike-task-board-todo-kanban": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/task-board-todo-kanban"
    }
  }
}
# add to Vellum
assistant mcp add theluckystrike-task-board-todo-kanban -t streamable-http -u 'https://mcp.zovo.one/mcp/task-board-todo-kanban'
// mcp.json
{
  "mcpServers": {
    "theluckystrike-task-board-todo-kanban": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/task-board-todo-kanban"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Sept 26 81

    First indexed and scored.

Diagnostics

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 30 Sept 2026 · Probed https://mcp.zovo.one/mcp/task-board-todo-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 Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"

Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Protected resource metadata

Document https://mcp.zovo.one/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.zovo.one
Authorisation server https://mcp.zovo.one

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/task-board-todo-kanban Verified 200
http (plaintext) http://mcp.zovo.one/mcp/task-board-todo-kanban HTTPS enforced 301 https://mcp.zovo.one/mcp/task-board-todo-kanban
MCP tools · 17 exposed · ~1,582 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
projectstring–Which board; defaults to your busiest one

No output schema declared.

No examples provided.

columns_set ~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.

NameTypeReqDescription
columnsarrayyesThe new column names in order, at most 12, e.g. ['inbox','next','doing','done']
projectstringyesWhich board

No output schema declared.

No examples provided.

license_activate ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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

NameTypeReqDescription
as_ofstring–Measure against this day instead of today (YYYY-MM-DD, 'next Monday', '+7d')
limitinteger–Rows to print; default 200

No output schema declared.

No examples provided.

project_delete ~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.

NameTypeReqDescription
projectstringyesBoard to remove, e.g. 'Nova Site'. It must hold no tasks at all.

No output schema declared.

No examples provided.

project_list ~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 ~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.

NameTypeReqDescription
columnstring–Column to start in; defaults to the first column (backlog)
duestring–Due date: YYYY-MM-DD, 'today', 'tomorrow', 'Friday', 'next Monday' or '+3d'
estimate_minutesinteger–How long you think it will take, in minutes
notesstring–Longer notes for the task
prioritystring–Priority; defaults to normal
projectstring–Project or board name. A partial name matching exactly one existing project is used as that project. Defaults to your only board.
tagsarray–Free-form tags, e.g. ['writing','client']
titlestringyesWhat the task is, e.g. 'Write the launch email'

No output schema declared.

No examples provided.

task_delete ~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.

NameTypeReqDescription
idstringyesTask id, e.g. NOVA-12

No output schema declared.

No examples provided.

task_done ~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.

NameTypeReqDescription
idstringyesTask id, e.g. NOVA-12

No output schema declared.

No examples provided.

task_list ~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.

NameTypeReqDescription
columnstring–Only this column, e.g. 'doing'
due_beforestring–Only tasks due on or before this day (YYYY-MM-DD, 'today', 'Friday', '+7d')
include_doneboolean–Include finished tasks; default false
limitinteger–Rows to print; default 200
overdueboolean–Only tasks past their due date
projectstring–Only this project
tagstring–Only tasks carrying this tag

No output schema declared.

No examples provided.

task_log_time ~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.

NameTypeReqDescription
idstringyesTask id, e.g. NOVA-12
minutesintegeryesMinutes to add; a negative number corrects an over-count

No output schema declared.

No examples provided.

task_move ~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.

NameTypeReqDescription
columnstringyesTarget column, e.g. 'doing'
idstringyesTask id, e.g. NOVA-12

No output schema declared.

No examples provided.

task_search ~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.

NameTypeReqDescription
limitinteger–Rows to print; default 200
querystringyesText to look for

No output schema declared.

No examples provided.

task_start_timer ~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.

NameTypeReqDescription
idstringyesTask id, e.g. NOVA-12

No output schema declared.

No examples provided.

task_update ~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.

NameTypeReqDescription
columnstring––
duestring–New due date, or 'none' to clear it
estimate_minutesinteger––
idstringyesTask id, e.g. NOVA-12
notesstring––
prioritystring––
projectstring–Move the task to another existing project board
tagsarray–Replaces the whole tag list
titlestring––

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
weekstring–ISO week, e.g. '2026-W36'. Defaults to this week. Past weeks are a Pro feature.

No output schema declared.

No examples provided.

Common questions

What is the io.github.theluckystrike/task-board-todo-kanban MCP server?

io.github.theluckystrike/task-board-todo-kanban is an MCP server listed in the public MCP registry as io.github.theluckystrike/task-board-todo-kanban. A todo and task board in kanban form, driven from chat with full CRUD. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/task-board-todo-kanban).

Is the io.github.theluckystrike/task-board-todo-kanban MCP server safe to use?

io.github.theluckystrike/task-board-todo-kanban 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/task-board-todo-kanban MCP server expose?

io.github.theluckystrike/task-board-todo-kanban 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/task-board-todo-kanban MCP server require authentication?

Yes. io.github.theluckystrike/task-board-todo-kanban 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/task-board-todo-kanban MCP server still maintained?

io.github.theluckystrike/task-board-todo-kanban is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.