io.elytrack/elytrack
Elytrack
Is the Elytrack MCP server down? It gave no valid answer in the probe of 2026-11-14: TLS error. One failed probe is not an outage.
Smart wallets, insiders, launches and news on Elysium (Hyperliquid L2), plus Montra trades.
TLS error no valid answer since 2026-11-14 · probed 2026-11-15 · unchanged since 2026-11-14
fetch failed | Hostname/IP does not match certificate's altnames: Host: elytrack.io. is not in the cert's altnames: DNS:*.up.railway.app, DNS:up.railway.app | E
- Endpoint
- https://elytrack.io/mcp (streamable-http)
- Host
- elytrack.io
- Website
- https://elytrack.io/agents
- Registry
- active, updated 2026-11-07 · registry entry
- Changes
- 3 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention hyperliquid or insiders.
- AgentFilings com.agentfilings/mcp · alive
- Bitpoort com.bitpoort/on-chain-data · needs auth
- Distill Markets com.distillmarkets/distill-markets · needs auth
- MrTrades Hyperliquid desk com.mrtrades/desk · needs auth
- Resolved Markets com.resolvedmarkets/mcp · needs auth
- chiefofstaff Hyperliquid perp data + token safety com.run402.chiefofstaff-solana/token-safety · alive
- Tape — Hyperliquid Analytics com.tapeperp/tape · alive
- Tickwind US Market Boards com.tickwind/tickwind · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-14 10:49 | TLS error | ||||
| 2026-11-08 10:44 | alive | 1.0 s | 13 | 2.6k | 1.5k |
| 2026-11-07 10:38 | alive | 3.4 s | 13 | 2.6k | 1.5k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-14. One failed probe is not an outage: the board calls a server down after two days without a valid answer. The next probe runs within a day.
- The TLS handshake fails: an expired or mismatched certificate, or an unsupported protocol version.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.