Remote MCP · Endpoint
$AI on HyperEVM MCP server
No. $AI on HyperEVM answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://thetickeris.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.thetickeris/agent-rail
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 401 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Quote and build unsigned buy/sell transactions for $AI on its HyperEVM bonding curve. No keys held.
- Website
- https://thetickeris.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 401 ms |
| 1 day ago | Handshake completed | 383 ms |
| 4 days ago | Handshake completed | 413 ms |
| 6 days ago | Handshake completed | 441 ms |
| 8 days ago | Handshake completed | 393 ms |
| 9 days ago | Handshake completed | 428 ms |
| 11 days ago | Handshake completed | 365 ms |
| 12 days ago | Handshake completed | 349 ms |
| 13 days ago | Handshake completed | 344 ms |
| 16 days ago | Handshake completed | 391 ms |
| 17 days ago | Handshake completed | 362 ms |
| 19 days ago | Handshake completed | 391 ms |
| 20 days ago | Handshake completed | 348 ms |
| 21 days ago | Handshake completed | 326 ms |
| 22 days ago | Handshake completed | 364 ms |
The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.
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 $AI on HyperEVM and makes no claim about it beyond what these checks measured.