# Elytrack (remote · elytrack.io)

Smart wallets, insiders, launches and news on Elysium (Hyperliquid L2), plus Montra trades.

- Trust score: 0/100 (low)
- Change this week: −68
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-11-20

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

> **Recent critical change**: TLS certificate (2026-11-14). See the changelog below before you install this server.

## Components

- remote · `elytrack.io`: 0/100 (this document), [markdown](https://verifymcp.io/servers/io-elytrack-elytrack/elytrack.md), [page](https://verifymcp.io/servers/io-elytrack-elytrack/elytrack)

## Channel facts

- Endpoint: `https://elytrack.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-20.

- **Endpoint Security**: 11/100
  - TLS check failed: the certificate doesn't match the endpoint's hostname.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the TLS certificate failed verification.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This view is read from the stored diagnostics trace and is never an input to the score. Each row links to its evidence.

### TLS certificate hostname

- Registry says: `https://elytrack.io/mcp`
- Package shows: `Certificate names *.up.railway.app, up.railway.app`
- What it means: The certificate does not name the host we connected to.
- Evidence: https://verifymcp.io/servers/io-elytrack-elytrack/elytrack#diagnostics-tls

## Install

### How do I install the Elytrack MCP server?

Elytrack is a hosted endpoint at https://elytrack.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-elytrack-elytrack 'https://elytrack.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-elytrack-elytrack": {
      "url": "https://elytrack.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-elytrack-elytrack": {
      "type": "http",
      "url": "https://elytrack.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-elytrack-elytrack]
url = "https://elytrack.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-elytrack-elytrack": {
      "type": "remote",
      "url": "https://elytrack.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-elytrack-elytrack --url 'https://elytrack.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-elytrack-elytrack:
    url: "https://elytrack.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-elytrack-elytrack": {
      "Transport": "http",
      "Url": "https://elytrack.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-elytrack-elytrack -t streamable-http -u 'https://elytrack.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-elytrack-elytrack": {
      "type": "http",
      "url": "https://elytrack.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 0, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-19 (score 14, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-18 (score 27, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-17 (score 41, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-16 (score 54, −14)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-14 (score 68, 0)

- [critical regression] TLS certificate: pass → fail
- [critical regression] Score status: scored → failed
- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-12 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `get_smart_tokens` (~103 tokens)

Tokens smart wallets buy

Tokens that smart wallets (a track record of early 2x calls) and insiders (linked to a dev) bought within a window, most wallets first, with how many still hold and the move since the first smart buy.

Input parameters:

- `limit` (integer)
- `min_wallets` (integer)
- `montra_only` (boolean): only tokens tradable with build_buy_tx
- `sort` (string)
- `window` (string)

### `get_token` (~60 tokens)

Token details

One token: live market (mcap, change, volume, holders), the smart wallets and insiders in it, its launch (dev bundle, same-block buys, snipers; bots left out) and its earliest wallets.

Input parameters:

- `address` (string, required)

### `get_wallet` (~38 tokens)

Wallet details

One wallet: skill, early calls, holding habits, insider evidence and its trades of the last 7 days.

Input parameters:

- `address` (string, required)

### `get_feed` (~68 tokens)

Live feed

Live alerts, newest first: insider and smart buys and sells, launches, bundle and dev sells, clusters. Pass after_id (the largest id you have) to get only new ones.

Input parameters:

- `after_id` (integer)
- `group` (string)
- `limit` (integer)

### `get_launches` (~73 tokens)

Launches

Recent launches on every launchpad with dev bundle, insiders' share, snipers and smart buys. signals_only (default) keeps the last 24 hours' launches that have any of these.

Input parameters:

- `limit` (integer)
- `min_insider_pct` (integer)
- `signals_only` (boolean)

### `get_top_wallets` (~51 tokens)

Top wallets

Wallets ranked: smart (by skill), insiders (by evidence), all, or sniper bots.

Input parameters:

- `limit` (integer)
- `sort` (string)
- `view` (string)

### `get_launchpads` (~55 tokens)

Launchpads compared

Every Elysium launchpad compared: 24h volume and trades, launches today and this week, tokens in all, tokens over $100K and the share of dev-bundled launches, with each one's top tokens.

### `get_news` (~45 tokens)

Chain news

Chain news from on-chain events: market cap milestones, new launchpads, insider clusters, large dev sells, heavily bundled launches and the daily recap.

Input parameters:

- `limit` (integer)

### `search_tokens` (~37 tokens)

Search tokens

Find tokens by symbol prefix (case-insensitive), largest market cap first.

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `build_buy_tx` (~130 tokens)

Build a buy

Build a Montra buy (HYPE -> token) for your wallet: one transaction with nonce, fees and gas filled, plus the quote and the minimum you will accept. Elytrack's fee (elytrack_fee_pct of amount_hype, shown in the answer) is paid out of amount_hype in the same transaction. Sign it yourself; Elytrack holds no keys.

Input parameters:

- `amount_hype` (string, required): HYPE to spend, e.g. "0.5"
- `slippage_pct` (number): percent
- `token` (string, required)
- `wallet` (string, required)

### `build_sell_tx` (~92 tokens)

Build a sale

Build a Montra sale (token -> HYPE) for your wallet: an approve for the router when needed, then the swap. Sign them yourself and send them in order.

Input parameters:

- `amount` (string, required): tokens to sell, e.g. "1500.5", or "all"
- `slippage_pct` (number): percent
- `token` (string, required)
- `wallet` (string, required)

### `send_signed_tx` (~59 tokens)

Send a signed transaction

Send a transaction you signed into Elysium through the Montra RPC. Returns its hash; check it with get_tx_status. At most 10 a minute per client.

Input parameters:

- `signed_tx` (string, required): 0x-prefixed signed transaction

### `get_tx_status` (~39 tokens)

Transaction status

Where a sent transaction is: queued, posted to the inbox, landed (with block and success) or dropped.

Input parameters:

- `hash` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-elytrack-elytrack/elytrack#diagnostics

## Score history

- 2026-11-20: 0
- 2026-11-19: 14
- 2026-11-18: 27
- 2026-11-17: 41
- 2026-11-16: 54
- 2026-11-15: 68
- 2026-11-14: 68
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 67
- 2026-11-10: 67
- 2026-11-09: 66
- 2026-11-08: 66
- 2026-11-07: 65

## Common questions

### What is the Elytrack MCP server?

Elytrack is an MCP server listed in the public MCP registry as io.elytrack/elytrack. Smart wallets, insiders, launches and news on Elysium (Hyperliquid L2), plus Montra trades. This page covers its hosted endpoint (https://elytrack.io/mcp).

### What tools does the Elytrack MCP server expose?

Elytrack exposes 13 tools: get_smart_tokens, get_token, get_wallet, get_feed, get_launches, and 8 more. Their descriptions and schemas cost roughly 850 tokens of context every time the server is loaded.

### Does the Elytrack MCP server require authentication?

Its publisher declares no required credentials for Elytrack. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Elytrack MCP server still maintained?

Elytrack has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 13 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://elytrack.io/mcp
- Website: https://elytrack.io/agents
- Changelog RSS feed: https://verifymcp.io/servers/io-elytrack-elytrack/elytrack.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-elytrack-elytrack/elytrack/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-elytrack-elytrack/elytrack.json
- HTML version of this page: https://verifymcp.io/servers/io-elytrack-elytrack/elytrack
