原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Femtos

✓ 服务方 · femtos.xyz

作者:femtos.xyz版本 1.2.1i★ –i在云端运行官方网站 ↗
注册名称xyz.femtos/mcp

安装方法

能做什么

Hyperliquid data on HyperCore, HyperEVM, Elysium: balances, prices, trades, token security, bridges

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 需要 Authorization
  • 分类 网络安全

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-10

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 2/3 项(仅展示,不用于排序)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Femtos。按照 https://mcp.popnx.com/i/xyz-femtos-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 2/3 项检查 · 你的提问会经过开发者的服务器(api.femtos.xyz) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 Femtos 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 Femtos 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Femtos 网站 ↗

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Femtos
    Remote MCP server URL · 地址https://api.femtos.xyz/mcp

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +ConnectorsFemtos

  5. 试一试

    用 Femtos 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Femtos,或回答中出现 Femtos 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 Femtos

Femtos 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 Femtos 的应用

  • 需要 Femtos 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 Femtos 的密钥(在开发者网站创建)
  • 需要 Femtos 的密钥(在开发者网站创建)
  • 需要 Femtos 的密钥(在开发者网站创建)

B · 网络安全 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 Femtos 的密钥(在开发者网站创建)

  1. 注册并创建 Femtos 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Femtos 网站 ↗

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user femtos https://api.femtos.xyz/mcp --header 'Authorization: Bearer {femtos_api_key}'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 Femtos 在列表中并显示已连接

  5. 试一试

    用 Femtos 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Femtos,或回答中出现 Femtos 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 Femtos 的密钥(在开发者网站创建)

  1. 注册并创建 Femtos 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Femtos 网站 ↗

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Femtos 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Femtos 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Femtos,或回答中出现 Femtos 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 Femtos 的密钥(在开发者网站创建)

  1. 注册并创建 Femtos 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    打开 Femtos 网站 ↗

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 Femtos 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 Femtos 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Femtos,或回答中出现 Femtos 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://api.femtos.xyz/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Femtos 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user femtos https://api.femtos.xyz/mcp --header 'Authorization: Bearer {femtos_api_key}'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "femtos": {
      "url": "https://api.femtos.xyz/mcp",
      "headers": {
        "Authorization": "Bearer {femtos_api_key}"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "femtos": {
      "type": "http",
      "url": "https://api.femtos.xyz/mcp",
      "headers": {
        "Authorization": "Bearer {femtos_api_key}"
      }
    }
  }
}

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Bearer . Free, no browser needed: https://femtos.xyz/agents.md#agent-onboarding

