Remote MCP · Endpoint

ai.robomart/robomart MCP server

No. ai.robomart/robomart answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.robomart.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.robomart/robomart
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
296 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Driverless delivery.
Listing
From the official MCP registry (active).
Recent checks of ai.robomart/robomart
CheckedResultHandshake
8 hours agoHandshake completed296 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed238 ms
5 days agoHandshake completed311 ms
7 days agoHandshake completed151 ms
8 days agoHandshake completed287 ms
9 days agoHandshake completed251 ms
12 days agoHandshake completed117 ms
13 days agoHandshake completed256 ms
15 days agoHandshake completed288 ms
16 days agoHandshake completed133 ms
17 days agoHandshake completed142 ms
18 days agoHandshake completed146 ms
19 days agoHandshake completed119 ms
20 days agoHandshake completed140 ms
21 days agoHandshake completed120 ms
23 days agoHandshake completed153 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 ai.robomart/robomart and makes no claim about it beyond what these checks measured.