Home / MCP registry index / com.kanbanmcp/kanbanmcp
KanbanMCP
com.kanbanmcp/kanbanmcp in the official MCP registry.
Endpoint https://kanbanmcp.com/.
The registry describes it as: Hosted kanban for AI agents: claim cards, check in while working, hand off with structured notes.
We read its 31 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
claim_next show heartbeat comment complete request_review block release raise inbox resolve events_since toggle_task find_cards list_boards get_setup get_context rules create_card update_card move_card link undo stop_run promote create_board edit_column delete_column set_brief update_persona label
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-kanbanmcp-kanbanmcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.