Remote MCP · Endpoint

nimo MCP server

Yes, as of 1 hour ago: the request timed out.

DownLast checked 1 hour ago

Server URL

https://api.heynimo.com/mcp-server

The last check failed: the request timed out.

Registry name
io.github.marvtub/nimo
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Website monitoring: uptime alerts, page speed and Core Web Vitals with the next fix, cron check-ins.
Listing
From the official MCP registry (active).
Recent checks of nimo
CheckedResultHandshake
1 hour agoFailed - the request timed out—
1 day agoCredentials required—
2 days agoCredentials required—
2 days agoCredentials required—
4 days agoCredentials required—
7 days agoCredentials required—
9 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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

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