_ registry / mcp streamable-http · checked 35m ago

kanbanthing

https://www.kanbanthing.com

Registry code: cc561ccccd4f2a18

api record

Drive a KanbanThing board. Every tool needs a board_id the user supplied - either a board UUID or a board URL. There is no way to list or search boards, so ask the user for the link rather than guessing. Boards with a password need it passed as `password` on every call.

endpoint
https://www.kanbanthing.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is kanbanthing live?
Yes — it answered the hub's last check (checked 35m ago). It answered 99% of checks over the last 30 days.
Is kanbanthing free to use?
Yes — the hub reached it with no key and no payment.
What tools does kanbanthing have?
8 tools: create_card, delete_card, list_cards, create_board, get_board, list_columns, move_card, update_card.
Is kanbanthing safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.5%· all time 99.5%

latency
1,049ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 407 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business tasks & projects
used for
  • create a kanban board
  • add and move cards on a board
  • update or delete cards
  • list cards in a column
takes → gives
text, data → data
tools
3 reads5 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 8 tools
8 never probed 0 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • create_card changes data unknown never probed

    Add a card to a column on a board. Lands in Backlog when no column is given.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id",
    "title"
  ],
  "properties": {
    "color": {
      "type": "string",
      "pattern": "^#[0-9a-f]{6}$",
      "description": "Card colour as #rrggbb."
    },
    "title": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Card title."
    },
    "column": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Column name or id. Defaults to Backlog."
    },
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "due_date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Due day as YYYY-MM-DD."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    },
    "description": {
      "type": "string",
      "maxLength": 4000
    }
  }
}
    arguments 47 lines
  • delete_card changes data unknown never probed

    Permanently delete a card from a board. This cannot be undone.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id",
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
      "description": "Card id from list_cards."
    },
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    }
  }
}
    arguments 26 lines
  • list_cards reads unknown 22h ago

    List the cards on a board, optionally only those in one column.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Maximum cards to return. Defaults to 100."
    },
    "column": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Column name or id. Omit for every column."
    },
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    }
  }
}
    arguments 32 lines
  • create_board changes data unknown never probed

    Create a new KanbanThing board and return its id, shareable URL and password. No sign-up. Every board is password protected: pass `password` to choose one, otherwise a random password is generated and returned. Give both the URL and the password to whoever should use the board. Boards are deleted when they expire.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Board name shown to everyone."
    },
    "columns": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1
      },
      "maxItems": 10,
      "description": "Columns left to right after Backlog. Defaults to To Do, In Progress, Done."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "Board password. A random one is generated and returned if omitted."
    },
    "lifespan_days": {
      "type": "integer",
      "maximum": 60,
      "minimum": 1,
      "description": "Days until the board is deleted. Defaults to 60."
    }
  }
}
    arguments 36 lines
  • get_board reads unknown 22h ago

    Read a board by id: its name, expiry, columns and how many cards each column holds.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id"
  ],
  "properties": {
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    }
  }
}
    arguments 20 lines
  • list_columns reads unknown 22h ago

    List the columns on a board, left to right, with their ids.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id"
  ],
  "properties": {
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    }
  }
}
    arguments 20 lines
  • move_card changes data unknown never probed

    Move a card to another column on the same board, at the end of that column.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id",
    "card_id",
    "column"
  ],
  "properties": {
    "column": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Destination column name or id."
    },
    "card_id": {
      "type": "string",
      "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
      "description": "Card id from list_cards."
    },
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    }
  }
}
    arguments 33 lines
  • update_card changes data unknown never probed

    Change a card title, description, due date or colour. Pass null to clear a field. Use move_card to change column.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "board_id",
    "card_id"
  ],
  "properties": {
    "color": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^#[0-9a-f]{6}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "Card colour as #rrggbb, or null."
    },
    "title": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    },
    "card_id": {
      "type": "string",
      "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
      "description": "Card id from list_cards."
    },
    "board_id": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1,
      "description": "The board UUID, or the board URL the user shared. Never invent one."
    },
    "due_date": {
      "anyOf": [
        {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        {
          "type": "null"
        }
      ],
      "description": "Due day as YYYY-MM-DD, or null."
    },
    "password": {
      "type": "string",
      "maxLength": 100,
      "description": "The board password, if the board is protected."
    },
    "description": {
      "anyOf": [
        {
          "type": "string",
          "maxLength": 4000
        },
        {
          "type": "null"
        }
      ]
    }
  }
}
    arguments 66 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id cc561ccccd4f2a18.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cc561ccccd4f2a18/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cc561ccccd4f2a18/badge.svg)](https://brick.blue/agent/cc561ccccd4f2a18?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.