List your agent

Femtos

MCP server · hosted · v1.1.0 · xyz.femtos/mcp
Online · tested 2h agoNEW · 3h agoSeen in the registry 2m ago

Hyperliquid data for agents: HyperCore, HyperEVM, Elysium trades, candles, bridges, wallets.

Website ↗How to connect ↓

What it does

Femtos is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence) and are not a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.1.0
PriceNot in the registry
First seen21 Oct 2026
Last checked2m ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)

Hosted endpoint

  • https://api.femtos.xyz/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "femtos": {
      "url": "https://api.femtos.xyz/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 2h ago

ONLINE Femtos answered an MCP connection on 21 Oct 2026 and introduced itself as femtos 1.0.0 (MCP protocol 2025-06-18).

27 tools offered to AI assistants

  • get_status · State of each layer (HyperCore, HyperEVM, Elysium): indexed head block and time, lag behind the chain, live or syncing, Elysium network (testnet / mainnet), HyperCore <> HyperEVM bridge matching coverage. Check it when an answer looks stale
  • list_markets · Tradable markets of a layer, most traded first (24 h USD volume). hypercore: perps, spot, HIP-3 dex perps (dex:COIN), outcome markets; `id` is the coin to pass to get_candles / get_trades (BTC, @107, xyz:TSLA). hyperevm / elysium: DEX pools
  • get_candles · OHLCV candles of one market, ascending, UTC-aligned. hypercore: market = coin (BTC, HYPE, @107 spot, xyz:TSLA), down to 1 s. hyperevm / elysium: market = pool key from list_markets; prices in quote plus `usd` and `mcap` OHLC (USD price and
  • get_trades · Latest trades of a market, newest first. hypercore: fills of a coin (px, sz, side B = buyer aggressor / A, block time). hyperevm / elysium: DEX swaps of a pool (sender, amounts, px = pool price after the swap, USD value).
  • search_coins · Tokens by symbol, name or address, with their links across layers (Elysium <-> HyperEVM <-> HyperCore), decimals, supply and USD price. Without layer: every layer. An exact address always answers its token (spam flagged).
  • get_coin · One token: its links across layers, the markets it trades on (most traded first) and its 5 largest holders. hypercore: id = token name (HYPE), index or token id; hyperevm / elysium: id = 0x address.
  • get_holders · Largest holders of a token and its concentration (top-10 share…); system addresses (pools, bridges, launchpad, zero/dead) counted apart. hypercore: token = name (HYPE), kind = balances (spot) or positions (perp open interest of a coin); hyp
  • list_launches · Latest token launches, newest first: Elysium launchpad Ascend (default) or HyperEVM LiquidLaunch (launchpad = liquidlaunch). Each: token, pool (pair), creator, priceUsd, mcapUsd, 24 h volume, holders, top-10 / dev share, dev sold, Ascend pr
  • get_launch · The story of one launched token: launch event, market cap, volume, holders, dev wallet and its funding, early buyers with flags, coordination signals, fees (exact from the launchpad ledger when indexed), lifecycle stage across layers and, f
  • get_launch_timeline · Replayable life of a launch, oldest first: launch, swaps and transfers with the running holder count and market cap, graduation links (bridge to HyperEVM, HyperCore listing). Long histories are cut to fit (see `truncated`).
  • get_token_lifecycle · One token from launch to perp across Elysium, HyperEVM and HyperCore: its address on each layer, the stages reached (Elysium launch, listing desk, HyperEVM mirror, HyperCore spot, perps) with chain evidence, and the links between them, each
  • get_bridges · Bridge movements, newest first, with 24 h stats. route core_evm: HyperCore <> HyperEVM transfers, both legs matched (status, latency, how they were paired); route evm_elysium: HyperEVM <> Elysium (Orbit) deposits and withdrawals. Filter by
Show 15 more
  • get_wallet · One address on HyperCore, HyperEVM and Elysium at once: HyperCore perp account (value, positions with liquidation price) and spot balances, HyperEVM and Elysium token balances and NFTs with USD values, bridge legs in flight and journeys acr
  • get_token_volume · Daily USD swap volume of an EVM token (both sides of every priced swap), oldest first, up to the indexed head (the last day is partial).
  • get_erc20_transfers · ERC-20 Transfer events of a token, newest first (from, to, amount, block, tx). Next page: pass `next` as before.
  • get_book · Live L2 order book of one HyperCore market from our own node: bids and asks best first as [px, sz, n] (price, size, order count), and the block it was read at. coin: perp name (BTC), spot @index (@107) or HIP-3 dex:COIN.
  • get_liquidations · HyperCore perp liquidations, newest first: one row per account, coin and block (side of the liquidated position, market or backstop, size, notional, average and mark price). Default window: the last 24 h; `from` older than 7 days (30 with a
  • get_liquidation_stats · HyperCore liquidations over a window (1h, 24h, 7d, 30d), every perp or one coin: totals (notional, count, accounts, long / short, market / backstop), per coin, per time bucket, the most liquidated accounts and the largest events.
  • get_positions · Open positions of one HyperCore perp at the latest holders snapshot: account, size, side, entry price, notional, unrealized PnL at the mark, leverage, margin mode and liquidation price when known. Sort by notional (default), upnl or liqDist
  • list_nft_collections · Most active NFT collections of an EVM layer over the last 1 h or 24 h before the indexed head: transfers, mints, burns, with each collection's name, symbol and standard.
  • get_nft_collection · One NFT collection of an EVM layer: metadata, standards, token ids seen (counted up to 1,000), transfers / mints / burns over the 24 h before the indexed head.
  • get_nft_tokens · Tokens of one collection by token id, ascending: current ERC-721 owner (null for ERC-1155), metadata URI. Next page: pass `next` as after.
  • get_nfts_owned · NFTs an address holds on an EVM layer at the indexed head: ERC-721 tokens and ERC-1155 balances, counted per collection, the tokens listed up to limit.
  • get_nft_transfers · Transfers (mints and burns included) of one collection or one of its tokens, newest first: from, to, token id, amount, block, tx. Next page: pass `next` as before.
  • search_entities · Named wallets (KOLs, traders, funds, market makers) and their wallets, from public attribution lists (not verified identities). A named wallet's address is given as its handle <entityId>.<hex>, usable as an address in every tool. Use the en
  • kol_leaderboard · Named wallets ranked by their trading on a layer. hypercore: PnL, volume, fills, win rate, open notional (default 7d, sort netPnl). hyperevm / elysium: swaps, transfers, net buy, holdings, bridge legs (default 24h, sort volume).
  • kol_activity · Latest moves of named wallets, newest first: HyperCore fills (minNotional USD, default 1000), HyperEVM / Elysium swaps and transfers. Optionally one entity (id from search_entities). Next page: pass `next` as before.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.femtos.xyz/mcpDECLAREDSRC-001 Official MCP Registry2m ago
Version1.1.0DECLAREDSRC-001 Official MCP Registry2m ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2m ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2m ago
Websitehttps://femtos.xyz/mcpDECLAREDSRC-001 Official MCP Registry2m ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2m ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2m ago

Change history

  • NEW21 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Questions about Femtos

How do I connect Femtos?

Use the hosted endpoint https://api.femtos.xyz/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Femtos need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Femtos offer?

When Electra Index connected on 21 Oct 2026, it listed 27 tools: get_status, list_markets, get_candles, get_trades, search_coins, get_coin, get_holders, list_launches and more. The full list is in "Live check" above.

Is Femtos online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.