Remote MCP · Endpoint
XGuard — Agent Execution Gateway MCP server
No. XGuard — Agent Execution Gateway answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.xguardgate.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.moelayyan90/xguard-control-plane
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 248 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 11.1% from 18 checks
- Described by its publisher as
- Scoped agent execution. Server-side credentials, policy, budgets and verifiable receipts.
- Repository
- https://github.com/moelayyan90/XGuard
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 248 ms |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 2 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 | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
| 26 days ago | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Handshake completed | 304 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 — Agent Execution Gateway and makes no claim about it beyond what these checks measured.