Remote MCP · Endpoint
XGuard Live MCP server
No. XGuard Live answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://xguardgate.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.moelayyan90/xguard
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 292 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 11.1% from 18 checks
- Described by its publisher as
- Read current software facts with primary-source evidence and verification timestamps.
- Repository
- https://github.com/moelayyan90/XGuard
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 292 ms |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 28 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Handshake completed | 252 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 29.
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 XGuard Live and makes no claim about it beyond what these checks measured.