Remote MCP · Endpoint

Mila MCP server

No. Mila answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.mila.gg/

The last check completed an MCP handshake.

Registry name
io.github.mila-gg/mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
229 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Create and manage documents, spreadsheets, and presentations from your AI assistant.
Listing
From the official MCP registry (active).
Recent checks of Mila
CheckedResultHandshake
2 hours agoHandshake completed229 ms
2 days agoHandshake completed207 ms
4 days agoHandshake completed213 ms
5 days agoHandshake completed201 ms
7 days agoHandshake completed232 ms
8 days agoHandshake completed198 ms
9 days agoHandshake completed221 ms
12 days agoHandshake completed199 ms
13 days agoHandshake completed202 ms
15 days agoHandshake completed210 ms
17 days agoHandshake completed208 ms
18 days agoHandshake completed214 ms
19 days agoHandshake completed227 ms
20 days agoHandshake completed215 ms
20 days agoHandshake completed198 ms
21 days agoHandshake completed205 ms
23 days agoHandshake completed200 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 Mila and makes no claim about it beyond what these checks measured.