Remote MCP · Endpoint

mu.micro/mu MCP server

No. mu.micro/mu answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://micro.mu/mcp

The last check completed an MCP handshake.

Registry name
mu.micro/mu
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
250 ms
Tools exposed
170 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Website
https://micro.mu/
Repository
https://github.com/micro/mu
Listing
From the official MCP registry (active).
Recent checks of mu.micro/mu
CheckedResultHandshake
1 hour agoHandshake completed250 ms
1 day agoHandshake completed249 ms
2 days agoHandshake completed265 ms
3 days agoHandshake completed242 ms
4 days agoHandshake completed297 ms
5 days agoHandshake completed254 ms
6 days agoHandshake completed246 ms
8 days agoHandshake completed249 ms
11 days agoHandshake completed334 ms
13 days agoHandshake completed245 ms
15 days agoHandshake completed247 ms
18 days agoHandshake completed243 ms
20 days agoHandshake completed245 ms
22 days agoHandshake completed246 ms
24 days agoHandshake completed243 ms
26 days agoHandshake completed250 ms
27 days agoHandshake completed246 ms
28 days agoHandshake completed247 ms
29 days agoHandshake completed243 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with mu.micro/mu and makes no claim about it beyond what these checks measured.