Remote MCP · Endpoint

Mode Analytics MCP Server and API by Cotlet MCP server

No. Mode Analytics MCP Server and API by Cotlet answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://cotlet.dev/mcp/v1/mode-analytics

The last check completed an MCP handshake.

Registry name
dev.cotlet/mode-analytics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
34 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Mode Analytics collaborative sql analytics MCP server: list reports, run report, read run results.
Listing
From the official MCP registry (active).
Recent checks of Mode Analytics MCP Server and API by Cotlet
CheckedResultHandshake
5 hours agoHandshake completed150 ms
4 days agoHandshake completed258 ms
7 days agoFailed - the check failed for an unclassified reason—

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

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