Remote MCP · Endpoint

Mlola UI MCP server

No. Mlola UI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ui.mlola.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.mlolahq/mlola-ui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
375 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Mlola UI components, tokens and design rules for coding agents, with a markup checker
Listing
From the official MCP registry (active).
Recent checks of Mlola UI
CheckedResultHandshake
1 hour agoHandshake completed375 ms
2 days agoHandshake completed298 ms
4 days agoHandshake completed642 ms
6 days agoHandshake completed293 ms
8 days agoHandshake completed371 ms
10 days agoHandshake completed291 ms
11 days agoHandshake completed324 ms
13 days agoHandshake completed396 ms
14 days agoHandshake completed313 ms
15 days agoHandshake completed314 ms
18 days agoHandshake completed291 ms
19 days agoHandshake completed619 ms
21 days agoHandshake completed389 ms
23 days agoHandshake completed318 ms
24 days agoHandshake completed342 ms

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

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