Remote MCP · Endpoint
Gate DEX MCP MCP server
No. Gate DEX MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.gatemcp.ai/mcp/dex
The last check completed an MCP handshake.
- Registry name
- io.github.gateio-dev/gate-dex
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 271 ms
- Tools exposed
- 47 tools
- Uptime, last 30 days
- 38.9% from 18 checks
- Described by its publisher as
- Gate DEX MCP for wallet auth, transfers, swaps, token info, market data, and RPC access.
- Repository
- https://github.com/gate/gate-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 271 ms |
| 1 day ago | Handshake completed | 247 ms |
| 2 days ago | Handshake completed | 226 ms |
| 3 days ago | Handshake completed | 258 ms |
| 4 days ago | Handshake completed | 244 ms |
| 5 days ago | Handshake completed | 245 ms |
| 6 days ago | Handshake completed | 223 ms |
| 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 | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 7 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 DEX MCP and makes no claim about it beyond what these checks measured.