Remote MCP · Endpoint

X-EGO MCP server

No. X-EGO answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.x-ego.com/mcp

The last check completed an MCP handshake.

Registry name
com.x-ego/x-ego
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
606 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Human approval for irreversible AI agent actions, bound to the exact tool call by a passkey tap
Listing
From the official MCP registry (active).
Recent checks of X-EGO
CheckedResultHandshake
1 hour agoHandshake completed606 ms
2 days agoHandshake completed444 ms
4 days agoHandshake completed537 ms
5 days agoHandshake completed544 ms
7 days agoHandshake completed474 ms
8 days agoHandshake completed1.04 s
9 days agoHandshake completed540 ms
12 days agoHandshake completed342 ms
13 days agoHandshake completed539 ms
15 days agoHandshake completed369 ms
16 days agoHandshake completed359 ms
18 days agoHandshake completed438 ms
19 days agoHandshake completed339 ms
20 days agoHandshake completed475 ms
20 days agoHandshake completed590 ms
21 days agoHandshake completed686 ms
22 days agoHandshake completed418 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 X-EGO and makes no claim about it beyond what these checks measured.