Remote MCP · Endpoint

Milanote MCP Server and API by Cotlet MCP server

No. Milanote MCP Server and API by Cotlet answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://cotlet.dev/mcp/v1/milanote

The last check completed an MCP handshake.

Registry name
dev.cotlet/milanote
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
190 ms
Tools exposed
69 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Milanote visual planning for creatives MCP server: list boards, add note, add link, upload image.
Listing
From the official MCP registry (active).
Recent checks of Milanote MCP Server and API by Cotlet
CheckedResultHandshake
38 minutes agoHandshake completed190 ms
3 days agoHandshake completed471 ms
12 days agoHandshake completed229 ms
12 days agoHandshake completed144 ms
14 days agoHandshake completed185 ms
15 days agoHandshake completed174 ms
16 days agoHandshake completed190 ms
17 days agoHandshake completed157 ms
18 days agoHandshake completed157 ms
20 days agoHandshake completed148 ms
22 days agoHandshake completed187 ms
25 days agoHandshake completed173 ms

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

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 Milanote MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.