Femtos MCP server
xyz.femtos/mcpfemtos.xyzstreamable-httpv1.2.1Scanned
Hyperliquid data on HyperCore, HyperEVM, Elysium: balances, prices, trades, token security, bridges
114 tools: 6 can delete or cancel things, 6 do something that can't be undone, 20 change things and 82 only read.
- Reads private data · 2
- Reads text others write · 15
- Can send data out · 5
- 11 findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here can delete or cancel things and 6 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Femtos MCP server can do
The Femtos MCP server is published by femtos.xyz, a domain the MCP Registry verified. It has 114 tools. It can delete or cancel things (6 tools: delete_webhook, cancel_plan, rotate_key, freeze_key and 2 more), do things that cannot be undone, such as sending, paying or publishing (get_open_interest, get_nft_transfers, get_builder_fills, replay_webhook and 2 more) and create or change data (20 tools: elysium_rpc, hyperevm_rpc, list_open_interest, get_positions and 16 more). 82 tools only read.
2 tools read private data (get_token_security and get_deploys); 15 tools bring in text other people can write (hyperevm_rpc, get_nft_tokens, create_webhook and 12 more); 5 tools can send data out of your system (get_open_interest, get_builder_fills, create_webhook and 2 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 11 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
114 tools
Deletes or cancels 6Claude Code: deny
cancel_planStop your plan from renewing: it runs to its period end (no refund), then the key is back on pay as you go.1 finding
Why it is in this group
- The name "cancel_plan" says "cancel": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "cancel_plan" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "cancel_plan" says "cancel": a word for removing or ending something.
Description, as the server wrote it Stop your plan from renewing: it runs to its period end (no refund), then the key is back on pay as you go. subscribe_plan before then resumes it. Free.
Annotations the server declares
- title: Cancel your plan
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
delete_accountDelete your account: the key stops working for good.No findings
Why it is in this group
- The name "delete_account" says "delete": a word for removing or ending something.
- The description says "Cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete your account: the key stops working for good. Refused while a plan runs or overage is due; a positive balance is lost only with forfeit_balance=true. Needs management_secret (agents); an account with an email gets a confirmation link. Cannot be undone.
Annotations the server declares
- title: Delete your account
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
delete_webhookDelete one of your webhooks and its pending deliveries.No findings
Why it is in this group
- The name "delete_webhook" says "delete": a word for removing or ending something.
- The description says "Cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete one of your webhooks and its pending deliveries. Cannot be undone.
Annotations the server declares
- title: Delete a webhook
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
freeze_keyEmergency stop for a leaked key: it is refused everywhere at once, this MCP connection included.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Emergency stop for a leaked key: it is refused everywhere at once, this MCP connection included. Unfreeze or rotate it after with your management secret (POST /v1/account/unfreeze, /v1/account/rotate). Free.
Annotations the server declares
- title: Freeze your key
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
recover_accountNo key needed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it No key needed. Send wallet, nonce and the signature of the recovery message: answers a new key and management secret (save both), the old ones stop working.
Annotations the server declares
- title: Recover an x402 account
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
rotate_keyReplace your API key: the new one is answered once, the current one (the one this MCP connection uses) stops working at once: reconnect with the new key.No findings
Why it is in this group
- The description's first verb is "replace": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Replace your API key: the new one is answered once, the current one (the one this MCP connection uses) stops working at once: reconnect with the new key. Needs management_secret (agents); an account with an email gets a confirmation link instead. Free.
Annotations the server declares
- title: Rotate your key
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 6Claude Code: ask
get_builder_fillsFills of one HyperCore builder code, newest first, with the builder fee of each, account, market, price, size, direction, PnL, oid, tid and hash.Can send data out1 finding
Why it is in this group
- The name "get_builder_fills" says "get": a word for reading.
- The description's first verb is "fill": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "get_builder_fills" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_builder_fills" says "get": a word for reading.
Description, as the server wrote it Fills of one HyperCore builder code, newest first, with the builder fee of each, account, market, price, size, direction, PnL, oid, tid and hash. From 2025-07-19; window from / to, default the last 24 h, at most 24 h per call. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Builder fills
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_nft_transfersTransfers (mints and burns included) of one collection or one of its tokens, newest first: from, to, token id, amount, block, tx.1 finding
Why it is in this group
- The name "get_nft_transfers" says "get": a word for reading.
- The description's first verb is "transfer": a word for a change that another call does not undo.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_nft_transfers" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_nft_transfers" says "get": a word for reading.
Description, as the server wrote it 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_cursor` as cursor.
Annotations the server declares
- title: NFT transfers
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_open_interestOpen 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 …Can send data out1 finding
Why it is in this group
- The name "get_open_interest" says "get": a word for reading.
- The description's first verb is "open": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "get_open_interest" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_open_interest" says "get": a word for reading.
Description, as the server wrote it 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 part opened by aggressors, the size liquidated, accounts long and short, the hourly funding rate settled. Exact after every block since 2025-03-22 10:49 UTC, from every trade and Hyperliquid's own per-minute values (anchored on every hourly funding since 2025-09-28, where accounts start); before, Hyperliquid's per-minute values alone, moves and trades null. Hyperliquid's API serves only the current open interest.
Annotations the server declares
- title: Open interest history of a perp
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
pay_with_walletStep 2: send chain, authorization (the quote typedData.message), signature, and the planId / interval or usd of the quote.Reads text others writeNo findings
Why it is in this group
- The name "pay_with_wallet" says "pay": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Step 2: send chain, authorization (the quote typedData.message), signature, and the planId / interval or usd of the quote. Femtos settles it on chain (no gas for you) and credits the account or buys the plan. state pending: call again with the same body after retryAfter (never charged twice). Spends money. Free.
Annotations the server declares
- title: Pay from your wallet
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
quote_wallet_paymentStep 1 of paying from an EVM wallet with USDC (Base, Arbitrum One or HyperEVM), no gas: the EIP-712 typed data of a USDC TransferWithAuthorization to sign with eth_signTypedData_v4…Reads text others writeNo findings
Why it is in this group
- The name "quote_wallet_payment" says "payment": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Step 1 of paying from an EVM wallet with USDC (Base, Arbitrum One or HyperEVM), no gas: the EIP-712 typed data of a USDC TransferWithAuthorization to sign with eth_signTypedData_v4, for a plan (planId, interval: what the balance lacks) or a top-up (usd). Then pay_with_wallet with the signature. Free.
Annotations the server declares
- title: Pay from your wallet: quote
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
replay_webhookSend deliveries again, same webhook-id (dedupe on it): one (msgId, delivered or dead), or every dead one since a time (since, Unix ms within 7 days; status all: delivered ones too)…Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Send deliveries again, same webhook-id (dedupe on it): one (msgId, delivered or dead), or every dead one since a time (since, Unix ms within 7 days; status all: delivered ones too).
Annotations the server declares
- title: Replay webhook deliveries
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 20Claude Code: ask
create_webhookCreate an outgoing webhook: we POST the events of its subscriptions to your HTTPS URL (port 443 or 8443, public address), signed (Standard Webhooks: webhook-id, webhook-timestamp, …Reads text others writeCan send data outNo findings
Why it is in this group
- The name "create_webhook" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Create an outgoing webhook: we POST the events of its subscriptions to your HTTPS URL (port 443 or 8443, public address), signed (Standard Webhooks: webhook-id, webhook-timestamp, webhook-signature = v1,<base64 HMAC-SHA256 of "id.timestamp.body" with the secret>). Channels (WebSocket vocabulary): bridge.transfers and elysium.bridge (matched bridge legs), wallet (filter.address: up to 100 addresses, filter.channel: event kinds), hc.liquidations and hc.positions (filter.min_notional; positions >= 10000), elysium.launches, hyperevm.launches. Your URL first gets a webhook.verification POST: answer {"challenge": "<data.challenge>"} within 10 s, nothing else is sent before. The answer carries the secret once. Free tier: 2 webhooks, 5 subscriptions, 10k deliveries a day.
Annotations the server declares
- title: Create a webhook
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
elysium_rpcOne 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, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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_getTransactionByHash, eth_getTransactionByBlockNumberAndIndex, eth_getTransactionByBlockHashAndIndex, eth_getTransactionReceipt, eth_getBlockReceipts, eth_getBalance, eth_getCode, eth_getStorageAt, eth_getTransactionCount, eth_call, eth_estimateGas, eth_gasPrice, eth_maxPriorityFeePerGas, eth_feeHistory, eth_getLogs, eth_getProof; eth_sendRawTransaction from 2026-12-24 (until then, send on POST https://api.femtos.xyz/v1/elysium/rpc). The answer is the node's {jsonrpc, id, result} or {error}. eth_getLogs over at most 1000 blocks; state (eth_call, eth_getBalance…) of the last 128 blocks only. Limits of your key's plan (no key: 5/s per IP): use the indexed tools for history.
Annotations the server declares
- title: Elysium JSON-RPC
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
enable_webhookTurn a disabled webhook (410 Gone, or failing for 24 h) on again: your URL gets a new webhook.verification challenge, deliveries resume once it is answered; pending ones are kept 7…Reads text others writeNo findings
Why it is in this group
- The name "enable_webhook" says "enable": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Turn a disabled webhook (410 Gone, or failing for 24 h) on again: your URL gets a new webhook.verification challenge, deliveries resume once it is answered; pending ones are kept 7 days.
Annotations the server declares
- title: Turn a webhook on again
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
get_deposit_addressYour USDC deposit address (created on the first call, then the same): send USDC on HyperCore (usdSend), HyperEVM, Base or Arbitrum One (ERC-20 transfer) and it is credited 1:1 to y…1 finding
Why it is in this group
- The name "get_deposit_address" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "get_deposit_address" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_deposit_address" says "get": a word for reading.
Description, as the server wrote it Your USDC deposit address (created on the first call, then the same): send USDC on HyperCore (usdSend), HyperEVM, Base or Arbitrum One (ERC-20 transfer) and it is credited 1:1 to your balance. Answers how to pay on each chain. Free.
Annotations the server declares
- title: Your USDC deposit address
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_forced_flowOpen stop-loss / take-profit orders and the liquidation prices of open positions of one HyperCore market on the same price buckets: per bucket the stops by kind and side (each at w…1 finding
Why it is in this group
- The name "get_forced_flow" says "get": a word for reading.
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_forced_flow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_forced_flow" says "get": a word for reading.
Description, as the server wrote it Open stop-loss / take-profit orders and the liquidation prices of open positions of one HyperCore market on the same price buckets: per bucket the stops by kind and side (each at what it would execute: a reduce-only order at most what is left of its wallet's position, the rest under stops.unbacked), the liquidations by side, the cascade (what fires with the move: sell = sell stop-losses + long liquidations, buy = buy stop-losses + short liquidations) and forced = cascade + take-profits (which fire against the move: sell ones above the mark, buy ones below), each with its running total from the mark outward (cumCascadeSell / cumSell downward, cumCascadeBuy / cumBuy upward); summary = cascade selling under the mark and buying over it, take-profits on the far side, and the forced totals, inside the grid. Same grid parameters as get_stop_map.
Annotations the server declares
- title: Forced flow map (stops + liquidations)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_payment_optionsHow to pay your account now: your USDC deposit address on each chain with exact instructions, x402 credit packs, a card checkout URL when cards are offered (give usd), and the cred…Reads text others write1 finding
Why it is in this group
- The name "get_payment_options" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "get_payment_options" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_payment_options" says "get": a word for reading.
Description, as the server wrote it How to pay your account now: your USDC deposit address on each chain with exact instructions, x402 credit packs, a card checkout URL when cards are offered (give usd), and the credits an amount buys. Free.
Annotations the server declares
- title: How to add credit
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
get_positionsOpen 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,…1 finding
Why it is in this group
- The name "get_positions" says "get": a word for reading.
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_positions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_positions" says "get": a word for reading.
Description, as the server wrote it 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 liquidation price when known. Sort by notional (default), upnl or liqDistance (closest to liquidation first). Named wallets carry `entity`.
Annotations the server declares
- title: Open positions
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_stop_mapOpen trigger orders (stop-loss and take-profit) of one HyperCore market bucketed by trigger price around the mark (default ±10 %, 20 round-width buckets): per bucket the count, siz…1 finding
Why it is in this group
- The name "get_stop_map" says "get": a word for reading.
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_stop_map" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_stop_map" says "get": a word for reading.
Description, as the server wrote it Open trigger orders (stop-loss and take-profit) of one HyperCore market bucketed by trigger price around the mark (default ±10 %, 20 round-width buckets): per bucket the count, size and notional (size × trigger price) of stops and take-profits, sell (closes longs) and buy (closes shorts), market and limit. Each order counts at what it would execute: a reduce-only order closes at most what is left of its wallet's position when it fires (positions a few seconds old); the size past it (wallets with no position, oversized or duplicate stops) is apart under `unbacked`. Position TP/SL that close the whole position (size 0) are counted apart under `whole`, sized the same way. `totals` cover every open trigger order of the coin, `below` / `above` those outside the grid. Cut at `height` (block) / `asOf`.
Annotations the server declares
- title: Stop-loss / take-profit map
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_triggered_stopsStop-loss and take-profit orders of one HyperCore market that fired, newest first: wallet, side, trigger and limit price, size (0 = whole position), the order the trigger placed (i…1 finding
Why it is in this group
- The name "get_triggered_stops" says "get": a word for reading.
- The description's first verb is "stop": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_triggered_stops" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_triggered_stops" says "get": a word for reading.
Description, as the server wrote it Stop-loss and take-profit orders of one HyperCore market that fired, newest first: wallet, side, trigger and limit price, size (0 = whole position), the order the trigger placed (its status in the trigger block) and its fills there (size, average price, notional). Window: since / until, default the last hour, at most 24 h per call and 7 days back. Named wallets carry `entity`. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Triggered stops
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
hyperevm_rpcOne 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_getBl…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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_getTransactionByHash, eth_getTransactionByBlockNumberAndIndex, eth_getTransactionByBlockHashAndIndex, eth_getTransactionReceipt, eth_getBlockReceipts, eth_getBalance, eth_getCode, eth_getStorageAt, eth_getTransactionCount, eth_call, eth_estimateGas, eth_gasPrice, eth_maxPriorityFeePerGas, eth_feeHistory, eth_getLogs, eth_getProof, and eth_sendRawTransaction (a transaction you signed, sent on to the chain; its answer is the hash). The answer is the node's {jsonrpc, id, result} or {error}. eth_getLogs over at most 1000 blocks; state (eth_call, eth_getBalance…) of the last 128 blocks only. Limits of your key's plan (no key: 5/s per IP): use the indexed tools for history.
Annotations the server declares
- title: HyperEVM JSON-RPC
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
kol_activityLatest moves of named wallets, newest first: HyperCore fills (minNotional USD, default 1000), HyperEVM / Elysium swaps and transfers.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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_cursor` as cursor.
Annotations the server declares
- title: Named-wallet moves
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
kol_leaderboardNamed wallets ranked by their trading on a layer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Named-wallet leaderboard
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
kol_positioningHow named wallets (KOLs, funds, market makers; or smart-money clusters with kind=cluster) are positioned on each HyperCore perp: long vs short notional and entity counts, net, aver…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it How named wallets (KOLs, funds, market makers; or smart-money clusters with kind=cluster) are positioned on each HyperCore perp: long vs short notional and entity counts, net, average entry and unrealized PnL per side, the named position closest to liquidation, the largest entities per side, and the net change over 1 h and 24 h. One market with coin.
Annotations the server declares
- title: Named-wallet positioning per market
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_open_interestOpen 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.1 finding
Why it is in this group
- The name "list_open_interest" says "list": a word for reading.
- The description's first verb is "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "list_open_interest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "list_open_interest" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Open interest of every perp
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
rotate_webhook_secretA new whsec_ signing secret, answered once; for 24 h every delivery carries two signatures (the new and the previous secret): accept either while you switch.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it A new whsec_ signing secret, answered once; for 24 h every delivery carries two signatures (the new and the previous secret): accept either while you switch.
Annotations the server declares
- title: Rotate a webhook secret
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
set_spending_capSet your monthly spending cap in USD (null lifts it).No findings
Why it is in this group
- The name "set_spending_cap" says "set": a word for a change.
Description, as the server wrote it Set your monthly spending cap in USD (null lifts it). Past it, heavy and medium calls answer 402 until next month. Answers the billing view. Free.
Annotations the server declares
- title: Set your spending cap
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
signupNo key needed.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it No key needed. Step 2: send agent_name with the solved salt and nonce; answers a free API key and a management secret, each once: save both (the secret rotates, unfreezes and deletes the account). Then connect with Authorization: Bearer <key>.
Annotations the server declares
- title: Get a key
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
subscribe_planSubscribe to a plan (get_plans lists them): paid from your USDC balance now (interval month, or year = 12 months prepaid at a discount) and renewed from it, or by card (checkout UR…Reads text others writeNo findings
Why it is in this group
- The name "subscribe_plan" says "subscribe": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Subscribe to a plan (get_plans lists them): paid from your USDC balance now (interval month, or year = 12 months prepaid at a discount) and renewed from it, or by card (checkout URL). Spends money. 402 insufficient_balance says how much to deposit. Free.
Annotations the server declares
- title: Subscribe to a plan
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
test_webhookQueue a webhook.test delivery to a verified webhook (not billed); its result shows in get_webhook_deliveries within seconds.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Queue a webhook.test delivery to a verified webhook (not billed); its result shows in get_webhook_deliveries within seconds.
Annotations the server declares
- title: Test a webhook
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
update_webhookChange a webhook: url (verified again by a webhook.verification challenge before anything else is sent), description, or subscriptions (the whole list: unchanged ones keep their se…Reads text others writeCan send data outNo findings
Why it is in this group
- The name "update_webhook" says "update": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Change a webhook: url (verified again by a webhook.verification challenge before anything else is sent), description, or subscriptions (the whole list: unchanged ones keep their seq).
Annotations the server declares
- title: Change a webhook
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 82Show 82 read-only tools
get_accountYour Femtos account: name, tier and limits in force, balance and debt (USD), credits used this month and free credits left, monthly cap, plan and renewal, how to pay (USDC deposit …No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it Your Femtos account: name, tier and limits in force, balance and debt (USD), credits used this month and free credits left, monthly cap, plan and renewal, how to pay (USDC deposit address, card, x402), how rotate/delete are confirmed (manageWith). Start here to manage the account. Free.
Annotations the server declares
- title: Your account
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_balancesWhat 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, l…No findings
Why it is in this group
- The name "get_balances" says "get": a word for reading.
Description, as the server wrote it 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 `perp`; totals per layer and overall, each layer with its source, height and asOf. Past balances: block or at (Unix ms) on one layer (EVM: needs tokens, read on our archive node; HyperCore: the holder snapshot at or before it, 7 days kept). verify: EVM rows read again on the node at the same block (indexer drift shows as onchain.match false).
Annotations the server declares
- title: Token balances
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_blockOne 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…No findings
Why it is in this group
- The name "get_block" says "get": a word for reading.
Description, as the server wrote it 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 decoded swaps, transfers and liquidity changes.
Annotations the server declares
- title: One block
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_bookLive 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.No findings
Why it is in this group
- The name "get_book" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Order book
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_bridgesBridge movements, newest first, with 24 h stats.No findings
Why it is in this group
- The name "get_bridges" says "get": a word for reading.
Description, as the server wrote it 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 account to follow one wallet across layers. Medium call.
Annotations the server declares
- title: Bridge movements
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_builderOne HyperCore builder code over a window (24h to all since 2025-07-19): fees (USD stablecoins at par, exact per token), volume, fills, users, rank; one row per day; its markets; it…No findings
Why it is in this group
- The name "get_builder" says "get": a word for reading.
Description, as the server wrote it One HyperCore builder code over a window (24h to all since 2025-07-19): fees (USD stablecoins at par, exact per token), volume, fills, users, rank; one row per day; its markets; its orders from 2026-10-13 15:50 UTC by status (fills, cancels, each rejection reason) and the fee rates they charged.
Annotations the server declares
- title: One builder code
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_builder_ordersOrder statuses of one HyperCore builder code, newest first: open, filled, canceled, triggered and every rejection reason, with market, side, type, prices, sizes, account and the fe…No findings
Why it is in this group
- The name "get_builder_orders" says "get": a word for reading.
Description, as the server wrote it Order statuses of one HyperCore builder code, newest first: open, filled, canceled, triggered and every rejection reason, with market, side, type, prices, sizes, account and the fee rate charged. From 2026-10-13 15:50 UTC; window from / to, default 24 h, at most 7 days per call. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Builder orders
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_buildersHyperCore builder codes ranked over a window (24h, 7d, 30d, 90d, all since 2025-07-19): builder fees earned (USD stablecoins at par, exact per token), volume, fills, distinct users…No findings
Why it is in this group
- The name "get_builders" says "get": a word for reading.
Description, as the server wrote it HyperCore builder codes ranked over a window (24h, 7d, 30d, 90d, all since 2025-07-19): builder fees earned (USD stablecoins at par, exact per token), volume, fills, distinct users, share of all builder fees, and order outcomes (distinct orders, filled, canceled, rejected; from 2026-10-13 15:50 UTC), and the app behind each code (Phantom, MetaMask…) when known. Sort by fees, volume, fills, users or orders.
Annotations the server declares
- title: Builder codes ranked
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_candlesOHLCV candles of one market, ascending, UTC-aligned.No findings
Why it is in this group
- The name "get_candles" says "get": a word for reading.
Description, as the server wrote it 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). Or token instead of market: a token's candles in USD through its reference pool (most liquid; the answer names it), HyperCore: its USDC market. Without from: the `limit` candles ending now. Windows over 30 days are billed as heavy calls.
Annotations the server declares
- title: OHLCV candles
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_chain_activityHyperEVM 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, vol…No findings
Why it is in this group
- The name "get_chain_activity" says "get": a word for reading.
Description, as the server wrote it 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, depositors, USD). The last bucket is the open one (`partial`). Ask 1d for a trend over weeks, 1h for days, 15m or 1m for the last hours.
Annotations the server declares
- title: Chain activity
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_coinOne token: its links across layers, the markets it trades on (most traded first) and its 5 largest holders.No findings
Why it is in this group
- The name "get_coin" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: One token
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_deploysHyperCore deploy actions, newest first: `perpDeploy` (HIP-3 perp dexs: market registrations, halts, funding rates, open interest caps, margin tables, sub-deployers…), `spotDeploy` …Reads private dataNo findings
Why it is in this group
- The name "get_deploys" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "table": it reads databases.
Description, as the server wrote it HyperCore deploy actions, newest first: `perpDeploy` (HIP-3 perp dexs: market registrations, halts, funding rates, open interest caps, margin tables, sub-deployers…), `spotDeploy` (HIP-1 tokens and spot pairs), `outcomeDeploy` and `activateOutcomeDeployer` (HIP-4 outcomes), `VoteGlobalAction` (validator votes: `J` lists a main-dex perp), with account, signers, status and the exchange's answer; the action as the node wrote it, every digit (a named wallet's address: its handle). Filters: kind, variant, dex, coin, user, status; notable: true leaves out the routine actions (funding interest rates, outcomes registered from a template, every outcome settlement, the validators' votes registering and settling outcomes and questions). Window from / to, default the last 24 h, at most 31 days per call, since 2026-11-01. head: the newest block the history has read; pending: blocks of the window it does not hold yet. Named wallets carry `entity`. Next page: pass `next_cursor` as cursor (same window).
Annotations the server declares
- title: HyperCore deploy actions
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_depositsYour USDC deposit address on each chain (HyperCore, HyperEVM, Base, Arbitrum One), amounts waiting to reach the minimum, and its latest deposits: amount, tx, pending / credited / i…No findings
Why it is in this group
- The name "get_deposits" says "get": a word for reading.
Description, as the server wrote it Your USDC deposit address on each chain (HyperCore, HyperEVM, Base, Arbitrum One), amounts waiting to reach the minimum, and its latest deposits: amount, tx, pending / credited / ignored with the reason. Free.
Annotations the server declares
- title: Your USDC deposits
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_entity_graphHow each wallet of a named entity was attributed: the links (bridges, HyperCore sub-accounts, sends both ways, Farcaster self-declarations) back to the public source, with their pr…No findings
Why it is in this group
- The name "get_entity_graph" says "get": a word for reading.
Description, as the server wrote it How each wallet of a named entity was attributed: the links (bridges, HyperCore sub-accounts, sends both ways, Farcaster self-declarations) back to the public source, with their proofs (source, time, USD value, chains), and the HyperCore metrics of smart-money wallets. Use it to judge an attribution before relying on it.
Annotations the server declares
- title: How a named wallet was found
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_entity_pnlThe HyperCore PnL curve of a named entity (id from search_entities): per hour or day, realized PnL, fees, funding, net and cumulative net, over 7d, 30d, 90d or all history.No findings
Why it is in this group
- The name "get_entity_pnl" says "get": a word for reading.
Description, as the server wrote it The HyperCore PnL curve of a named entity (id from search_entities): per hour or day, realized PnL, fees, funding, net and cumulative net, over 7d, 30d, 90d or all history. Realized only: open positions' unrealized PnL is in get_entity's answer.
Annotations the server declares
- title: A named wallet's PnL curve
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_erc20_transfersERC-20 Transfer events, newest first (from, to, amount, block, tx).No findings
Why it is in this group
- The name "get_erc20_transfers" says "get": a word for reading.
Description, as the server wrote it 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, direction and USD value. Without address: the transfers of one token. Filtered pages may hold fewer rows than limit: keep paging with `next_cursor` (null = no more).
Annotations the server declares
- title: ERC-20 transfers (of a token, or from / to an address)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_gasHyperEVM 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 ser…No findings
Why it is in this group
- The name "get_gas" says "get": a word for reading.
Description, as the server wrote it 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, typical tips, utilization) and the latest block. Points are every block up to 25000 per series, else buckets with min / mean / max base fee; ask a coarse resolution (5m, 15m, 1h) for a short answer. Values in wei.
Annotations the server declares
- title: Gas tracker
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_holdersLargest holders of a token and its concentration (top-10 share…); system addresses (pools, bridges, launchpad, zero/dead) counted apart.No findings
Why it is in this group
- The name "get_holders" says "get": a word for reading.
Description, as the server wrote it 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. Named wallets carry `entity`; EVM rows say what each address is (label, labelKind: pool, bridge, protocol, token, creator, multisig, contract, wallet; contract: has code) and what each holder did with the token: pnl (buys / sells since its first swap, average entry price and market cap, realized / unrealized PnL) and tags (dev, sniper, bundler, insider, pro); tagShares = supply held by snipers, bundlers, insiders, pro traders, the creator among the 100 largest (proHolders: how many pro traders).
Annotations the server declares
- title: Token holders
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_holders_historyHow 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 an…No findings
Why it is in this group
- The name "get_holders_history" says "get": a word for reading.
Description, as the server wrote it 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 first snapshot (`since`) on, up to 365 days. interval=1h: one point an hour over the last hours (up to 720), replayed from the token's transfers (a token with more than 20,000 transfers: hourly snapshots, from their start). The hourly count comes from transfers and can differ from `current` for tokens whose balances change without a transfer.
Annotations the server declares
- title: Holder count history
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_hypercore_accountThe HyperCore account of an address (or a named wallet's handle), read from our node at most 2 s ago: perp account value, margin used and withdrawable, each position (size, entry a…No findings
Why it is in this group
- The name "get_hypercore_account" says "get": a word for reading.
Description, as the server wrote it The HyperCore account of an address (or a named wallet's handle), read from our node at most 2 s ago: perp account value, margin used and withdrawable, each position (size, entry and liquidation price, leverage, unrealized PnL, cumulative funding with Hyperliquid's sign: positive = paid), the HIP-3 dex accounts, the spot balances with USD values, and whether the perp collateral is held in spot (`perp.inSpot`). The other layers of the address: get_wallet.
Annotations the server declares
- title: HyperCore account
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_hypercore_wallet_pnlThe HyperCore PnL curve of any address (or a named wallet's handle): per hour or day, realized PnL, fees, funding, net and cumulative net, plus the perp account value at each bucke…No findings
Why it is in this group
- The name "get_hypercore_wallet_pnl" says "get": a word for reading.
Description, as the server wrote it The HyperCore PnL curve of any address (or a named wallet's handle): per hour or day, realized PnL, fees, funding, net and cumulative net, plus the perp account value at each bucket's end and the net transfers in it, over 7d, 30d, 90d or all history. Account values are walked back from our node's state now (standard accounts; unified and portfolio-margin ones get none, accountValue.status says why). Open positions now: get_hypercore_account.
Annotations the server declares
- title: A HyperCore wallet's PnL curve
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_launchThe 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 launchpa…No findings
Why it is in this group
- The name "get_launch" says "get": a word for reading.
Description, as the server wrote it 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" criteria. Elysium first, then HyperEVM LiquidLaunch.
Annotations the server declares
- title: One launch
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_launch_timelineReplayable 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).No findings
Why it is in this group
- The name "get_launch_timeline" says "get": a word for reading.
Description, as the server wrote it 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`).
Annotations the server declares
- title: Launch timeline
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_ledgerYour money movements, newest first: USDC deposits and x402 packs (with tx), card payments, credits by Femtos, plans paid from the balance, refunds; usage debits with usage=true.No findings
Why it is in this group
- The name "get_ledger" says "get": a word for reading.
Description, as the server wrote it Your money movements, newest first: USDC deposits and x402 packs (with tx), card payments, credits by Femtos, plans paid from the balance, refunds; usage debits with usage=true. With the balance now. Next page: pass `next_cursor` as cursor. Free.
Annotations the server declares
- title: Your payments and charges
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_liquidation_mapLiquidation prices of the open perp positions of one HyperCore market, bucketed by price around the mark: per bucket the longs (liquidated by a forced sell as price falls to them) …No findings
Why it is in this group
- The name "get_liquidation_map" says "get": a word for reading.
Description, as the server wrote it Liquidation prices of the open perp positions of one HyperCore market, bucketed by price around the mark: per bucket the longs (liquidated by a forced sell as price falls to them) and the shorts (forced buy), count, |size| and |size| × liquidation price. Real per-position prices: every account's positions a few seconds old (the node state rolled forward with every fill, funding payment, ledger update and accepted account action), each liquidation price from Hyperliquid's formula on the account state, not a leverage model; `coverage` gives the share of open interest that has one (portfolio-margin cross accounts have none). Same grid parameters as get_stop_map: the buckets line up.
Annotations the server declares
- title: Liquidation price map
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_liquidation_statsHyperCore 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…No findings
Why it is in this group
- The name "get_liquidation_stats" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Liquidation stats
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_liquidationsHyperCore 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).No findings
Why it is in this group
- The name "get_liquidations" says "get": a word for reading.
Description, as the server wrote it 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` says where it starts. Named wallets carry `entity`.
Annotations the server declares
- title: Liquidations
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_mev_botOne Elysium sandwich bot over all its sandwiches: its contracts, first / last seen, sandwiches, USD taken, distinct victims and pools, median tip (wei).No findings
Why it is in this group
- The name "get_mev_bot" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: One sandwich bot
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_mev_statsMEV 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 …No findings
Why it is in this group
- The name "get_mev_stats" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: MEV stats
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_nft_collectionOne 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.No findings
Why it is in this group
- The name "get_nft_collection" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: One NFT collection
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_nft_tokensTokens of one collection by token id, ascending: current ERC-721 owner (null for ERC-1155), metadata URI, image URL.Reads text others writeNo findings
Why it is in this group
- The name "get_nft_tokens" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "uri": it reads web pages, which anyone can write.
Description, as the server wrote it Tokens of one collection by token id, ascending: current ERC-721 owner (null for ERC-1155), metadata URI, image URL. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: NFT tokens
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_nfts_ownedNFTs 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.No findings
Why it is in this group
- The name "get_nfts_owned" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: NFTs of a wallet
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_open_interest_cohortsWho 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–…No findings
Why it is in this group
- The name "get_open_interest_cohorts" says "get": a word for reading.
Description, as the server wrote it 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 shorts. Read whale vs retail positioning over time.
Annotations the server declares
- title: Open interest by position size
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_open_interest_opensWho 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 …No findings
Why it is in this group
- The name "get_open_interest_opens" says "get": a word for reading.
Description, as the server wrote it 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; plus the window's longs / shorts opened in total and by aggressors. Use it to explain an open interest jump.
Annotations the server declares
- title: Largest orders that opened positions
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_plansThe price list: credits per call class (and which calls are medium / heavy), pay-as-you-go bands, plans with their monthly and annual price and included credits, payment methods.No findings
Why it is in this group
- The name "get_plans" says "get": a word for reading.
Description, as the server wrote it The price list: credits per call class (and which calls are medium / heavy), pay-as-you-go bands, plans with their monthly and annual price and included credits, payment methods. Use it before subscribe_plan. Free.
Annotations the server declares
- title: Plans and prices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_poolOne 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 ba…No findings
Why it is in this group
- The name "get_pool" says "get": a word for reading.
Description, as the server wrote it 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; virtual reserves of the in-range liquidity for V4 / Infinity pools: not TVL), depth to ±2 %, trades / buys / sells / USD volume / price change over 5m, 1h, 6h, 24h, for V2-style pools the largest LP holders, and how much of its liquidity is burned, locked (until when), free or in contracts.
Annotations the server declares
- title: One pool
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_position_changesPast 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 pr…No findings
Why it is in this group
- The name "get_position_changes" says "get": a word for reading.
Description, as the server wrote it 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's bars. Window: the last 24 h by default, at most 30 days, anywhere since 2025-05-25. sort=notional for the largest of the window. Named wallets carry `entity`.
Annotations the server declares
- title: Large position changes
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_position_flowLarge 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, …No findings
Why it is in this group
- The name "get_position_flow" says "get": a word for reading.
Description, as the server wrote it 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 across units. Floors: minNotional for buys and sells, liqMinNotional for liquidations (at least 10000). History from 2025-05-25.
Annotations the server declares
- title: Large position moves per bar
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_predicted_fundingPredicted hourly funding rate of the running hour for HyperCore perps, main dex and HIP-3 dexes (coin: one perp, dex: one dex, neither: every perp): the rate that will be paid at n…No findings
Why it is in this group
- The name "get_predicted_funding" says "get": a word for reading.
Description, as the server wrote it Predicted hourly funding rate of the running hour for HyperCore perps, main dex and HIP-3 dexes (coin: one perp, dex: one dex, neither: every perp): the rate that will be paid at nextFundingTime if the hour ended now (Hyperliquid's own), the average premium it stands for (null while it sits within clamp of the interest rate), the latest premium, and the terms of the formula (interestRate and clamp per 8 h, multiplier).
Annotations the server declares
- title: Predicted funding rates
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_price_historyUSD prices in the past.No findings
Why it is in this group
- The name "get_price_history" says "get": a word for reading.
Description, as the server wrote it 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 billed as heavy calls.
Annotations the server declares
- title: Token price history (batch)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_price_levelThe wallets behind one price band of a HyperCore market (a bucket of get_forced_flow / get_stop_map / get_liquidation_map: px_lo = its pxLo, px_hi = its pxHi): the open stop-loss /…No findings
Why it is in this group
- The name "get_price_level" says "get": a word for reading.
Description, as the server wrote it The wallets behind one price band of a HyperCore market (a bucket of get_forced_flow / get_stop_map / get_liquidation_map: px_lo = its pxLo, px_hi = its pxHi): the open stop-loss / take-profit orders triggering in it, each with what it would execute (a reduce-only order at most what is left of its wallet's position; the rest as unbackedSz) and the wallet's position, and the open positions liquidated in it (size, entry, leverage, liquidation price). Largest first. Named wallets carry `entity`.
Annotations the server declares
- title: Who sits at a price level
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_pricesCurrent 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 (Hyper…No findings
Why it is in this group
- The name "get_prices" says "get": a word for reading.
Description, as the server wrote it 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), pool (HyperEVM / Elysium: last swap of the token's reference pool, the most liquid one, with block / tx / logIndex). hypercore: tokens = names (HYPE, PURR) or perp coins (BTC).
Annotations the server declares
- title: Token prices (batch)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_recovery_challengeNo key needed.No findings
Why it is in this group
- The name "get_recovery_challenge" says "get": a word for reading.
Description, as the server wrote it No key needed. Lost the key of an account created by an x402 payment? Get the message its paying wallet must sign (personal_sign), then call recover_account. EOA wallets only.
Annotations the server declares
- title: Recover an x402 account: message
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_signup_challengeNo key needed.No findings
Why it is in this group
- The name "get_signup_challenge" says "get": a word for reading.
Description, as the server wrote it No key needed. Step 1 of a free API key for an agent: a proof-of-work challenge. Find a nonce of 1-32 characters [0-9a-zA-Z] such that SHA-256 of "<salt>:<nonce>" starts with `difficulty` zero bits (run code: about 0.5 M hashes), then call signup.
Annotations the server declares
- title: Get a key: challenge
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_statusState of each layer (HyperCore, HyperEVM, Elysium): indexed head block and time, lag behind the chain, live or syncing, Elysium network (mainnet), HyperCore <> HyperEVM bridge matc…No findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Layer status
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_token_balanceThe 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).No findings
Why it is in this group
- The name "get_token_balance" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: One token balance
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_token_lifecycleOne 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, …No findings
Why it is in this group
- The name "get_token_lifecycle" says "get": a word for reading.
Description, as the server wrote it 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 / HyperEVM address, core:<index>, a HyperCore token id or name, or a perp coin (dex:COIN).
Annotations the server declares
- title: Token across the 3 layers
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_token_overviewOne 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…No findings
Why it is in this group
- The name "get_token_overview" says "get": a word for reading.
Description, as the server wrote it 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 pools and the reference one, creator and creation time.
Annotations the server declares
- title: Token overview (all pools)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_token_securityIs 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, …Reads private dataNo findings
Why it is in this group
- The name "get_token_security" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "database": it reads databases.
Description, as the server wrote it 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, mintable, pausable, blacklist, max tx / wallet, cooldown, tax setters, upgradeable proxy, selfdestruct, ownership reclaim, verified source on Sourcify or the Blockscout bytecode database, of the implementation behind a proxy); holders (top 10 share and its part in EOAs, creator / owner share), liquidity and who holds it (LP burned / locked with the unlock time / free / in contracts, V2 LP tokens and V3 / V4 positions). Verdict ok / caution / danger / honeypot with reasons; each check has a severity (info, warn, danger). Cached 60 s per token. Medium call.
Annotations the server declares
- title: Token security / honeypot check
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_token_tradersWho 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 …No findings
Why it is in this group
- The name "get_token_traders" says "get": a word for reading.
Description, as the server wrote it 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 share, realized, unrealized and total PnL (average cost over the window: realized = min(bought, sold) × (avg sell − avg buy); unrealized = what it still holds of its net buy × (current price − avg buy)), first / last swap, named wallets with entity. sort = pnl, realized or volume; totals of the window (traders, buyers, sellers, swaps, volume). Priced swaps only, the token on either side of any pool; trader = the wallet that received or gave the tokens (tx.from when no other). Medium call.
Annotations the server declares
- title: Top traders of a token (PnL)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_token_volumeDaily 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).No findings
Why it is in this group
- The name "get_token_volume" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Daily token volume
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_tokensMetadata of up to 100 tokens: symbol, name, decimals, total supply, creator and creation time, logo / description / socials when indexed (launchpad metadata), token family, cross-l…No findings
Why it is in this group
- The name "get_tokens" says "get": a word for reading.
Description, as the server wrote it Metadata of up to 100 tokens: symbol, name, decimals, total supply, creator and creation time, logo / description / socials when indexed (launchpad metadata), token family, cross-layer links, spam flag. Unknown addresses come back in `missing`.
Annotations the server declares
- title: Token metadata (batch)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_tradesLatest trades of a market, newest first.No findings
Why it is in this group
- The name "get_trades" says "get": a word for reading.
Description, as the server wrote it 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 object {rows, next_cursor, coverage…} as soon as a history filter is given. History (hyperevm / elysium): pass trader (a wallet: every swap it sent), beneficiary (a wallet: every swap that paid it or took its tokens, smart-account swaps sent by a bundler included), pool or token (more than 20 pools: its priced swaps only, `coverage: priced`), optionally side, minUsd (USD at the swap), from / to (Unix ms): newest first, each row with its pool and symbols; filtered pages may hold fewer rows than limit, keep paging with `next_cursor` (null = no more).
Annotations the server declares
- title: Trades / swaps, and swap history of a wallet, pool or token
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_transactionOne 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 cre…No findings
Why it is in this group
- The name "get_transaction" says "get": a word for reading.
Description, as the server wrote it 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 its legs, matched bridge rows and the cross-layer journey it belongs to. A transaction not indexed yet comes from the node (source: rpc, nothing decoded).
Annotations the server declares
- title: One transaction
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_twap_historyHyperCore TWAP orders that ended (finished, terminated, or error with its reason) in a window, newest first, by market (coin) and / or account (user): size, executed size and notio…No findings
Why it is in this group
- The name "get_twap_history" says "get": a word for reading.
Description, as the server wrote it HyperCore TWAP orders that ended (finished, terminated, or error with its reason) in a window, newest first, by market (coin) and / or account (user): size, executed size and notional, average price, what was left undone, start, scheduled end, when and how it ended. Window from / to, default the last 24 h, at most 7 days per call, since 2026-10-13. Named wallets carry `entity`. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Ended TWAPs
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_twapsRunning HyperCore TWAP orders of a market (coin) and / or an account (user), every market when neither is given: side, size, executed size and notional, average price, remaining si…No findings
Why it is in this group
- The name "get_twaps" says "get": a word for reading.
Description, as the server wrote it Running HyperCore TWAP orders of a market (coin) and / or an account (user), every market when neither is given: side, size, executed size and notional, average price, remaining size and notional at the last trade, progress, start and scheduled end, trigger, status; and per market the net TWAP pressure (remaining buys minus remaining sells, in quote units). sort=remaining (default), newest or ending. Named wallets carry `entity`. Ended TWAPs: get_twap_history.
Annotations the server declares
- title: Running TWAPs and TWAP pressure
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_usageYour usage per UTC day and call class (rest, medium, heavy, hl, ws_bytes, webhook): calls or bytes, credits, USD charged.No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it Your usage per UTC day and call class (rest, medium, heavy, hl, ws_bytes, webhook): calls or bytes, credits, USD charged. Free.
Annotations the server declares
- title: Your usage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_wall_eventsOne 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, …No findings
Why it is in this group
- The name "get_wall_events" says "get": a word for reading.
Description, as the server wrote it 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, placed on its passive side at least 20 bps from the last trade (a bid below, an ask above), resting 24 h at most. Tested: the price came to it before it ended. It held when it traded (a fill of the order), wholly or in part, however it ended; it was pulled when its owner cancelled it unfilled (a cancel or a scheduled cancel) with a trade within 10 bps of it, or through it, in the 60 s from its cancel on: as the price came, or just ahead of it (ladders that requote large orders a few seconds ahead of the price are pulled walls, the commonest kind). Up to 24 h per call.
Annotations the server declares
- title: Walls held or pulled on a market
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_walletOne 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 …No findings
Why it is in this group
- The name "get_wallet" says "get": a word for reading.
Description, as the server wrote it 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, ledger, swaps, transfers, bridges), each section with its freshness. Medium call; balances alone: get_balances (a REST call).
Annotations the server declares
- title: Cross-layer wallet
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_fill_barsA wallet's fills on one HyperCore market summed per bar of a unit (1m to 1d, 1w, 1M): per bar its buys and sells (count, size, notional, average price, closed PnL, fees), its posit…No findings
Why it is in this group
- The name "get_wallet_fill_bars" says "get": a word for reading.
Description, as the server wrote it A wallet's fills on one HyperCore market summed per bar of a unit (1m to 1d, 1w, 1M): per bar its buys and sells (count, size, notional, average price, closed PnL, fees), its position on the coin after the bar and whether it was liquidated in it. Only the bars with a fill. Window from / to in Unix ms, or the last `limit` bars. History from 2025-05-25.
Annotations the server declares
- title: A wallet's fills per bar
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_fillsA wallet's HyperCore fills, newest first: market, side, price, size, notional, direction (Open Long, Close Short…), closed PnL, fee, builder fee, oid, tid, hash, the position befor…No findings
Why it is in this group
- The name "get_wallet_fills" says "get": a word for reading.
Description, as the server wrote it A wallet's HyperCore fills, newest first: market, side, price, size, notional, direction (Open Long, Close Short…), closed PnL, fee, builder fee, oid, tid, hash, the position before the fill, and whether it is a liquidation of the wallet. coin: one market; from / to: a window in Unix ms (default everything up to now). History from 2025-05-25. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: A wallet's fills
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_fundingA wallet's HyperCore funding payments, newest first: per perp and hour the amount in USDC (negative = paid by the wallet, positive = received), its position and the funding rate.No findings
Why it is in this group
- The name "get_wallet_funding" says "get": a word for reading.
Description, as the server wrote it A wallet's HyperCore funding payments, newest first: per perp and hour the amount in USDC (negative = paid by the wallet, positive = received), its position and the funding rate. coin: one perp; from / to: a window in Unix ms (default everything up to now). History from 2025-09-27. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: A wallet's funding payments
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_mevEvery 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…No findings
Why it is in this group
- The name "get_wallet_mev" says "get": a word for reading.
Description, as the server wrote it 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 block, back-run in the next; probable = another spacing, up to 120 blocks; sure = strict or by a known sandwich bot. Free, no key.
Annotations the server declares
- title: Was a wallet sandwiched?
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_open_ordersA wallet's open HyperCore orders now (our node, at most 1 s old): resting limit orders and trigger orders (stop-loss / take-profit) on the main dex and every HIP-3 dex, each with c…No findings
Why it is in this group
- The name "get_wallet_open_orders" says "get": a word for reading.
Description, as the server wrote it A wallet's open HyperCore orders now (our node, at most 1 s old): resting limit orders and trigger orders (stop-loss / take-profit) on the main dex and every HIP-3 dex, each with coin, side, kind, limit and trigger price, size left and placed (0 = whole position), reduce-only, time in force, placed at. coin: one market. The status history of its trigger orders: get_wallet_stops.
Annotations the server declares
- title: A wallet's open orders
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_order_historyA wallet's HyperCore orders that left the book (filled, canceled, rejected), newest first: market, side, kind, limit and trigger price, size placed, filled and left, average fill p…No findings
Why it is in this group
- The name "get_wallet_order_history" says "get": a word for reading.
Description, as the server wrote it A wallet's HyperCore orders that left the book (filled, canceled, rejected), newest first: market, side, kind, limit and trigger price, size placed, filled and left, average fill price, the last status with Hyperliquid's reason (marginCanceled, reduceOnlyRejected…) and its time. Orders that left the book in the last 1 to 2 days (since 00:00 UTC yesterday, whenever placed) come first by exit time; then older ones placed in the last 30 days, by placement day then order id, not by exit time. coin: one market; outcome: filled, canceled or rejected. A page can be shorter than limit while next_cursor is set: keep following it (pass it as cursor). A cursor of the last-days part expires after about 2 days (400: start again without one). Orders whose last status fell in an ingest gap of our node are missing: Hyperliquid's historicalOrders has them.
Annotations the server declares
- title: A wallet's order history
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_pnlOne 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 …No findings
Why it is in this group
- The name "get_wallet_pnl" says "get": a word for reading.
Description, as the server wrote it 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: realized PnL, volume, swaps, closed positions and win rate, all-time unrealized PnL and value. Average cost over the wallet's priced swaps; tokens received by transfer are held with no cost; the native HYPE balance is in the wrapped HYPE row. sort = value, pnl, realized, unrealized, volume or lastTrade; status = all, open or closed. Medium call; live: WS pnl.
Annotations the server declares
- title: Wallet PnL (HyperEVM / Elysium)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_stopsA wallet's open HyperCore trigger orders (stop-loss / take-profit): coin, side, trigger and limit price, size (0 = whole position), reduce-only, placed at.No findings
Why it is in this group
- The name "get_wallet_stops" says "get": a word for reading.
Description, as the server wrote it A wallet's open HyperCore trigger orders (stop-loss / take-profit): coin, side, trigger and limit price, size (0 = whole position), reduce-only, placed at. history: true lists instead every status event of its trigger orders over the last 3 days at most (placed, triggered, canceled, rejected, and the fill or cancel of the order a trigger placed, `triggered: true`), newest first (a heavy call; next page: pass `next_cursor` as cursor).
Annotations the server declares
- title: A wallet's stops
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallet_value_historyThe 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.No findings
Why it is in this group
- The name "get_wallet_value_history" says "get": a word for reading.
Description, as the server wrote it 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 for window=all; current holdings: get_balances.
Annotations the server declares
- title: Portfolio value history (HyperEVM / Elysium)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_wallsWhich 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…No findings
Why it is in this group
- The name "get_walls" says "get": a word for reading.
Description, as the server wrote it 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 tested walls is liquidity that leaves as the price comes: requoting ladders, or spoofing (a record, not a verdict). Filter by market, account, side, wall size tier; window 24h, 7d or all (since 2026-10-13 15:50 UTC).
Annotations the server declares
- title: Order book wall reliability
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_webhookOne of your webhooks: state (pending_verification, active, or disabled with the reason and how to turn it on), failures in a row, subscriptions with their seq, today's deliveries a…No findings
Why it is in this group
- The name "get_webhook" says "get": a word for reading.
Description, as the server wrote it One of your webhooks: state (pending_verification, active, or disabled with the reason and how to turn it on), failures in a row, subscriptions with their seq, today's deliveries against your tier's daily limit.
Annotations the server declares
- title: One webhook
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
get_webhook_deliveriesDeliveries of one webhook, newest first (kept 7 days): msgId (the webhook-id header), type, status pending / delivered / dead, and each attempt with its HTTP status, latency, error…Reads text others writeNo findings
Why it is in this group
- The name "get_webhook_deliveries" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Deliveries of one webhook, newest first (kept 7 days): msgId (the webhook-id header), type, status pending / delivered / dead, and each attempt with its HTTP status, latency, error and the first 4 KiB of your answer. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Webhook deliveries
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_launchesLatest 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 Hyp…No findings
Why it is in this group
- The name "list_launches" says "list": a word for reading.
Description, as the server wrote it 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), creator, priceUsd, mcapUsd, 24 h volume, holders, top-10 / dev share, dev sold, Ascend progress and on-chain graduation (Ascend rows: ascendGraduation phase, progress, hold, deadline). sort: newest (default), volume24h, mcap, progress; status: curve, graduated, pool. Next page (newest, Elysium): pass `next_cursor` as cursor.
Annotations the server declares
- title: Token launches
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_marketsTradable 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 …No findings
Why it is in this group
- The name "list_markets" says "list": a word for reading.
Description, as the server wrote it 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 coin to pass to get_candles / get_trades (BTC, @107, xyz:TSLA); each with its last 5 min and last hour (change5m / change1h, volume5mUsd / volume1hUsd, trades5m / trades1h, traders5m / traders1h: distinct accounts) and trendScore; sort (hypercore only): trending (markets with a score above 0, highest first), volume, volume1h, volume5m, gainers, losers. hyperevm / elysium: DEX pools with price, priceUsd, 24 h volume, mcapUsd (Elysium); `id` is the pool key to pass to get_candles / get_trades / get_pool. `total` = markets matching. Next page: pass `next_cursor` as cursor. pairs (a watchlist, up to 100 ids, comma-separated: pool keys, HyperCore coins): those markets only, in that order, whatever q, kind, limit and the spam filter.
Annotations the server declares
- title: Markets and pools
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_mev_botsThe 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).No findings
Why it is in this group
- The name "list_mev_bots" says "list": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Sandwich bots
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_new_poolsEvery 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 sy…No findings
Why it is in this group
- The name "list_new_pools" says "list": a word for reading.
Description, as the server wrote it 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, current liquidity (V2 / V3 pools: token balances; V4 / Infinity: virtual reserves; USD = twice the smaller side), price, 24 h volume. Pools of a spam token left out. Filters: dex, token (either side), quote, minLiquidityUsd, newTokenOnly, since (ms). Filtered pages may hold fewer rows than limit: keep paging with `next_cursor` (null = no more). Live: WS <layer>.pools.new.
Annotations the server declares
- title: New pools (chain-wide)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_new_tokensEvery 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 (ascen…No findings
Why it is in this group
- The name "list_new_tokens" says "list": a word for reading.
Description, as the server wrote it 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 exists, priceUsd, mcapUsd, liquidityUsd, 24 h volume, holders. Spam tokens left out. Filters: launchpad (name, none, any, 0x), hasPool, minLiquidityUsd, minHolders, creator, since (ms); security=summary adds the cached get_token_security verdict to each row. Filtered pages may hold fewer rows than limit: keep paging with `next_cursor` (null = no more). Live: WS <layer>.tokens.new.
Annotations the server declares
- title: New tokens (chain-wide)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_nft_collectionsMost 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, standard and logo.No findings
Why it is in this group
- The name "list_nft_collections" says "list": a word for reading.
Description, as the server wrote it 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, standard and logo.
Annotations the server declares
- title: NFT collections
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_sandwichesSandwich 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…No findings
Why it is in this group
- The name "list_sandwiches" says "list": a word for reading.
Description, as the server wrote it 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: victim, bot, pool, token, from / to (Unix ms), minLossUsd, confidence; keep paging with next_cursor.
Annotations the server declares
- title: Sandwiches (MEV)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_top_tokensThe tokens of HyperEVM or Elysium with activity in the last 24 hours (a pool traded or created in it), one row per token over all its pools (not one per pool like list_markets): pr…No findings
Why it is in this group
- The name "list_top_tokens" says "list": a word for reading.
Description, as the server wrote it The tokens of HyperEVM or Elysium with activity in the last 24 hours (a pool traded or created in it), 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 / buyers / sellers), liquidity, market cap, FDV, holders (daily snapshot and now) and top-10 share, first pool time, pool count, the most traded pool (topPool: the market for get_candles / get_trades), creator, launchpad and launch (progress, bonded, dev share, dev sold), the HyperCore price and gap of a Core-linked token, socials, named wallets trading it, a 24 h hourly spark and a 1 h five-minute spark. sort: trending (default; rows with a score of 0 left out), volume, gainers, losers, new, mcap, liquidity. Stablecoins and WHYPE left out unless includeStables, spam unless includeSpam, liquidity under minLiquidityUsd (default 1000) always. security=summary adds the cached get_token_security verdict to each row. addresses (a watchlist, up to 100 token addresses, comma-separated): those tokens' rows only, in that order, whatever sort and filters (spam ones flagged). Trending = last-hour volume (capped at 10 × liquidity) × its acceleration over the 24 h hourly average × √distinct wallets. Next page: pass next_cursor as cursor.
Annotations the server declares
- title: Token screener (trending, gainers, new…)
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
list_webhooksYour account's webhooks: URL, state (pending_verification, active, disabled with the reason and how to enable), failures in a row, subscriptions.Reads text others writeNo findings
Why it is in this group
- The name "list_webhooks" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Your account's webhooks: URL, state (pending_verification, active, disabled with the reason and how to enable), failures in a row, subscriptions. A rotated key sees the same webhooks. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Your webhooks
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
search_coinsTokens by symbol, name or address, with their links across layers (Elysium <-> HyperEVM <-> HyperCore), decimals, supply and USD price.No findings
Why it is in this group
- The name "search_coins" says "search": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Find tokens
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
search_entitiesNamed wallets (KOLs, traders, funds, market makers) and their wallets, from public attribution lists (not verified identities).No findings
Why it is in this group
- The name "search_entities" says "search": a word for reading.
Description, as the server wrote it 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 entity id with kol_activity. Next page: pass `next_cursor` as cursor.
Annotations the server declares
- title: Named wallets
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
150 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write15
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__femtos__get_deploys",
"mcp__femtos__get_token_security"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:21 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 36
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.femtos.xyz/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.femtos.xyz
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 36 tools that change things (6 destructive, 6 irreversible, 24 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.femtos.xyz/mcp: tools/list returned 130 tools to an anonymous client, including delete_webhook (destructive), cancel_plan (destructive), rotate_key (destructive), freeze_key (destructive), delete_account (destructive) and 31 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 31 to 36
- Nov 6, 2026
- RFC 9728 protected resource metadata: none to https://api.femtos.xyz/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.femtos.xyz
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
- Oct 29, 2026
- Tools that change things, listed without credentials: 8 to 31
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_open_interest" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_open_interest" says "get": a word for reading.
The server marks "list_open_interest" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "list_open_interest" says "list": a word for reading.
- Warnget_positions
The server marks "get_positions" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_positions" says "get": a word for reading.
- Warnget_stop_map
The server marks "get_stop_map" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_stop_map" says "get": a word for reading.
- Warnget_forced_flow
The server marks "get_forced_flow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_forced_flow" says "get": a word for reading.
The server marks "get_triggered_stops" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_triggered_stops" says "get": a word for reading.
Show 5 more findingsShow fewer
The server marks "get_nft_transfers" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_nft_transfers" says "get": a word for reading.
The server marks "get_builder_fills" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "get_builder_fills" says "get": a word for reading.
The server marks "get_deposit_address" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_deposit_address" says "get": a word for reading.
The server marks "get_payment_options" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "get_payment_options" says "get": a word for reading.
- Warncancel_plan
The server marks "cancel_plan" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "cancel_plan" says "cancel": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 31 -> 36.View diff
- Tools that change things, listed without credentials: 31 to 36
Tools7 added, 10 changed.+7 added~10 changedView diff
- Added:get_chain_activityOnly reads
- Added:get_hypercore_wallet_pnlOnly reads
- Added:get_predicted_fundingOnly reads
- Added:get_wallet_order_historyOnly reads
- Added:get_wallet_pnlOnly reads
- Added:get_wallet_value_historyOnly reads
- Added:hyperevm_rpcChanges things
- Changed:elysium_rpcChanges thingstitledescriptioninputSchemaannotations
- Changed:get_holdersOnly readsdescription
- Changed:get_holders_historyOnly readsdescriptioninputSchema
- Changed:get_mev_botOnly readsinputSchema
- Changed:get_token_tradersOnly readsdescriptioninputSchema
- Changed:get_tradesOnly readsdescriptioninputSchema
- Changed:list_launchesOnly readsdescriptioninputSchema
- Changed:list_marketsOnly readsdescriptioninputSchema
- Changed:list_sandwichesOnly readsinputSchema
- Changed:list_top_tokensOnly readsdescriptioninputSchema
Tools58 added, 48 changed.+58 added~48 changedView diff
- Added:cancel_planDeletes or cancels
- Added:delete_accountDeletes or cancels
- Added:elysium_rpcChanges things
- Added:enable_webhookChanges things
- Added:freeze_keyDeletes or cancels
- Added:get_accountOnly reads
- Added:get_blockOnly reads
- Added:get_builderOnly reads
- Added:get_builder_fillsCan't be undone
- Added:get_builder_ordersOnly reads
- Added:get_buildersOnly reads
- Added:get_deploysOnly reads
- Added:get_deposit_addressChanges things
- Added:get_depositsOnly reads
- Added:get_entity_graphOnly reads
- Added:get_entity_pnlOnly reads
- Added:get_gasOnly reads
- Added:get_holders_historyOnly reads
- Added:get_hypercore_accountOnly reads
- Added:get_ledgerOnly reads
- Added:get_mev_botOnly reads
- Added:get_mev_statsOnly reads
- Added:get_open_interestCan't be undone
- Added:get_open_interest_cohortsOnly reads
- Added:get_open_interest_opensOnly reads
- Added:get_payment_optionsChanges things
- Added:get_plansOnly reads
- Added:get_position_changesOnly reads
- Added:get_position_flowOnly reads
- Added:get_price_levelOnly reads
- Added:get_recovery_challengeOnly reads
- Added:get_signup_challengeOnly reads
- Added:get_token_tradersOnly reads
- Added:get_twap_historyOnly reads
- Added:get_twapsOnly reads
- Added:get_usageOnly reads
- Added:get_wall_eventsOnly reads
- Added:get_wallet_fill_barsOnly reads
- Added:get_wallet_fillsOnly reads
- Added:get_wallet_fundingOnly reads
- Added:get_wallet_mevOnly reads
- Added:get_wallet_open_ordersOnly reads
- Added:get_wallsOnly reads
- Added:get_webhookOnly reads
- Added:kol_positioningChanges things
- Added:list_mev_botsOnly reads
- Added:list_open_interestChanges things
- Added:list_sandwichesOnly reads
- Added:list_top_tokensOnly reads
- Added:pay_with_walletCan't be undone
- Added:quote_wallet_paymentCan't be undone
- Added:recover_accountDeletes or cancels
- Added:rotate_keyDeletes or cancels
- Added:rotate_webhook_secretChanges things
- Added:set_spending_capChanges things
- Added:signupChanges things
- Added:subscribe_planChanges things
- Added:update_webhookChanges things
- Changed:create_webhookChanges thingsinputSchema
- Changed:delete_webhookDeletes or cancelsinputSchema
- Changed:get_balancesOnly readsinputSchema
- Changed:get_bookOnly readsdescription
- Changed:get_bridgesOnly readsdescriptioninputSchema
- Changed:get_candlesOnly readsinputSchema
- Changed:get_coinOnly readsinputSchema
- Changed:get_erc20_transfersOnly readsinputSchema
- Changed:get_forced_flowChanges thingsdescriptioninputSchema
- Changed:get_holdersOnly readsdescriptioninputSchema
- Changed:get_launchOnly readsinputSchema
- Changed:get_launch_timelineOnly readsinputSchema
- Changed:get_liquidation_mapOnly readsdescriptioninputSchema
- Changed:get_liquidationsOnly readsdescriptioninputSchema
- Changed:get_nft_collectionOnly readsinputSchema
- Changed:get_nft_tokensOnly readsdescriptioninputSchema
- Changed:get_nft_transfersCan't be undoneinputSchema
- Changed:get_nfts_ownedOnly readsinputSchema
- Changed:get_poolOnly readsdescriptioninputSchema
- Changed:get_positionsChanges thingsdescriptioninputSchema
- Changed:get_price_historyOnly readsinputSchema
- Changed:get_pricesOnly readsinputSchema
- Changed:get_statusOnly readsdescriptioninputSchema
- Changed:get_stop_mapChanges thingsdescriptioninputSchema
- Changed:get_token_balanceOnly readsinputSchema
- Changed:get_token_lifecycleOnly readsdescriptioninputSchema
- Changed:get_token_overviewOnly readsdescriptioninputSchema
- Changed:get_token_securityOnly readsdescriptioninputSchema
- Changed:get_token_volumeOnly readsinputSchema
- Changed:get_tokensOnly readsinputSchema
- Changed:get_tradesOnly readsdescriptioninputSchema
- Changed:get_transactionOnly readsinputSchema
- Changed:get_triggered_stopsChanges thingsinputSchema
- Changed:get_walletOnly readsdescriptioninputSchema
- Changed:get_wallet_stopsOnly readsinputSchema
- Changed:get_webhook_deliveriesOnly readsinputSchema
- Changed:kol_activityChanges thingsinputSchema
- Changed:kol_leaderboardChanges thingsinputSchema
- Changed:list_launchesOnly readsinputSchema
- Changed:list_marketsOnly readsdescriptioninputSchema
- Changed:list_new_poolsOnly readsdescriptioninputSchema
- Changed:list_new_tokensOnly readsinputSchema
- Changed:list_nft_collectionsOnly readsdescriptioninputSchema
- Changed:list_webhooksOnly readsinputSchema
- Changed:replay_webhookCan't be undoneinputSchema
- Changed:search_coinsOnly readsinputSchema
- Changed:search_entitiesOnly readsinputSchema
- Changed:test_webhookChanges thingsinputSchema
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://api.femtos.xyz/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://api.femtos.xyz; Dynamic client registration: not observed -> yes (…View diff
- RFC 9728 protected resource metadata: none to https://api.femtos.xyz/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://api.femtos.xyz
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 31.View diff
- Tools that change things, listed without credentials: 8 to 31
Tools22 added, 8 changed.+22 added~8 changedView diff
- Added:create_webhookChanges things
- Added:delete_webhookDeletes or cancels
- Added:get_balancesOnly reads
- Added:get_forced_flowChanges things
- Added:get_liquidation_mapOnly reads
- Added:get_poolOnly reads
- Added:get_price_historyOnly reads
- Added:get_pricesOnly reads
- Added:get_stop_mapChanges things
- Added:get_token_balanceOnly reads
- Added:get_token_overviewOnly reads
- Added:get_token_securityOnly reads
- Added:get_tokensOnly reads
- Added:get_transactionOnly reads
- Added:get_triggered_stopsChanges things
- Added:get_wallet_stopsOnly reads
- Added:get_webhook_deliveriesOnly reads
- Added:list_new_poolsOnly reads
- Added:list_new_tokensOnly reads
- Added:list_webhooksOnly reads
- Added:replay_webhookCan't be undone
- Added:test_webhookChanges things
- Changed:get_candlesOnly readsdescriptioninputSchema
- Changed:get_coinOnly readsdescription
- Changed:get_erc20_transfersOnly readstitledescriptioninputSchemaannotations
- Changed:get_tradesOnly readstitledescriptioninputSchemaannotations
- Changed:get_walletOnly readsdescription
- Changed:kol_leaderboardChanges thingsinputSchema
- Changed:list_marketsOnly readsdescription
- Changed:search_entitiesOnly readsinputSchema
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http femtos https://api.femtos.xyz/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http femtos https://api.femtos.xyz/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__femtos__get_status",
"mcp__femtos__list_markets",
"mcp__femtos__list_top_tokens",
"mcp__femtos__get_candles",
"mcp__femtos__get_trades",
"mcp__femtos__search_coins",
"mcp__femtos__get_coin",
"mcp__femtos__get_holders",
"mcp__femtos__get_holders_history",
"mcp__femtos__list_launches",
"mcp__femtos__list_new_tokens",
"mcp__femtos__list_new_pools",
"mcp__femtos__get_launch",
"mcp__femtos__get_launch_timeline",
"mcp__femtos__get_token_lifecycle",
"mcp__femtos__get_token_security",
"mcp__femtos__get_prices",
"mcp__femtos__get_price_history",
"mcp__femtos__get_tokens",
"mcp__femtos__get_token_overview",
"mcp__femtos__get_token_traders",
"mcp__femtos__get_bridges",
"mcp__femtos__get_wallet",
"mcp__femtos__get_wallet_pnl",
"mcp__femtos__get_wallet_value_history",
"mcp__femtos__get_balances",
"mcp__femtos__get_token_balance",
"mcp__femtos__get_token_volume",
"mcp__femtos__get_erc20_transfers",
"mcp__femtos__get_pool",
"mcp__femtos__get_wallet_mev",
"mcp__femtos__list_sandwiches",
"mcp__femtos__get_mev_stats",
"mcp__femtos__list_mev_bots",
"mcp__femtos__get_mev_bot",
"mcp__femtos__get_transaction",
"mcp__femtos__get_gas",
"mcp__femtos__get_chain_activity",
"mcp__femtos__get_block",
"mcp__femtos__get_book",
"mcp__femtos__get_walls",
"mcp__femtos__get_wall_events",
"mcp__femtos__get_open_interest_cohorts",
"mcp__femtos__get_open_interest_opens",
"mcp__femtos__get_liquidations",
"mcp__femtos__get_liquidation_stats",
"mcp__femtos__get_position_changes",
"mcp__femtos__get_position_flow",
"mcp__femtos__get_liquidation_map",
"mcp__femtos__get_wallet_stops",
"mcp__femtos__get_price_level",
"mcp__femtos__get_hypercore_account",
"mcp__femtos__get_wallet_open_orders",
"mcp__femtos__get_wallet_fills",
"mcp__femtos__get_wallet_order_history",
"mcp__femtos__get_wallet_fill_bars",
"mcp__femtos__get_wallet_funding",
"mcp__femtos__get_hypercore_wallet_pnl",
"mcp__femtos__get_twaps",
"mcp__femtos__get_twap_history",
"mcp__femtos__get_predicted_funding",
"mcp__femtos__list_nft_collections",
"mcp__femtos__get_nft_collection",
"mcp__femtos__get_nft_tokens",
"mcp__femtos__get_nfts_owned",
"mcp__femtos__search_entities",
"mcp__femtos__get_entity_graph",
"mcp__femtos__get_entity_pnl",
"mcp__femtos__get_builders",
"mcp__femtos__get_builder",
"mcp__femtos__get_builder_orders",
"mcp__femtos__get_deploys",
"mcp__femtos__list_webhooks",
"mcp__femtos__get_webhook",
"mcp__femtos__get_webhook_deliveries",
"mcp__femtos__get_account",
"mcp__femtos__get_usage",
"mcp__femtos__get_ledger",
"mcp__femtos__get_deposits",
"mcp__femtos__get_plans",
"mcp__femtos__get_signup_challenge",
"mcp__femtos__get_recovery_challenge"
],
"ask": [
"mcp__femtos__elysium_rpc",
"mcp__femtos__hyperevm_rpc",
"mcp__femtos__get_open_interest",
"mcp__femtos__list_open_interest",
"mcp__femtos__get_positions",
"mcp__femtos__get_stop_map",
"mcp__femtos__get_forced_flow",
"mcp__femtos__get_triggered_stops",
"mcp__femtos__get_nft_transfers",
"mcp__femtos__kol_leaderboard",
"mcp__femtos__kol_positioning",
"mcp__femtos__kol_activity",
"mcp__femtos__get_builder_fills",
"mcp__femtos__create_webhook",
"mcp__femtos__update_webhook",
"mcp__femtos__enable_webhook",
"mcp__femtos__rotate_webhook_secret",
"mcp__femtos__test_webhook",
"mcp__femtos__replay_webhook",
"mcp__femtos__get_deposit_address",
"mcp__femtos__get_payment_options",
"mcp__femtos__subscribe_plan",
"mcp__femtos__quote_wallet_payment",
"mcp__femtos__pay_with_wallet",
"mcp__femtos__set_spending_cap",
"mcp__femtos__signup"
],
"deny": [
"mcp__femtos__delete_webhook",
"mcp__femtos__cancel_plan",
"mcp__femtos__rotate_key",
"mcp__femtos__freeze_key",
"mcp__femtos__delete_account",
"mcp__femtos__recover_account"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as femtos. Review it before you use it.
Capability tags behind 19 rules
- mcp__femtos__get_token_security private-data
- mcp__femtos__hyperevm_rpc untrusted-input
- mcp__femtos__get_open_interest outbound
- mcp__femtos__get_nft_tokens untrusted-input
- mcp__femtos__get_builder_fills outbound
- mcp__femtos__get_deploys private-data
- mcp__femtos__create_webhook untrusted-input, outbound
- mcp__femtos__list_webhooks untrusted-input
- mcp__femtos__update_webhook untrusted-input, outbound
- mcp__femtos__enable_webhook untrusted-input
- mcp__femtos__rotate_webhook_secret untrusted-input
- mcp__femtos__test_webhook untrusted-input
- mcp__femtos__get_webhook_deliveries untrusted-input
- mcp__femtos__replay_webhook untrusted-input, outbound
- mcp__femtos__get_payment_options untrusted-input
- mcp__femtos__subscribe_plan untrusted-input
- mcp__femtos__quote_wallet_payment untrusted-input
- mcp__femtos__pay_with_wallet untrusted-input
- mcp__femtos__signup untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/xyz.femtos/mcp/verify?hash=b046de515b18f3cc2a699237637bc1cc3053fc0a02004ba2fd20195f7af39456" | jq -e '.changed == false'Pinned hash b046de515b18, from Nov 10, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/xyz.femtos/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/xyz.femtos/mcp)Source: MCP Registry. Synced Nov 10, 2026, 01:18 UTC.
Femtos MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Femtos MCP server safe?
- No scan can promise that. What its definitions show: 114 tools, 32 of which can change, send or delete something, and 11 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Femtos MCP server delete data?
- Yes. 6 tools can delete, cancel or revoke something: delete_webhook, cancel_plan, rotate_key, freeze_key, delete_account and recover_account.
Can the Femtos MCP server do things that cannot be undone?
- Yes. 6 tools can send, pay, publish or merge: get_open_interest, get_nft_transfers, get_builder_fills, replay_webhook, quote_wallet_payment and pay_with_wallet.
What tools does the Femtos MCP server have?
- 114 tools: 6 destructive, 6 irreversible, 20 write, 82 read. delete_webhook, cancel_plan, rotate_key, freeze_key, delete_account, recover_account, get_open_interest, get_nft_transfers and 106 more.
Does the Femtos MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Femtos MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_open_interest, get_builder_fills, create_webhook, update_webhook and replay_webhook.
Has the Femtos MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.