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/kanban-todo-tasks-projects-board

MCPB · KANBAN.MCPB · 2 COMPONENTS · SCANNED SEP 20

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

48 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security23
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 96 of 96 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 1595 tokens (~88/item across 18 items; 17 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

mcpb · kanban.mcpb

Download bundle
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.

  • 17 Sept 26 48

    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 20 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/kanban.mcpb@0.22.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~1,576 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
projectstringWhich 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 ~71

Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.

NameTypeReqDescription
keystringyesLicense key from the checkout confirmation page

No output schema declared.

No examples provided.

license_status ~54

Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.

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_ofstringMeasure against this day instead of today (YYYY-MM-DD, 'next Monday', '+7d')
limitintegerRows 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
columnstringColumn to start in; defaults to the first column (backlog)
duestringDue date: YYYY-MM-DD, 'today', 'tomorrow', 'Friday', 'next Monday' or '+3d'
estimate_minutesintegerHow long you think it will take, in minutes
notesstringLonger notes for the task
prioritystringPriority; defaults to normal
projectstringProject or board name. A partial name matching exactly one existing project is used as that project. Defaults to your only board.
tagsarrayFree-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
columnstringOnly this column, e.g. 'doing'
due_beforestringOnly tasks due on or before this day (YYYY-MM-DD, 'today', 'Friday', '+7d')
include_donebooleanInclude finished tasks; default false
limitintegerRows to print; default 200
overduebooleanOnly tasks past their due date
projectstringOnly this project
tagstringOnly 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
limitintegerRows 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
duestringNew due date, or 'none' to clear it
estimate_minutesinteger
idstringyesTask id, e.g. NOVA-12
notesstring
prioritystring
projectstringMove the task to another existing project board
tagsarrayReplaces 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
weekstringISO 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/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 MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/kanban.mcpb).

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

io.github.theluckystrike/kanban-todo-tasks-projects-board scores 48 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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,576 tokens of context every time the server is loaded.

What licence is the io.github.theluckystrike/kanban-todo-tasks-projects-board MCP server under?

io.github.theluckystrike/kanban-todo-tasks-projects-board declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.