Remote MCP · Endpoint

Cotlet MCP server

No. Cotlet answered an MCP handshake 45 minutes ago.

UpLast checked 45 minutes ago

Server URL

https://cotlet.dev/mcp/v1

The last check completed an MCP handshake.

Registry name
dev.cotlet/cotlet
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
223 ms
Tools exposed
635 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hosted MCP server and REST API that lets AI agents use apps with no API, signed in as you.
Listing
From the official MCP registry (active).
Recent checks of Cotlet
CheckedResultHandshake
45 minutes agoHandshake completed223 ms
3 days agoHandshake completed150 ms
12 days agoHandshake completed230 ms
13 days agoHandshake completed420 ms
14 days agoHandshake completed151 ms
15 days agoHandshake completed146 ms
16 days agoHandshake completed139 ms
17 days agoHandshake completed215 ms
18 days agoHandshake completed189 ms
20 days agoHandshake completed171 ms
22 days agoHandshake completed234 ms
25 days agoHandshake completed570 ms
27 days agoHandshake completed203 ms

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

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