SQD is an MCP server with 31 tools an agent can call, among them portal_bitcoin_get_analytics, portal_bitcoin_query_transactions, portal_debug_hyperliquid_query_replica_commands. It answers at https://portal.sqd.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Query 130+ SQD Portal datasets across blockchains, including native Tron transactions and events.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
portal_bitcoin_get_analytics | 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 pictur Inputs: network, timeframe, mode, from_block, to_block, from_timestamp |
portal_bitcoin_query_transactions | 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 envelop Inputs: network, from_block, to_block, timeframe, from_timestamp, to_timestamp |
portal_debug_hyperliquid_query_replica_commands | 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 eve Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_debug_query_blocks | 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, log Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_debug_resolve_time_to_block | 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 que Inputs: network, timestamp |
portal_evm_get_analytics | 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 Inputs: network, num_blocks, timeframe, from_timestamp, to_timestamp, limit |
portal_evm_get_contract_activity | 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 d Inputs: network, contract_address, timeframe, from_timestamp, to_timestamp, include_events |
portal_evm_get_contract_deployment | 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: - w Inputs: network, contract_address, contract, timeframe, from_block, to_block |
portal_evm_get_ohlc | 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 c Inputs: network, pool_address, pool_id, pool_manager_address, source, interval |
portal_evm_query_logs | 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 Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_evm_query_token_transfers | 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 Inputs: network, from_block, to_block, timeframe, from_timestamp, to_timestamp |
portal_evm_query_traces | 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 Inputs: network, from_block, to_block, timeframe, from_timestamp, to_timestamp |
portal_evm_query_transactions | 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 fo Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_get_head | 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 curren Inputs: network, type |
portal_get_network_info | 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: - Y Inputs: network |
portal_get_recent_activity | 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 Inputs: network, timeframe, from_timestamp, to_timestamp, from_addresses, to_addresses |
portal_get_time_series | 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: Inputs: network, metric, interval, duration, address, from_timestamp |
portal_get_wallet_summary | 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 Inputs: network, address, timeframe, from_timestamp, to_timestamp, include_tokens |
portal_hyperliquid_get_analytics | 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 wan Inputs: network, timeframe, mode, from_timestamp, to_timestamp, coin |
portal_hyperliquid_get_ohlc | 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 fil Inputs: network, coin, interval, duration, from_timestamp, to_timestamp |
portal_hyperliquid_query_fills | 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, Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_list_networks | 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 networ Inputs: vm, network_type, query, real_time_only, limit, cursor |
portal_resolve_entity | 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 lik Inputs: network, kind, query, limit |
portal_solana_get_analytics | 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 Inputs: network, timeframe, mode, from_timestamp, to_timestamp, include_compute_units |
portal_solana_query_instructions | 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 Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_solana_query_transactions | 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-speci Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_substrate_get_analytics | 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 Po Inputs: network, timeframe, mode, from_block, to_block, from_timestamp |
portal_substrate_query_calls | 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 Substra Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_substrate_query_events | 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 Inputs: network, timeframe, from_block, to_block, from_timestamp, to_timestamp |
portal_tron_query_logs | 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 Inputs: network, from_block, to_block, timeframe, from_timestamp, to_timestamp |
portal_tron_query_transactions | 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 t Inputs: network, from_block, to_block, timeframe, from_timestamp, to_timestamp |
Every block below points at https://portal.sqd.dev/mcp. Pick your client and copy.
claude mcp add --transport http sqd https://portal.sqd.dev/mcp
{
"mcpServers": {
"sqd": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://portal.sqd.dev/mcp"]
}
}
}{
"mcpServers": {
"sqd": {
"url": "https://portal.sqd.dev/mcp"
}
}
}{
"servers": {
"sqd": {
"type": "http",
"url": "https://portal.sqd.dev/mcp"
}
}
}{
"context_servers": {
"sqd": {
"url": "https://portal.sqd.dev/mcp"
}
}
}{
"mcpServers": {
"sqd": {
"serverUrl": "https://portal.sqd.dev/mcp"
}
}
}{
"mcpServers": {
"sqd": {
"url": "https://portal.sqd.dev/mcp"
}
}
}name: SQD
version: 0.0.1
schema: v1
mcpServers:
- name: SQD
type: streamable-http
url: https://portal.sqd.dev/mcp{
"mcpServers": {
"sqd": {
"httpUrl": "https://portal.sqd.dev/mcp"
}
}
}{
"mcpServers": {
"sqd": {
"type": "http",
"url": "https://portal.sqd.dev/mcp"
}
}
}{
"mcpServers": {
"sqd": {
"url": "https://portal.sqd.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fportal.sqd.dev%2Fmcp&type=streamable_http&id=sqd&name=SQD
It answered our last check on 24 October 2026 in 85 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
31, as returned by the server's own tools/list on 21 September 2026: portal_bitcoin_get_analytics, portal_bitcoin_query_transactions, portal_debug_hyperliquid_query_replica_commands, portal_debug_query_blocks, portal_debug_resolve_time_to_block, portal_evm_get_analytics, portal_evm_get_contract_activity, portal_evm_get_contract_deployment, and 23 more.
It answered our last check on 24 October 2026 in 85 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://portal.sqd.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.subsquid-labs. Endpoint host: portal.sqd.dev. ARD identifier: urn:air:io.github.subsquid-labs:mcp:portal-mcp-server.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.