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.
Listing
From the official MCP registry (active).
Recent checks of $AI on HyperEVM
CheckedResultHandshake
2 hours agoHandshake completed401 ms
1 day agoHandshake completed383 ms
4 days agoHandshake completed413 ms
6 days agoHandshake completed441 ms
8 days agoHandshake completed393 ms
9 days agoHandshake completed428 ms
11 days agoHandshake completed365 ms
12 days agoHandshake completed349 ms
13 days agoHandshake completed344 ms
16 days agoHandshake completed391 ms
17 days agoHandshake completed362 ms
19 days agoHandshake completed391 ms
20 days agoHandshake completed348 ms
21 days agoHandshake completed326 ms
22 days agoHandshake completed364 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.