portal_list_networksLABSCO SUMMARY
One question shape across five chain families.
The path it wants is resolve first, then drill: turn a symbol or alias into a filter, start a wallet question with the summary, and reach for raw queries only once the summary points somewhere. Responses come back compact unless you ask for the full payload.
What it is
A query wrapper over the SQD Portal API. It does not index chains itself: it validates what you ask, maps it onto Portal requests, and returns responses shaped for an agent to read.
What you get
- The networks Portal covers, one network's details, and its current head
- Token symbols, contract aliases, pool identifiers and protocol names resolved into query-ready filters
- A wallet summary with fund flow, asset movement, counterparties and the largest movements observed
- Recent activity and time series across chains
- EVM transactions, logs, token transfers, contract deployment and activity, analytics and OHLC
- Solana transactions, instructions and analytics
- Bitcoin transactions and analytics
- Substrate events, calls and analytics
- Hyperliquid fills, analytics and OHLC
- Debug tools for blocks and time-to-block resolution
Requirements
Access to the SQD Portal API — the server holds no chain data of its own and answers only what Portal indexes.
Setup effort
Add the hosted endpoint — paste it into your client
USE CASES
01
Following the money through a wallet
The summary gives inbound and outbound flow, counterparties and the biggest movements before you touch a raw query.
02
Turning a token symbol into something queryable
Resolution comes from open token-list data and keeps ambiguous matches explicit, rather than silently picking one address.
03
Investigating a contract's history
When it was deployed, what it has been doing since, and the logs behind a particular period.
04
Charting price or activity over time
Time series and OHLC on the same interface, whether the venue is an EVM chain or Hyperliquid.
05
Asking the same question on a non-EVM chain
Solana instructions, Bitcoin transactions and Substrate events answer to the same query pattern, so the chain stops dictating the tooling.
06
Checking how current the data is
The head and the network details tell you how far behind the index is before you draw a conclusion from it.
28 tools
Listed in project docs. Your client may show a different list.
portal_get_network_infoportal_get_headportal_resolve_entityportal_get_recent_activityportal_get_wallet_summaryportal_get_time_seriesportal_evm_query_transactionsportal_evm_query_logsportal_evm_query_token_transfersportal_evm_get_contract_deploymentportal_evm_get_contract_activityportal_evm_get_analyticsportal_evm_get_ohlcportal_solana_query_transactionsportal_solana_query_instructionsportal_solana_get_analyticsportal_bitcoin_query_transactionsportal_bitcoin_get_analyticsportal_substrate_query_eventsportal_substrate_query_callsportal_substrate_get_analyticsportal_hyperliquid_query_fillsportal_hyperliquid_get_analyticsportal_hyperliquid_get_ohlcportal_debug_query_blocksportal_debug_resolve_time_to_blockportal_debug_hyperliquid_query_replica_commandsBEFORE YOU INSTALL
What to know first
Tools you get
28 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
ENDPOINT URL
https://portal.sqd.dev/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Code — plugin
CLAUDE CODE — PLUGIN · TERMINAL
claude plugin marketplace add subsquid-labs/portal-mcp-server
claude plugin install portal@sqdCodex — plugin
CODEX — PLUGIN · TERMINAL
git clone https://github.com/subsquid-labs/portal-mcp-server
cd portal-mcp-server
codex plugin marketplace add .
codex plugin add portal@sqdClaude Desktop — local stdio
CLAUDE DESKTOP — LOCAL STDIO · TERMINAL
git clone https://github.com/subsquid-labs/portal-mcp-server
cd portal-mcp-server
npm install
npm run buildAdd an entry like this to claude_desktop_config.json:
CLAUDE DESKTOP — LOCAL STDIO · JSON
{
"mcpServers": {
"SQD": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PORTAL_MCP_SERVER>/dist/index.js"
]
}
}
}Self-host — HTTP
SELF-HOST — HTTP · TERMINAL
git clone https://github.com/subsquid-labs/portal-mcp-server
cd portal-mcp-server
npm install
npm run build
npm run start:http
