Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Elytrack

REMOTE · ELYTRACK.IO

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

Available components

−68 this week 0 Trust /100

Last scanned (1 day ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 13 Nov 2026.

Category Crypto and Web3

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: even once the server responds again it stays dead until it is manually reinstated.

Recent critical change

TLS certificate (14 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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.

What we tested

Checks we ran (4)

  • TLS certificate
  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • TLS certificate hostname

    Registry says
    https://elytrack.io/mcp
    Package shows
    Certificate names *.up.railway.app, up.railway.app

    The certificate does not name the host we connected to. See the evidence →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 −14

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

  • 19 Nov 26 −13

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

  • 18 Nov 26 −14

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

  • 17 Nov 26 −13

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

  • 16 Nov 26 −14

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

  • 14 Nov 26 0
    • TLS certificate: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Nov 2026 · Probed https://elytrack.io/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Chain error: Hostname mismatch

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 618edc56941aa1165ddb080bf9f799eb7c1
SANs: *.up.railway.app, up.railway.app
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of elytrack.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
elytrack.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://elytrack.io/mcp TLS failed
http (plaintext) http://elytrack.io/mcp HTTPS enforced 301 https://elytrack.io/mcp
MCP tools · 13 exposed · ~850 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_buy_tx ~130

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.

NameTypeReqDescription
amount_hypestringyesHYPE to spend, e.g. "0.5"
slippage_pctnumber–percent
tokenstringyes–
walletstringyes–

No output schema declared.

No examples provided.

build_sell_tx ~92

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.

NameTypeReqDescription
amountstringyestokens to sell, e.g. "1500.5", or "all"
slippage_pctnumber–percent
tokenstringyes–
walletstringyes–

No output schema declared.

No examples provided.

get_feed ~68

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.

NameTypeReqDescription
after_idinteger––
groupstring––
limitinteger––

No output schema declared.

No examples provided.

get_launches ~73

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.

NameTypeReqDescription
limitinteger––
min_insider_pctinteger––
signals_onlyboolean––

No output schema declared.

No examples provided.

get_launchpads ~55

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_news ~45

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

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

get_smart_tokens ~103

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.

NameTypeReqDescription
limitinteger––
min_walletsinteger––
montra_onlyboolean–only tokens tradable with build_buy_tx
sortstring––
windowstring––

No output schema declared.

No examples provided.

get_token ~60

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.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

get_top_wallets ~51

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

NameTypeReqDescription
limitinteger––
sortstring––
viewstring––

No output schema declared.

No examples provided.

get_tx_status ~39

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

NameTypeReqDescription
hashstringyes–

No output schema declared.

No examples provided.

get_wallet ~38

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

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

search_tokens ~37

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

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

send_signed_tx ~59

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.

NameTypeReqDescription
signed_txstringyes0x-prefixed signed transaction

No output schema declared.

No examples provided.

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.

remote · elytrack.io

# add to Claude Code
claude mcp add --transport http io-elytrack-elytrack 'https://elytrack.io/mcp'
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.