说明仍为英文原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ femtos.xyz
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.2.1
发布到注册中心i
2026年11月10日
代码最后更新i
–
最近检查
2026年11月15日
作者
femtos.xyz
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月15日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • get_status

    State of each layer (HyperCore, HyperEVM, Elysium): indexed head block and time, lag behind the chain, live or syncing, Elysium network (mainnet), HyperCore <> HyperEVM bridge matching coverage. Check it when an answer looks stale. Free.

  • list_markets

    Tradable markets of a layer, most traded first (24 h USD volume) unless sort says otherwise; HyperCore markets are sorted by the tool (GET /v1/markets without sort answers them in the venue's order). hypercore: perps, spot, HIP-3 dex perps (dex:COIN), outcome markets; `id` is the

  • list_top_tokens

    The tokens of HyperEVM or Elysium with activity (a pool traded in the last 24 hours, or created in the last hour), one row per token over all its pools (not one per pool like list_markets): price, windows 5m / 1h / 6h / 24h (change, volume, trades, buys / sells, distinct traders

  • 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 market cap). hypercore with includeUsd:

  • 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). Answer: an array of trades with only market / limit; one o

  • 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. Price, FDV, liquidity and 5m–24h windows over all its pools: get_token_overview.

  • 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); hyperevm / elysium: token = 0x address. Nam

  • get_holders_history

    How the number of holders of a HyperEVM or Elysium ERC-20 evolved: one point a UTC day (holders at the indexed head just after 00:00 UTC, system addresses such as pools, bridges and zero / dead left out, as get_holders totalHolders) and the count now. History from the layer's fir

  • list_launches

    Latest token launches: Elysium (default) every launchpad, Ascend and every bonding curve inferred from its trades (launchpad name, curve progress, graduation to a DEX pool), or HyperEVM LiquidLaunch (launchpad = liquidlaunch). Each: token, the pool it trades in now (pair), creato

  • list_launchpads

    Every launchpad of Elysium (default) or HyperEVM ranked by launches in 24 h (or by 24 h volume, graduations, all-time launches): launches 24h / 7d / all time, tokens on their curve, graduated and the graduation rate, the 24 h USD volume of its tokens, its top token, its latest la

  • get_launchpad

    One launchpad of Elysium (default) or HyperEVM by name (ascend, obol, liquidlaunch… as list_launchpads names them) or contract: launches 24h / 7d / all time, on curve, graduated and the rate, 24 h volume, top token, and its launches and graduations per day over 30 days.

  • list_new_tokens

    Every ERC-20 created on HyperEVM or Elysium, newest first (not only launchpad launches): creation block / tx / time, creator, the contract it was deployed through, launchpad (ascend, liquidlaunch… or null = direct), first pool (dex, quote, initial liquidity) and, once a pool exis

  • list_new_pools

    Every new pair / pool of every DEX on HyperEVM or Elysium (V2, V3, V4, PancakeSwap Infinity, LiquidLaunch curves…), newest first: dex, factory, fee tier, hooks, both tokens with symbols and whether each was just created (newToken), creation block / tx / time, initial liquidity, c

  • 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, for Ascend, progress toward the "Ascended

  • 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 exact or inferred. address: an Elysium

  • get_token_security

    Is this HyperEVM or Elysium ERC-20 safe to trade: a buy, a transfer and a sell simulated on our node through its most liquid pool (state overrides, nothing sent): canBuy, canSell, buy / sell / transfer tax, gas, revert reason; static checks of its code (owner and renounced, minta

  • get_prices

    Current USD price of up to 100 tokens in one call, each with its source and provenance: hl_mid (HYPE / WHYPE: HyperCore spot mid; hl_oracle when no mid is recorded), hl_spot (HyperCore tokens and HyperEVM tokens linked to one: last trade of its USDC market), hl_perp, unit (USDC),

  • get_price_history

    USD prices in the past. With at (Unix ms): the price of up to 100 tokens at that time (last observation at or before it). With from / to / interval: USD closes per unit (1m 5m 15m 1h 4h 1d) of up to 25 tokens, gap-filled. Same sources as get_prices. Windows over 30 days are bille

  • get_tokens

    Metadata of up to 100 tokens: symbol, name, decimals, total supply, creator and creation time, logo, description and socials (website, X, Telegram, Discord, docs) with the source of each field and the X / Telegram handles in `profile` (issuer-provided, unverified text), token fam

  • get_token_overview

    One token across all its pools on HyperEVM or Elysium (DexScreener style): USD price and source, FDV, market cap, liquidity, volume / trades / buys / sells / unique buyers, sellers and traders / price change over 5m, 1h, 6h, 24h, holders and top-10 share, pool count, the 5 best p

  • get_token_traders

    Who traded a HyperEVM or Elysium token over 1h, 6h, 24h or since launch (window=all), over all its pools or one (pool), and how they did, or one wallet's line (trader): per wallet buys / sells, amounts and USD bought / sold, average buy and sell price, current balance and supply

  • 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; route arb_core: deposits and withdrawals of the na

  • 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 across the layers, latest events (fills, le

  • get_wallet_pnl

    One wallet's positions on HyperEVM or Elysium and how it did: per token balance, average cost, cost of what it holds, bought / sold amounts and USD, realized and unrealized PnL at the current price, first buy, last trade (pools=true: per pool too); totals for 1d / 7d / 30d / all:

  • get_wallet_lp_positions

    One wallet's liquidity positions on the DEXs followed position by position (HyperSwap V3 and V2 on HyperEVM): position NFTs, positions opened on a pool directly, LP tokens, and positions a vault holds for it (custody: delegated). Per position: pool, tokens, range (ticks), liquidi

  • get_wallet_value_history

    The USD value of one address on HyperEVM or Elysium over time: window 1d (5 min points), 7d (hourly), 30d or all (daily), then the head. Exact balances at each point (our archive node + the stored transfers), prices as get_price_history. Spam and unpriced tokens left out. Heavy f

  • get_balances

    What an address holds, one flat list: HyperCore spot tokens (live), HyperEVM and Elysium ERC-20s and native HYPE (indexed head), each with raw units, amount, USD price and value, largest first; spam tokens left out; HyperCore perp accounts (account value, withdrawable) apart in `

  • get_token_balance

    The balance of one token for one address: HyperCore coin name (USDC, HYPE…), or a HyperEVM / Elysium token address (`native` = HYPE; layer hyperevm unless elysium is given). 0 when not held. block / at for a past balance, verify to compare with the node.

  • 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, newest first (from, to, amount, block, tx). address: the transfers sent / received by a wallet (direction in, out or any), optionally of one token, in a window (from / to, Unix ms) or above minUsd (amount × current token price); each row with token, symbol

  • get_pool

    One DEX pool of HyperEVM or Elysium: dex, factory, fee tier, hooks, tokens with USD prices, creation block / tx, price, liquidity with its USD value and how it is measured (pool balances for V2 / V3; for V4 / Infinity pools what their positions hold at the current price), depth t

  • list_pool_metrics

    The pools of a DEX with their numbers (HyperSwap V3 and V2 on HyperEVM): what each pool holds and its USD value (TVL), and over 24h, 7d and 30d its swaps, volume, fees paid, the liquidity providers' and the protocol's parts, and its fee APR (LP fees over the tokens held through t

  • get_pool_metrics_history

    One pool's metrics over time (HyperSwap V3 and V2 on HyperEVM): per hour or per UTC day its swaps, volume, fees paid, the liquidity providers' and the protocol's parts (USD at each swap's own price), the tokens it held at the end of the unit (raw units: divide by 10^decimals) wit

  • get_wallet_mev

    Every sandwich (MEV) of a wallet's Elysium swaps, newest first: the bot, its front-run and back-run transactions, the pool and tokens, what the victim paid and got, its loss in USD; with the totals (sandwiches, USD lost, USD of the swaps hit). strict = front-run in the victim's b

  • list_sandwiches

    Sandwich attacks found on Elysium, newest first, one row per victim swap: confidence (strict / probable), the victim and the bot, the pool and tokens, front-run / victim / back-run transactions and blocks, what the victim paid and lost in USD, the bot's profit, tips. Filters: vic

  • get_mev_stats

    MEV on Elysium over 24h, 7d, 30d or all: sandwiches (count, USD taken, victims, bots, USD of the swaps hit), cyclic arbitrage (txs, profit USD), an hourly or daily series, and the top bots, pools and routers hit.

  • list_mev_bots

    The sandwich bots of Elysium over 24h, 7d, 30d or all, most USD taken first: contracts, first / last seen, sandwiches, USD taken, victims, pools, median tip (wei).

  • get_mev_bot

    One Elysium sandwich bot over all its sandwiches: its contracts, first / last seen, sandwiches, USD taken, distinct victims and pools, median tip (wei). Its sandwiches: list_sandwiches with bot.

  • get_transaction

    One transaction by hash, HyperEVM then Elysium (or layer): status, block, from / to, value, gas and fee (HYPE and USD), decoded ERC-20 transfers, swaps, liquidity events, pools created and NFT transfers, the raw logs we do not decode (from our node), and when it is a bridge leg i

  • get_gas

    HyperEVM or Elysium gas over 1h, 6h, 24h or 7d: each block's base fee, gas used and limit, transactions and priority fees (p50 / p90 tips), HyperEVM small and big blocks as two series (each has its own base fee). Stats per series (base fee min / median / p90 / p99 / max / mean, t

  • get_chain_activity

    HyperEVM or Elysium activity per bucket (1m, 15m, 1h or 1d), oldest first: user transactions, distinct wallets and new wallets, contracts created, fees in HYPE, swaps, traders, volume in USD, launches, ERC-20s created, and deposits bridged in from the parent chain (count, deposit

  • get_block

    One HyperEVM or Elysium block (a number, or latest): hash, time, small or big block (HyperEVM), gas, base fee, tips, HYPE burnt and fees, and every transaction in order with sender, recipient (named wallets tagged), HYPE sent, function called, status, gas, tip, fee and its decode

  • elysium_rpc

    One JSON-RPC call on our Elysium mainnet (chain 99901) node, free: eth_chainId, eth_blockNumber, net_version, net_listening, web3_clientVersion, eth_syncing, eth_getBlockByNumber, eth_getBlockByHash, eth_getBlockTransactionCountByNumber, eth_getBlockTransactionCountByHash, eth_ge

  • hyperevm_rpc

    One JSON-RPC call on our HyperEVM (chain 999) node, free: eth_chainId, eth_blockNumber, net_version, net_listening, web3_clientVersion, eth_syncing, eth_getBlockByNumber, eth_getBlockByHash, eth_getBlockTransactionCountByNumber, eth_getBlockTransactionCountByHash, eth_getTransact

  • get_transaction_status

    Where one transaction is on HyperEVM or Elysium (layer): pending with the upstreams that accepted it, included (block, index, success or reverted), replaced (the hash that took its nonce) or dropped, for a transaction sent through hyperevm_rpc / elysium_rpc or POST /v1/ /rpc; any

  • list_sent_transactions

    The transactions this account sent through hyperevm_rpc / elysium_rpc or POST /v1/ /rpc in the last 24 hours (layer; from: up to 10 sender addresses), newest first, each pending (with the upstreams that accepted it), included, replaced or dropped. Never another account's.

  • 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. depth 1: the best bid and offer (BBO) only.

  • get_walls

    Which HyperCore accounts' order book walls hold: per account, its large resting orders placed away from the price (≥ $25k, ≥ 20 bps away), how many the price came to, how many held (filled) and how many were pulled as the price came, with the hold rate. A low hold rate over many

  • get_wall_events

    One HyperCore market's large resting orders that the price came to, one by one, newest first: held (filled) or pulled (cancelled as the price came), with time, price, size, value, life and owner. A wall: a resting limit order (Gtc or Alo, not a trigger) worth at least $25k, place

  • get_open_interest

    Open interest of a HyperCore perp over time (bars of 1s to 1M since 2023-05-20, 1s and 15s since 2025-09-28): open / high / low / close of the open interest (size, Σ |position| of longs and shorts), its value at the last price, longs and shorts opened and closed in each bar, the

  • list_open_interest

    Open interest of every HyperCore perp now (main dex and HIP-3): size and USD value, accounts long and short, change over 1 h, 24 h and 7 d, totals per perp dex. Sort by value, size, 24 h change or accounts. Exact, from every fill and hourly funding.

  • get_open_interest_cohorts

    Who holds a HyperCore perp's open interest, every hour since 2025-09-28: long and short size and accounts by position size tier (0 = no trade price known, 1 = under $10k, 2 = $10k–100k, 3 = $100k–1M, 4 = $1M–10M, 5 = $10M and more), and the share of the 10 largest longs and short

  • get_open_interest_opens

    Who opened positions on a HyperCore perp in a window of up to a day (since 2025-03-22 10:49 UTC): the orders that opened longs or shorts, largest value first, with the account and its named wallet, size and value opened, average price, taker or resting, position before and after;

  • 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 coin) is clamped, the answer's `from` s

  • 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, current to a few seconds (the node state rolled forward with every fill, funding payment, ledger update and accepted account action): account, size, side, entry price, notional, unrealized PnL at the mark, leverage, margin mode and liquidatio

  • get_position_changes

    Past HyperCore perp position changes of one coin over a notional (at least 10000), one row per account and block (opens, closes, increases, reductions, flips, with size, average price and whether a liquidation moved it): the history of the WS hc.positions channel, the rows behind

  • get_position_flow

    Large HyperCore perp position moves and liquidations of one coin summed per bar of a unit (1m to 1d, 1w, 1M): buys, sells, longs liquidated, shorts liquidated, each with notional, count, volume-weighted price and the largest move (named wallet when known). The figures add up acro

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ! 注意

    作者与仓库一致

    注册中心没有列出源代码仓库,因此无法将发布者(femtos.xyz)与代码对应起来

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 300 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 60 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/xyz-femtos-mcp.svg)](https://mcp.popnx.com/en/servers/xyz-femtos-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“网络安全”中的其他服务器比较i

  • 星标数多于此分类中其他 1124 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1124 个服务器的 77% 更新
  • 基础检查结果等于或优于此分类中其他 1124 个服务器的 45%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Femtos 安全吗?

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.2.1)于10天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:GitHits, Dependency Management MCP Server, Snyk MCP, TokenSafe, Draugr

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

作者:githits-com正在增长↓ 3807/周★ 138昨天更新

电脑或云端✓ 服务方 · githits.com

Snyk MCP

Easily find and fix security issues in your applications leveraging Snyk platform capabilities.

作者:snyk广泛使用↓ 76.2万/周★ 617个月前更新

在你的电脑上运行✓ 服务方 · snyk.io

TokenSafe

Your AI agent is smart enough to code all day. Local firewall & zero-loss runtime.

作者:tokensafe-dev广泛使用↓ 6785/周★ 47今天更新

电脑或云端✓ 服务方 · tokensafe.dev

Draugr

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

作者:draugr-dev起步阶段★ 303天前更新

在你的电脑上运行✓ 服务方 · draugr.dev
与相似项目对比
本项
Femtos
GitHitsDependency Management MCP ServerSnyk MCPTokenSafeDraugr
运行位置在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装需要安装在电脑上云端或安装在电脑上都可以需要安装在电脑上
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查2/35/53/43/35/53/3
许可证–Apache-2.0–Apache-2.0MITApache-2.0
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

仓库中没有找到 README