Remote MCP · Endpoint

GateOnAI MCP server

No. GateOnAI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.gateonai.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.giorgio44/gateonai-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
291 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Search and compare AI tools, build AI workflows, find tools that state EU hosting. No API key.
Listing
From the official MCP registry (active).
Recent checks of GateOnAI
CheckedResultHandshake
2 hours agoHandshake completed291 ms
12 hours agoHandshake completed376 ms
1 day agoHandshake completed142 ms
2 days agoHandshake completed306 ms
4 days agoHandshake completed292 ms
4 days agoHandshake completed294 ms
5 days agoHandshake completed135 ms
6 days agoHandshake completed291 ms
8 days agoHandshake completed404 ms
11 days agoHandshake completed298 ms
13 days agoHandshake completed299 ms
16 days agoHandshake completed326 ms
18 days agoHandshake completed333 ms
20 days agoHandshake completed304 ms
22 days agoHandshake completed288 ms
24 days agoHandshake completed140 ms

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

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