Remote MCP · Endpoint

cnvs.app MCP server

No. cnvs.app answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://cnvs.app/mcp

The last check completed an MCP handshake.

Registry name
app.cnvs/whiteboard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
236 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Real-time collaborative whiteboard — AI agents and humans edit the same board live over MCP.
Listing
From the official MCP registry (active).
Recent checks of cnvs.app
CheckedResultHandshake
9 hours agoHandshake completed236 ms
2 days agoHandshake completed239 ms
4 days agoHandshake completed192 ms
5 days agoHandshake completed203 ms
7 days agoHandshake completed313 ms
8 days agoHandshake completed233 ms
9 days agoHandshake completed51 ms
12 days agoHandshake completed202 ms
13 days agoHandshake completed167 ms
15 days agoHandshake completed219 ms
16 days agoHandshake completed168 ms
17 days agoHandshake completed175 ms
19 days agoHandshake completed209 ms
19 days agoHandshake completed179 ms
20 days agoHandshake completed239 ms
21 days agoHandshake completed234 ms
22 days agoHandshake completed192 ms

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

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 cnvs.app and makes no claim about it beyond what these checks measured.