Remote MCP · Endpoint
Gate MCP MCP server
No. Gate MCP answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.gatemcp.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.gateio-dev/gate-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 233 ms
- Tools exposed
- 83 tools
- Uptime, last 30 days
- 50.0% from 18 checks
- Described by its publisher as
- Public Gate market data MCP for spot, futures, margin, options, delivery, earn, and alpha.
- Repository
- https://github.com/gate/gate-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 233 ms |
| 1 day ago | Handshake completed | 236 ms |
| 2 days ago | Handshake completed | 351 ms |
| 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 | Handshake completed | 420 ms |
| 22 days ago | Handshake completed | 229 ms |
| 24 days ago | Handshake completed | 565 ms |
| 26 days ago | Handshake completed | 280 ms |
| 27 days ago | Handshake completed | 569 ms |
| 29 days ago | Handshake completed | 279 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 20 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 Gate MCP and makes no claim about it beyond what these checks measured.