Remote MCP · Endpoint

Language mi MCP server

No. Language mi answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/lang-mi/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/lang-mi
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
307 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
ISO 639 language tag mi.
Listing
From the official MCP registry (active).
Recent checks of Language mi
CheckedResultHandshake
1 day agoHandshake completed307 ms
11 days agoHandshake completed26 ms
12 days agoHandshake completed161 ms
13 days agoHandshake completed25 ms
14 days agoHandshake completed14 ms
16 days agoHandshake completed155 ms
16 days agoHandshake completed20 ms
17 days agoHandshake completed18 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed20 ms
23 days agoHandshake completed16 ms
25 days agoHandshake completed22 ms
28 days agoHandshake completed31 ms

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

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