Remote MCP · Endpoint

McpStamp Kanban Board MCP server

No. McpStamp Kanban Board answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mcp.zovo.one/mcp/kanban

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/kanban-todo-tasks-projects-board
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Task boards per project: priorities, due dates, estimates, overdue tasks and a weekly review.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Kanban Board
CheckedResultHandshake
20 minutes agoHandshake completed106 ms
8 days agoHandshake completed239 ms
9 days agoHandshake completed38 ms
11 days agoHandshake completed41 ms
12 days agoHandshake completed49 ms
13 days agoHandshake completed32 ms
14 days agoHandshake completed39 ms
15 days agoHandshake completed230 ms
16 days agoHandshake completed134 ms
19 days agoHandshake completed53 ms
21 days agoHandshake completed31 ms
24 days agoHandshake completed24 ms
26 days agoHandshake completed165 ms
28 days agoHandshake completed712 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with McpStamp Kanban Board and makes no claim about it beyond what these checks measured.