Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
SQD is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
31
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Query 130+ SQD Portal datasets across blockchains, including native Tron transactions and events.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sqd-mcp https://portal.sqd.dev/mcp
# 2 — ask your agent for something these tools do
# portal_list_networks, portal_get_network_info, portal_get_head and 28 more
SQD costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SLAll 1 server
subsquid-labs1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sqd-mcp https://portal.sqd.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
31 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Find the right network or chain name to use across EVM, Solana, Bitcoin, Substrate, and Hyperliquid. COMMON USER ASKS: - Find Base-like networks - Show Solana mainnets - Show Substrate mainnets FIRST CHOICE FOR: - finding the correct network before any other query WHEN TO USE: - You are not sure which network name, chain name, or alias to use. - You want to filter networks by VM family, network
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vm | string | no | Filter by VM family |
| network_type | string | no | Filter by network type |
| query | string | no | Search by name, alias, or chain ID |
| real_time_only | boolean | no | Only show networks with a real-time indexed head |
| limit | number | no | Max results to return (default: 25, max: 100) |
| cursor | string | no | Continuation cursor from a previous network catalog page |
Answer "is this network caught up?" with indexing freshness, lag, heads, and available tables. COMMON USER ASKS: - Is Base caught up? FIRST CHOICE FOR: - checking indexing head, lag, tables, and capabilities for one network WHEN TO USE: - You want to know whether a network is indexed, fresh, caught up, or behind before querying. - You need chain family, real-time status, or available tables for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | yes | Network name or alias |
Get just the latest indexed head block or slot for a network. COMMON USER ASKS: - Latest head - Finalized head FIRST CHOICE FOR: - getting the current indexed head before building a manual block range WHEN TO USE: - You only need the current block or slot number. - You need the current head before building a raw block-range query. DON'T USE: - You want to know if the network is caught up, behi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | yes | Network name or alias |
| type | string | no | Block type |
Resolve user-facing blockchain entities into query-ready identifiers, with ambiguity kept explicit. COMMON USER ASKS: - Resolve USDC on Base - Resolve WETH on Ethereum - Resolve BAYC contract FIRST CHOICE FOR: - resolving a token symbol like USDC to token contract addresses - resolving EVM contract aliases, protocol names, pool identifiers, or Hyperliquid coin names before querying - checking wh
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias when the entity is network-scoped, e.g. "base", "ethereum", "arbitrum-one", or "hyperliquid-fills". |
| kind | string | no | Entity kind to resolve: token, contract alias/address, pool identifier, protocol name, or Hyperliquid coin/ticker. |
| query | string | yes | Entity string to resolve, e.g. "USDC", "bayc", "uniswap", "BTC", or "0x...". |
| limit | number | no | Maximum matches to return. |
Get a simple recent-activity feed across EVM, Solana, Bitcoin, or Hyperliquid with chronological paging and investigation pivots. COMMON USER ASKS: - Recent activity on Base - Recent Hyperliquid fills FIRST CHOICE FOR: - recent activity on any supported network without manual block math - questions like "what has been happening on Base lately?" - first-pass incident triage when the user asks wha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (supports short names: 'polygon', 'base', 'ethereum', 'arbitrum', etc.). Optional when continuing with cursor. |
| timeframe | string | no | Time period or block count. Examples: '100' (default), '1h', '6h', '24h', '7d', '3d'. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| from_addresses | array | no | Filter by sender addresses |
| to_addresses | array | no | Filter by recipient addresses |
| limit | integer | no | Max activity rows to return (default: 10, max: 25) |
| cursor | string | no | Continuation cursor from a previous response |
Summarize wallet activity and fund flow with shared overview, asset movement, counterparties, evidence pivots, and follow-up filters across supported networks. COMMON USER ASKS: - EVM wallet fund-flow triage - Solana wallet activity and fee flow FIRST CHOICE FOR: - one-call wallet analysis across supported VMs - suspicious wallet triage, fund-flow direction, counterparties, and next evidence piv
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| address | string | no | Wallet address to analyze. Optional when continuing with cursor. |
| timeframe | string | no | Look-back period as timeframe or block count. Examples: '1h', '24h', '7d', '3d', '1000'. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| include_tokens | boolean | no | Include ERC20 token transfers |
| include_nfts | boolean | no | Include NFT transfers (ERC721/1155) |
| limit_per_type | integer | no | Requested items per category (default: 5). Values up to the retained compatibility maximum of 10 are accepted, while each category is safely capped at 4 rows and remains cursorable. |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| response_format | string | no | Response format: defaults to 'compact' for a readable wallet investigation. Use 'summary' for headline flow only or 'full' for all returned activity rows. |
| cursor | string | no | Continuation cursor from a previous response |
Build simple activity charts and other time-series views across supported VMs, including compare-previous windows and grouped EVM contract trends. COMMON USER ASKS: - Base transactions per 15m bucket - Compare two periods FIRST CHOICE FOR: - activity over time, compare-current-vs-previous, grouped trends, and simple activity charts WHEN TO USE: - You want chart-ready metric buckets over time. -
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | yes | Network name (supports short names: 'ethereum', 'polygon', 'base', etc.) |
| metric | string | yes | Metric to aggregate over time. Per chain family: evm: transaction_count, transactions_per_block, avg_gas_price, gas_used, block_utilization, unique_addresses; solana: transaction_count, unique_address |
| interval | string | yes | Time bucket interval (5m, 15m, 1h, 6h, 1d) |
| duration | string | no | Total time period to analyze. Defaults to "6h" for interactive use. The bound is in blocks, not time: this tool reads every block in the window and stops at 12,000, so "24h" is fine on Bitcoin or Ethe |
| address | string | no | Optional: Filter to specific contract address for contract-specific trends |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "24h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| compare_previous | boolean | no | Compare the selected window against the immediately previous window |
| group_by | string | no | Optional grouping mode. contract is currently supported only for EVM transaction_count |
| group_limit | number | no | Maximum number of contract groups when group_by=contract |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
Query raw EVM logs with address/topic filters, common event aliases, earliest/latest scanning, and optional inline decoding. COMMON USER ASKS: - Recent USDC Transfer logs - First recent USDC Transfer log - Latest ERC721/pass mint ID and tx hash FIRST CHOICE FOR: - NFT or ERC721 mint lookups such as latest pass minted, token ID, and mint transaction hash - contract event questions where the user
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Natural time range such as '5m', '1h', '24h', '7d', or 'past 30 minutes'. Alternative to from_block/to_block. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number. RECOMMENDED: <10k blocks for fast (<1s) responses. Larger ranges may be slow or timeout. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| addresses | array | no | Contract addresses to filter (e.g., ['0xUSDC...', '0xDAI...']). IMPORTANT: Always include this or topics for fast queries. |
| token_symbols | array | no | Token symbols to resolve via open token-list data and merge into addresses, e.g. ["USDC"]. |
| max_token_symbol_matches | number | no | Maximum token-list matches to include per token symbol. Use addresses for deterministic single-contract filters. |
| event | no | Common event alias or topic0 hash. Examples: "transfer", "approval", "swap", "sync", "deposit", "withdrawal". Merges with topic0. | |
| topic0 | array | no | Event signatures (topic0). E.g., Transfer = 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef |
| topic1 | array | no | Topic1 filter (often: from address in Transfer, indexed parameter 1) |
| topic2 | array | no | Topic2 filter (often: to address in Transfer, indexed parameter 2) |
| topic3 | array | no | Topic3 filter (indexed parameter 3, chain-specific) |
| scan_order | string | no | Which side of the block window to scan first. Use earliest for first-event questions. |
| max_scan_blocks | integer | no | Maximum blocks to inspect for bounded earliest/latest scans. Sparse latest searches default to 25,000 blocks to stay within MCP request timeouts; raise only when deeper coverage is worth the added lat |
| limit | integer | no | Max logs to return (default: 20, max: 25). This verified ceiling keeps pages within MCP client budgets. |
| field_preset | string | no | Field preset: 'minimal' (address+topic0+block, ~80% smaller), 'standard' (all topics+timestamp), 'full' (includes raw data hex, largest). Use 'minimal' to reduce context usage. |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output, or stays 'full' when inline transaction context is requested. Use 'summary' for counting or categorizing. |
Query raw EVM transactions with optional logs, traces, state-diff context, and evidence pivots for transaction-level investigations. COMMON USER ASKS: - Recent Base transactions - Filter by sender - First EIP-2930 transaction from Berlin fork WHEN TO USE: - You need raw transaction records on an EVM network. - You want chain-specific transaction fields or include flags that convenience tools do
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Natural time range such as '5m', '1h', '24h', '7d', or 'past 30 minutes'. Alternative to from_block/to_block. Large ranges are allowed with a low limit (<=100). |
| from_block | number | no | Starting block number (use this OR timeframe). Large ranges OK with low limit (<=100). |
| to_block | number | no | Ending block number. RECOMMENDED: <5k blocks for fast (<500ms) responses. Larger ranges may be slow. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| from_addresses | array | no | FILTER: Sender addresses (wallets or contracts that initiated the transaction). Optional if limit <=100. |
| to_addresses | array | no | FILTER: Recipient addresses (typically contracts being called, or wallets receiving ETH). Optional if limit <=100. |
| from_token_symbols | array | no | Resolve token symbols via open token-list data and merge them into from_addresses. Rare, but useful for token-contract-originated transactions. |
| to_token_symbols | array | no | Resolve token symbols via open token-list data and merge them into to_addresses, e.g. transfer/approve calls to USDC. |
| max_token_symbol_matches | number | no | Maximum token-list matches to include per token symbol. Use from_addresses/to_addresses for deterministic single-contract filters. |
| sighash | array | no | FILTER: Function sighash (4-byte hex, e.g., '0xa9059cbb' for transfer). Optional if limit <=100. |
| method | no | FILTER: Common EVM method alias or 4-byte sighash. Examples: "transfer", "approve", "transferFrom", "deposit", "withdraw". Merges with sighash. | |
| transaction_type | no | FILTER: EVM transaction type. Accepts decimal or hex strings such as 0, 1, 2, "0x0", "0x1", "0x2". Applied client-side while streaming Portal results; use with scan_order="earliest" and from_block to | |
| transaction_status | no | FILTER: Transaction receipt status. Use "success"/1 or "failed"/0 for failed/reverted transaction searches. | |
| contract_creation | boolean | no | FILTER: true returns contract-creation transactions; false excludes them. Useful for "first contract creation from this wallet". |
| min_value_wei | no | FILTER/RANKING: Minimum native token value in wei. Accepts decimal or hex string. | |
| min_gas_used | no | FILTER/RANKING: Minimum receipt gasUsed. Accepts decimal or hex string. | |
| min_effective_gas_price_wei | no | FILTER/RANKING: Minimum effectiveGasPrice in wei. Accepts decimal or hex string. |
Query raw EVM traces: internal calls, contract creations, self-destructs, and block rewards, filtered by caller, callee, method, deployer, or one transaction, with the parent transaction hash on every row. COMMON USER ASKS: - Internal calls of one transaction - Recent internal calls into a contract - Contracts deployed by an address FIRST CHOICE FOR: - what a transaction called internally, inclu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number. Traces are expensive: keep filtered windows under 5,000 blocks. |
| timeframe | string | no | Time range (e.g., '10m', '1h'). Alternative to from_block/to_block. Keep it short for traces. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| type | array | no | FILTER: trace types. 'create' covers both CREATE and CREATE2; 'reward' only exists on proof-of-work history. |
| call_from | array | no | FILTER (call traces): calling addresses, contracts or wallets. |
| call_to | array | no | FILTER (call traces): called addresses. |
| call_sighash | array | no | FILTER (call traces): 4-byte selectors such as 0xa9059cbb. |
| method | no | FILTER (call traces): method alias such as transfer, approve, deposit, or a 4-byte selector. Merges with call_sighash. | |
| create_from | array | no | FILTER (create traces): deployer addresses. |
| create_result_address | array | no | FILTER (create traces): deployed contract addresses. |
| transaction_hash | string | no | FILTER: keep only traces of this transaction. Give its block (from_block = to_block) or a window of at most 1,000 blocks; find the block with portal_evm_query_transactions first when unknown. |
| include_transaction | boolean | no | Attach the parent transaction (sender, recipient, value, status). The hash is always attached. |
| include_subtraces | boolean | no | Also return the child traces of each matching trace |
| scan_order | string | no | Which side of the block window to scan first. Use earliest for first-occurrence questions. |
| max_scan_blocks | integer | no | Safety cap for bounded scans. Default: 5,000 blocks with filters, 100 without. |
| finalized_only | boolean | no | Only query finalized blocks |
| field_preset | string | no | Field preset: 'minimal' (type, from, to), 'standard' (value, selector, gas, result address), 'full' (adds call input and output and creation code). |
Query token-transfer activity on EVM without needing to remember Transfer event signatures. Best for "did token X move?" and asset-tracing questions. COMMON USER ASKS: - Recent USDC transfers - First recent USDC transfer WHEN TO USE: - You want ERC-20 style transfer activity filtered by token, sender, or recipient. - You want the fastest answer to a token movement question like "did USDC move?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| from_block | number | no | Starting block number |
| to_block | number | no | Ending block number. RECOMMENDED: <10k blocks for fast responses. |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to block numbers. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| token_addresses | array | no | Token contract addresses |
| token_symbols | array | no | Token symbols to resolve via open token-list data, e.g. ["USDC"]. Merges with token_addresses. |
| max_token_symbol_matches | number | no | Maximum token-list matches to include per token symbol. Use token_addresses for deterministic single-contract filters. |
| from_addresses | array | no | Sender addresses |
| to_addresses | array | no | Recipient addresses |
| scan_order | string | no | Which side of the block window to scan first. Use earliest for first-transfer questions. |
| limit | number | no | Max transfers |
| include_token_info | boolean | no | Include token metadata (symbol, decimals) inline. Avoids separate token metadata lookups. |
| cursor | string | no | Continuation cursor from a previous response |
Locate the create trace and parent transaction that deployed a specific EVM contract address within a bounded window. COMMON USER ASKS: - Find BAYC deployment - Find recent deployment - Find deployment from known range FIRST CHOICE FOR: - who deployed this EVM contract - when was this contract deployed - what deployment transaction created this contract WHEN TO USE: - You need the deployer, dep
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | yes | EVM network name or alias, e.g. base, ethereum, arbitrum. |
| contract_address | string | no | Contract address whose deployment transaction should be located. |
| contract | string | no | Contract address or a supported well-known alias/name, e.g. "bayc" or "bored apes" on Ethereum. |
| timeframe | string | no | Optional recent time window to search, e.g. "24h" or "7d". |
| from_block | number | no | Optional starting block. Provide this for older contracts when the deployment is not recent. |
| to_block | number | no | Optional ending block. Defaults to the indexed head. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "7d ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| search_depth_blocks | number | no | When no explicit range is given, search this many recent blocks backward from the indexed head. |
| max_scan_blocks | number | no | Safety cap for historical deployment scans. Default: scan the requested window up to 1,000,000 blocks. |
| scan_order | string | no | Scan latest first for recent deployments, or earliest first when you provide a historical from_block. |
Summarize what one specific contract has been doing lately, including recent interactions, unique callers, and optional event activity. COMMON USER ASKS: - Contract activity snapshot FIRST CHOICE FOR: - what one specific contract has been doing lately on an EVM network WHEN TO USE: - You want to ask "what has this contract been doing?" and get a contract-level answer. - You want a contract-cent
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | yes | Network name or alias |
| contract_address | string | yes | Contract address to analyze |
| timeframe | string | no | Analysis period as timeframe or block count. Examples: '1h', '24h', '7d', '3d', '1000'. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| include_events | boolean | no | Include event log summary |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
Get the big picture for network-wide EVM activity with ranked contracts and compact overview metrics. COMMON USER ASKS: - Top contracts on Base FIRST CHOICE FOR: - the big picture for activity on an EVM network like Base or Optimism WHEN TO USE: - You want the big picture for activity on an EVM network. - You want the most active contracts on an EVM network. - You want an analytics-style networ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (supports short names: 'ethereum', 'polygon', 'base', etc.). Optional when continuing with cursor. |
| num_blocks | number | no | Number of recent blocks to analyze when timeframe is omitted (default: 50, max: 10000) |
| timeframe | string | no | Optional natural time window like '1h' or '24h' |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| limit | number | no | Number of top contracts to return (default: 10, max: 100) |
| include_details | boolean | no | Include sample transaction hashes for each contract |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| cursor | string | no | Continuation cursor from a previous response |
Build chart-ready EVM OHLC candles plus a recent trade tape from supported DEX event sources, including Uniswap v2-style swaps, Uniswap v3/v4, and Aerodrome Slipstream. COMMON USER ASKS: - Base Uniswap v2-style swap candles - Base Uniswap candles - Base Uniswap v4 candles WHEN TO USE: - You need OHLC candles for supported EVM event-derived price sources. - You want a candle chart and recent trad
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | EVM network name (default: base-mainnet) |
| pool_address | string | no | Pool/pair contract address for address-keyed sources like Uniswap v3, Slipstream, or Sync-derived CPMM pools. |
| pool_id | string | no | Uniswap v4 pool id (bytes32). Optional when you provide the full v4 pool key instead. |
| pool_manager_address | string | no | Uniswap v4 PoolManager address. Optional on networks with a built-in official Uniswap deployment mapping. |
| source | string | no | Which event source to build candles from. Prefer swap-derived sources for factual trade prices and volumes. Uniswap v4 uses PoolManager Swap events filtered by pool_id, not a per-pool contract address |
| interval | string | no | Candle interval. auto uses chart-friendly defaults like 1h→5m and 24h→1h. |
| duration | string | no | How much recent history to cover. Accepts compact durations like "1h" or natural phrases like "past 30 minutes". |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| price_in | string | no | Choose which token the displayed price should be expressed in. auto picks the more human-readable quote side. |
| base_token | string | no | Legacy orientation input. Prefer price_in instead. |
| include_recent_trades | boolean | no | Include a recent trade tape for swap-derived sources when factual per-trade amounts are available. |
| recent_trades_limit | integer | no | Maximum number of recent trades to return in the trade tape. |
| currency0_address | string | no | Optional Uniswap v4 currency0 address. Use with currency1_address, fee, and tick_spacing to derive pool_id factually. |
| currency1_address | string | no | Optional Uniswap v4 currency1 address. Use with currency0_address, fee, and tick_spacing to derive pool_id factually. |
| fee | integer | no | Optional Uniswap v4 LP fee in hundredths of a bip, e.g. 3000 for 0.30%. |
| tick_spacing | integer | no | Optional Uniswap v4 tick spacing. Required with the rest of the pool key when deriving pool_id. |
| hooks_address | string | no | Optional Uniswap v4 hooks contract address. Defaults to the zero address when omitted. |
| token0_symbol | string | no | Optional token0 symbol label for summaries |
| token1_symbol | string | no | Optional token1 symbol label for summaries |
| token0_decimals | number | no | Optional token0 decimals for human-readable prices |
Query raw Solana instructions with program and account filters. COMMON USER ASKS: - Token Program instructions WHEN TO USE: - You need program-level or account-level instruction activity. - You want to inspect Token Program, Jupiter, System Program, or Anchor discriminator activity. DON'T USE: - You only need transaction-level activity and not individual instructions. EXAMPLES: - Token Program
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. Solana slots are ~400ms. |
| from_block | number | no | Starting slot number (use this OR timeframe) |
| to_block | number | no | Ending slot number. Keep ranges reasonable for performance. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized slots |
| program_id | no | Program IDs. You can pass a single string or an array. | |
| d1 | no | 1-byte discriminator filter (0x-prefixed hex). You can pass a single string or an array. | |
| d2 | no | 2-byte discriminator filter (0x-prefixed hex). You can pass a single string or an array. | |
| d4 | no | 4-byte discriminator filter (0x-prefixed hex). You can pass a single string or an array. | |
| d8 | no | 8-byte discriminator filter - Anchor (0x-prefixed hex). You can pass a single string or an array. | |
| a0 | no | Account at index 0. You can pass a single string or an array. | |
| a1 | no | Account at index 1. You can pass a single string or an array. | |
| a2 | no | Account at index 2. You can pass a single string or an array. | |
| a3 | no | Account at index 3. You can pass a single string or an array. | |
| a4 | no | Account at index 4. You can pass a single string or an array. | |
| a5 | no | Account at index 5. You can pass a single string or an array. | |
| a6 | no | Account at index 6. You can pass a single string or an array. | |
| a7 | no | Account at index 7. You can pass a single string or an array. |
Query raw Solana transactions with optional balances, rewards, logs, and instruction context. COMMON USER ASKS: - Recent Solana transactions - Filter by program WHEN TO USE: - You need raw Solana transaction records. - You want Solana-specific filters or include flags that convenience tools do not expose. DON'T USE: - You only want recent activity or a compact network summary. EXAMPLES: - Rece
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| from_block | number | no | Starting slot number (use this OR timeframe) |
| to_block | number | no | Ending slot number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized slots |
| fee_payer | array | no | Fee payer addresses |
| mentions_account | array | no | Accounts mentioned anywhere in the transaction |
| include_instructions | boolean | no | Include instruction data |
| include_balances | boolean | no | Include SOL balance changes |
| include_token_balances | boolean | no | Include SPL token balance changes |
| include_logs | boolean | no | Include program logs |
| include_rewards | boolean | no | Include block rewards (validator staking rewards). Filter by pubkey using mentions_account. |
| limit | integer | no | Max transactions to return (default: 20, max: 25) |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output, or stays 'full' when inline instruction, balance, log, or reward context is requested. Use 'summary' for aggregate stats. |
| cursor | string | no | Continuation cursor from a previous response |
Get the big picture for Solana throughput, fees, wallet activity, and optional top-program usage. COMMON USER ASKS: - Solana network snapshot - Include top programs FIRST CHOICE FOR: - the big picture for Solana right now WHEN TO USE: - You want the big picture for Solana right now. - You want a network health snapshot for Solana. - You want throughput, fee, success-rate, or top-program analyti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: solana-mainnet) |
| timeframe | string | no | Time range. Accepts compact durations like '15m' or natural phrases like 'past 30 minutes'. Optional; defaults to a 1h analysis window. |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| include_compute_units | boolean | no | Include average compute-unit stats across the full range (disabled by default for speed) |
| include_programs | boolean | no | Include top programs by instruction count (requires an extra instruction scan and is slower) |
| program_limit | number | no | Max top-program rows to return per page when include_programs is enabled |
| response_format | string | no | Response format: 'summary' (high-level metrics), 'compact' (core sections), 'full' (complete analytics). |
| cursor | string | no | Continuation cursor for paginating top_programs |
Query raw Bitcoin transactions and optionally attach inputs and outputs inline. COMMON USER ASKS: - Recent Bitcoin transactions - Attach inputs and outputs WHEN TO USE: - You need raw Bitcoin transaction records. - You want the UTXO envelope without switching to separate input/output tools. DON'T USE: - You only need a quick wallet or network summary. EXAMPLES: - Recent Bitcoin transactions: {
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: bitcoin-mainnet). Optional when continuing with cursor. |
| from_block | number | no | Starting block number |
| to_block | number | no | Ending block number |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| include_inputs | boolean | no | Attach transaction inputs inline |
| include_outputs | boolean | no | Attach transaction outputs inline |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps inline inputs and outputs in a smaller shape when requested. |
| limit | integer | no | Max transactions to return (default: 20, max: 25). With include_inputs or include_outputs and response_format "full", a page near the maximum can exceed the 50,000-byte response budget; the response_t |
| cursor | string | no | Continuation cursor from a previous response |
Get the big picture for Bitcoin block, fee, and address activity over a recent or explicit window. COMMON USER ASKS: - Bitcoin network snapshot FIRST CHOICE FOR: - the big picture for Bitcoin right now WHEN TO USE: - You want the big picture for Bitcoin right now. - You want a network-level Bitcoin snapshot. - You care about block cadence, fees, SegWit/Taproot adoption, or activity metrics. DO
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: bitcoin-mainnet) |
| timeframe | string | no | Time range: '1h' (~6 blocks), '6h' (~36 blocks), '24h' (~144 blocks). Default: '1h' |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| include_address_activity | boolean | no | Include unique address count and output value (requires extra queries, slower) |
| response_format | string | no | Response format: 'summary' (high-level metrics only), 'compact' (core sections, lighter payload), 'full' (complete analytics). |
Query raw Substrate or Polkadot event rows with pallet/event-name filters and optional parent call or extrinsic context. COMMON USER ASKS: - Balances.Transfer events on Polkadot FIRST CHOICE FOR: - raw Substrate or Polkadot event rows with optional parent call or extrinsic context WHEN TO USE: - You need raw event records on a Substrate network. - You want pallet-level event activity like Balan
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Substrate network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g. '1h', '24h'). Alternative to from_block/to_block. |
| from_block | number | no | Starting block number |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| event_names | array | no | Optional qualified event names like Balances.Transfer or System.ExtrinsicSuccess |
| include_extrinsic | boolean | no | Attach the parent extrinsic inline for each matching event |
| include_call | boolean | no | Attach the emitting call inline when the event has call context |
| include_stack | boolean | no | Attach the parent call stack when the event has nested call context |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested extrinsic or call context in a smaller inline shape. |
| limit | integer | no | Max events to return (max: 10; use compact mode for context-rich rows) |
| cursor | string | no | Continuation cursor from a previous response |
Query raw Substrate or Polkadot calls with pallet/call-name filters and optional child-call, emitted-event, or extrinsic context. COMMON USER ASKS: - Recent Balances calls - Polkadot calls with emitted events FIRST CHOICE FOR: - raw Substrate or Polkadot call rows, especially when you want the events emitted by those calls WHEN TO USE: - You need raw call records on a Substrate network. - You w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Substrate network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g. '1h', '24h'). Alternative to from_block/to_block. |
| from_block | number | no | Starting block number |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| call_names | array | no | Optional qualified call names like Timestamp.set or Balances.transfer_keep_alive |
| include_subcalls | boolean | no | Attach direct descendant calls inline for each matching call |
| include_extrinsic | boolean | no | Attach the parent extrinsic inline for each matching call |
| include_stack | boolean | no | Attach the parent call stack for each matching call |
| include_events | boolean | no | Attach events emitted directly by each matching call |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested subcalls, events, and extrinsic context in a smaller inline shape. |
| limit | integer | no | Max calls to return (max: 10; use compact mode for context-rich rows) |
| cursor | string | no | Continuation cursor from a previous response |
Analytics snapshot for Substrate or Polkadot activity in an indexed window, with event, call, and extrinsic counts plus top event and call names. COMMON USER ASKS: - Polkadot activity snapshot - Big picture for Polkadot activity - How is Polkadot doing? FIRST CHOICE FOR: - Polkadot activity analytics in an indexed window - how Polkadot is doing in an indexed window - analytics snapshot for Polka
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Substrate network name (default: polkadot) |
| timeframe | string | no | Time range like '1h', '6h', or '24h'. Default: '1h' |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| response_format | string | no | Response format: 'summary' (headline metrics only), 'compact' (core sections), 'full' (full dashboard payload) |
| section_limit | number | no | Max rows to keep in ranked event and call sections |
Query raw individual Hyperliquid fills with trader, coin, fee, PnL, and builder context. COMMON USER ASKS: - Recent BTC fills WHEN TO USE: - You need raw fill records on Hyperliquid. - You want to filter by trader, coin, direction, builder, or fee token. DON'T USE: - You want the big picture, top traders, grouped aggregates, or candles instead of raw fill rows. EXAMPLES: - Recent BTC fills: {"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: 'hyperliquid-fills'). Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| user | array | no | Trader wallet addresses (0x-prefixed, lowercase) |
| coin | array | no | Asset symbols (e.g., "ETH", "BTC", "SOL") |
| dir | array | no | Trade direction: "Open Long", "Close Long", "Open Short", "Close Short" |
| builder | array | no | Builder addresses (0x-prefixed, lowercase) |
| fee_token | array | no | Fee token symbols |
| cloid | array | no | Client order IDs (0x-prefixed hex) |
| limit | integer | no | Requested fills per page (default: 20). Values up to the retained compatibility maximum of 200 are accepted, while each response is safely capped at 25 rows and remains cursorable. |
| include_pnl | boolean | no | Include closedPnl and startPosition fields |
| include_builder_info | boolean | no | Include builder and builderFee fields |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for aggregate stats or 'full' when you truly need every fill field. |
| cursor | string | no | Continuation cursor from a previous response |
Get the big-picture Hyperliquid fill analytics with top traders, volume by coin, fees, and PnL. COMMON USER ASKS: - Hyperliquid fill snapshot - Who traded the most? WHEN TO USE: - You want network-level Hyperliquid fill analytics. - You want to know who traded the most, which coins had volume, or how fees and PnL looked. - You want grouped aggregate sections without stitching raw fills together
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: 'hyperliquid-fills') |
| timeframe | string | no | Time range: '1h', '6h', '24h'. Default: '1h' |
| mode | string | no | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| coin | array | no | Filter by asset symbols (e.g., ["BTC", "ETH"]) |
| response_format | string | no | Response format: 'summary' (smallest snapshot), 'compact' (chat-sized ranked sections, default), 'full' (complete analytics). |
| section_limit | number | no | Per-section page size for ranked sections. Default: 6 |
| cursor | string | no | Continuation cursor for ranked analytics sections |
Build chart-ready Hyperliquid trade OHLC candles with fixed buckets and auto intervals. COMMON USER ASKS: - BTC candles WHEN TO USE: - You want candles for one coin on Hyperliquid. - You need chart-ready OHLC, volume, and VWAP data from fills. DON'T USE: - You want scalar time-series buckets or raw fills. EXAMPLES: - BTC candles: {"network":"hyperliquid-fills","coin":"BTC","duration":"6h","int
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: 'hyperliquid-fills') |
| coin | string | no | Asset symbol to build candles for (for example: "BTC", "ETH", "SOL"). Optional when continuing with cursor. |
| interval | string | no | Candle interval. Use auto for chart-friendly defaults: 1h→5m, 6h→15m, 12h→30m, 24h→1h. |
| duration | string | no | How much recent trading history to cover when exact timestamps are omitted. Defaults to "1h". Accepts compact durations like "1h" or natural phrases like "past 30 minutes". |
| from_timestamp | no | Exact candle-window start. Use together with to_timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input. | |
| to_timestamp | no | Exact inclusive candle-window end. Use together with from_timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input. | |
| user | string | no | Optional trader wallet address (0x-prefixed, lowercase) |
| cursor | string | no | Continuation cursor from a previous candle page |
Query raw Tron transactions: native TRX transfers, TRC-10 asset transfers, TriggerSmartContract calls by contract and method, or any contract type, with optional inline logs and internal transactions. COMMON USER ASKS: - Recent native TRX transfers - USDT transfer calls in a block window - TRX sent from one wallet FIRST CHOICE FOR: - native TRX transfers, TRC-10 transfers, and smart-contract cal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: tron-mainnet). Optional when continuing with cursor. |
| from_block | number | no | Starting block number |
| to_block | number | no | Ending block number. Tron produces a block every 3 seconds. |
| timeframe | string | no | Time range (e.g., '5m', '1h'). Alternative to from_block/to_block. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| kind | string | no | Which Tron transaction family to query: transfer (native TRX), transfer_asset (TRC-10), trigger_smart_contract (contract calls), all (any contract type, filter by types only). auto picks from the filt |
| types | array | no | FILTER (kind=all): Tron contract types such as TransferContract, TriggerSmartContract, DelegateResourceContract. |
| from_addresses | array | no | FILTER: sender or caller addresses. Accepts Base58 (T...), 41-prefixed hex, or 0x/bare 20-byte hex. |
| to_addresses | array | no | FILTER (transfer, transfer_asset): recipient addresses in any accepted form. |
| contract_addresses | array | no | FILTER (trigger_smart_contract): called contract addresses in any accepted form, e.g. USDT. |
| method | no | FILTER (trigger_smart_contract): method alias such as transfer, approve, transferFrom, or a 4-byte sighash. | |
| sighash | array | no | FILTER (trigger_smart_contract): 4-byte method selectors, with or without 0x. Merges with method. |
| asset | array | no | FILTER (transfer_asset): TRC-10 asset id such as 1005157, or the raw hex asset name. |
| include_logs | boolean | no | Attach the event logs each transaction emitted |
| include_internal_transactions | boolean | no | Attach the internal transactions of each transaction |
| finalized_only | boolean | no | Only query finalized blocks |
| max_scan_blocks | integer | no | Safety cap for filtered latest-first scans. Default: min(window, 50000). |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for counts by type, TRX moved, and top callers. |
| limit | integer | no | Max transactions to return (default: 20, max: 25) |
Query raw Tron (TVM) event logs by contract address and topics with common event aliases, the parent transaction hash on every row, and optional inline decoding. COMMON USER ASKS: - Recent USDT transfers on Tron - USDT transfers received by one wallet FIRST CHOICE FOR: - TRC-20 token transfer events on Tron such as USDT - contract event evidence on Tron with the parent transaction hash WHEN TO
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: tron-mainnet). Optional when continuing with cursor. |
| from_block | number | no | Starting block number |
| to_block | number | no | Ending block number. Tron produces a block every 3 seconds. |
| timeframe | string | no | Time range (e.g., '5m', '1h'). Alternative to from_block/to_block. |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| addresses | array | no | FILTER: emitting contract addresses in any form (Base58 T..., 41-prefixed hex, 0x or bare 20-byte hex). Always include this or topic0 for fast queries. |
| event | no | FILTER: common event alias (transfer, approval, swap, mint, burn) or a topic0 hash. Merges with topic0. | |
| topic0 | array | no | FILTER: event signature hashes, with or without 0x. |
| topic1 | array | no | FILTER: indexed parameter 1 (often the sender). An address in any form is padded to a topic. |
| topic2 | array | no | FILTER: indexed parameter 2 (often the recipient). An address in any form is padded to a topic. |
| topic3 | array | no | FILTER: indexed parameter 3. |
| include_transaction | boolean | no | Attach the parent transaction (type, caller, contract, result, fee). The hash is always attached. |
| decode | boolean | no | Decode known event signatures inline with Base58 addresses |
| finalized_only | boolean | no | Only query finalized blocks |
| max_scan_blocks | integer | no | Safety cap for filtered latest-first scans. Default: min(window, 50000). |
| response_format | string | no | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for counts by contract and event. |
| limit | integer | no | Max logs to return (default: 20, max: 25) |
| cursor | string | no | Continuation cursor from a previous response |
ADVANCED: Query raw block records directly for EVM, Solana, or Bitcoin. COMMON USER ASKS: - Recent Base blocks WHEN TO USE: - You are debugging Portal coverage or block-level fields. - You need raw block records instead of transactions, logs, or summaries. DON'T USE: - You are answering a normal end-user question; prefer recent activity, time series, or raw transaction tools first. EXAMPLES: -
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name or alias. Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| limit | number | no | Max blocks to return (default: 20). Note: Lower default for MCP to reduce context usage. |
| include_l2_fields | boolean | no | Include L2-specific fields (auto-detected for L2 chains) |
| field_preset | string | no | Field preset for EVM datasets: 'minimal' (number+timestamp+gas), 'standard' (+hash+miner+size), 'full' (all block fields). Ignored for Solana/Bitcoin. |
| cursor | string | no | Continuation cursor from a previous response |
ADVANCED: Resolve a timestamp to the nearest indexed block or slot. COMMON USER ASKS: - Resolve one hour ago on Base - Resolve an older time on Polkadot WHEN TO USE: - You are debugging timestamp windows or building a manual block-range query. - You want to inspect exact versus estimated timestamp-to-block resolution. DON'T USE: - You just want to query by time; most public tools already accept
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | yes | Network name or alias |
| timestamp | yes | Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago" |
ADVANCED: Query Hyperliquid replica-command actions such as orders, cancels, and leverage updates. COMMON USER ASKS: - Recent order action WHEN TO USE: - You are debugging Hyperliquid replica-command records. - You need raw order-action events instead of fills or analytics. DON'T USE: - You only need public trading activity; fills and analytics are usually the better fit. EXAMPLES: - Recent or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Network name (default: 'hyperliquid-replica-cmds'). Optional when continuing with cursor. |
| timeframe | string | no | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| from_block | number | no | Starting block number (use this OR timeframe) |
| to_block | number | no | Ending block number |
| from_timestamp | no | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". | |
| to_timestamp | no | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". | |
| finalized_only | boolean | no | Only query finalized blocks |
| action_type | array | no | Action types to filter |
| user | array | no | User wallet addresses (0x-prefixed, lowercase) |
| vault_address | array | no | Vault addresses (0x-prefixed, lowercase) |
| status | string | no | Filter by action status |
| limit | integer | no | Max actions to return (1). Replica command payloads can contain large batches, so this exact one-record cursor page is the verified safe response budget. |
| cursor | string | no | Continuation cursor from a previous response |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SQD or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.8.5.
0.8.5
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SQD can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.