SQD Portal
About
Query onchain data across EVM, Solana, Bitcoin, Substrate, and Hyperliquid through the SQD Portal API, available as a hosted remote endpoint or local stdio server.
Details
- Author
- subsquid-labs
- Categories
- Finance, Other
Jump to
Setup
Install SQD Portal in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/subsquid-labs/portal-mcp-server
Follow the installation instructions in the repository README, then restart your MCP client.
Thin MCP wrapper around theSQD Portal APIfor blockchain data queries.
This server does not index chains itself. It validates user input, maps it onto Portal requests, and returns MCP-friendly responses.
- 25public tools
- 3advanced/debug tools
- public params usenetwork
- discovery filters usevm
- no legacy tool aliases inv0.7.9
Raw query tools default to compact responses. Ask forresponse_format: "full"only when you need the larger payload.
Entity questions can useportal_resolve_entityfirst. It resolves EVM token symbols/addresses, EVM contract aliases, pool identifiers, protocol names, and Hyperliquid coin names into query-ready filters while keeping ambiguous matches explicit.
Token symbol resolution and token metadata come from open token-list data, not baked-in token address constants. Responses include explicit notices when token-list data is unavailable, stale, or unsupported for a network.
Wallet questions should start withportal_get_wallet_summary. It returnsfund_flowby default, including inbound/outbound movement, asset flows, counterparties, largest observed movements, and next evidence pivots before raw-tool drill-down.
- portal_list_networks
- portal_get_network_info
- portal_get_head
- portal_resolve_entity
- portal_get_recent_activity
- portal_get_wallet_summary
- portal_get_time_series
- portal_evm_query_transactions
- portal_evm_query_logs
- portal_evm_query_token_transfers
- portal_evm_get_contract_deployment
- portal_evm_get_contract_activity
- portal_evm_get_analytics
- portal_evm_get_ohlc
- portal_solana_query_transactions
- portal_solana_query_instructions
- portal_solana_get_analytics
- portal_bitcoin_query_transactions
- portal_bitcoin_get_analytics
- portal_substrate_query_events
- portal_substrate_query_calls
- portal_substrate_get_analytics
- portal_hyperliquid_query_fills
- portal_hyperliquid_get_analytics
- portal_hyperliquid_get_ohlc
- portal_debug_query_blocks
- portal_debug_resolve_time_to_block
- portal_debug_hyperliquid_query_replica_commands
- EVM networks indexed by Portal, including Base, Ethereum, Optimism, Arbitrum, Monad, Hyperliquid EVM, and others
- Solana mainnet
- Bitcoin mainnet
- Hyperliquid fills and replica commands
- Substrate networks indexed by Portal
Substrate support is currently historical only. It does not have a real-time tail.
Most tools return the same envelope in MCPstructuredContentand in a compact JSON text fallback for older clients. The envelope contains a normal result body plus shared metadata such as:
- answer
- display
- next_steps
- investigation
- _freshness
- _coverage
- _pagination
- _ordering
investigationis a compact evidence guide for agents: it identifies the primary result path, bounded window, useful pivot fields such as addresses or transaction hashes, follow-up filters, and limitations before a result is treated as complete.
When a response uses estimated, partial, sampled, capped, or paginated data, the top-level answer and metadata disclose it. Safe pagination follow-ups include executable tool-call metadata with explicit cursor arguments; suggestions that cannot be reconstructed safely are marked non-executable.
Chart-oriented tools also return chart and table descriptors so MCP clients or LLMs can render them without reverse-engineering the payload.
The server does not ship its own frontend. It returns structured data and rendering hints for the client to use.
The server exposes a structured tool-selection guide for client builders:
- MCP resourcesqd://toolsreturns grouped tool metadata, examples, starting points, and integration notes.
- MCP resourcesqd://tools/{name}returns the guide entry for one tool, for examplesqd://tools/portal_get_time_series.
- HTTPGET /toolsorGET /tools.jsonreturns the live tool catalog with input schemas plus the same structured guide metadata.
The Codex plugin wrapper lives inplugins/portaland defaults to the hosted MCP endpoint athttps://portal.sqd.dev/mcp.
Install it from this repo-local marketplace:
codex plugin marketplace add . codex plugin add portal@sqd
Open a new Codex thread after installing. First-use prompts include Hyperliquid BTC perp fills, recent Base transaction volume, and top USDC senders on Base.
The Claude Code plugin uses the same hosted MCP endpoint and the same public selector:
claude plugin marketplace add subsquid-labs/portal-mcp-server claude plugin install portal@sqd
Open a new Claude Code session after installing so the SQD MCP tools are loaded.
Add an entry like this toclaude_desktop_config.json:
{ "mcpServers": { "SQD": { "command": "node", "args": ["/absolute/path/to/sqd-portal-mcp-server/dist/index.js"] } } }
- If you do not know the exact network name, start withportal_list_networks.
- If you need recent indexed state, useportal_get_network_infoorportal_get_headfirst.
- If the question is broad, start withportal_get_recent_activity,portal_get_wallet_summary, orportal_get_time_seriesbefore dropping to raw queries.
- Time windows accept compact and natural wording such as30m,past 30 minutes,in the past 1h,in last 38 mins,last hour, or30 minutes ago.
- Useportal_evm_get_ohlcandportal_hyperliquid_get_ohlconly when you actually need candle-shaped output.
- For large or exploratory queries, preferresponse_format: "compact"unless you need the full record shape.
HTTP mode exposes health state at/healthand read-only tool discovery at/toolsand/tools.json.
- SetMCP_HTTP_BEARER_TOKENto requireAuthorization: Bearer <token>forPOST /andPOST /mcp.
- /healthand read-onlyGET /tools/GET /tools.jsonremain public.
- SetMCP_CURSOR_SECRETin production so pagination cursors are signed with a deployment-specific secret. Local development uses a deterministic fallback for convenience.
- MCP_HTTP_BEARER_TOKENto protect HTTP MCP POSTs
- MCP_CURSOR_SECRETto sign pagination cursors
npm test npm run test:tools npm run test:routing npm run test:substrate npm run test:timestamps npm run test:plugin npm run test:conversations npm run test:negative npm run test:quality npm run test:ci
Non-custodial stablecoin yield. Stablecoin Yield Index (SYX) + 12 USDC vault APYs across Ethereum, Base, Arbitrum.
Pay-per-call x402 data APIs for AI agents — token rug-check, on-chain reads, web search, and AI-visibility (does AI recommend a brand). USDC on Base, no API key.
Live cross-DEX crypto prices read from on-chain pool state: per-venue price, liquidity depth and gross cross-venue spread across BSC, Polygon, Arbitrum, Base, Avalanche and Optimism. Works keyless, no account.
MCP server for Base L2 DeFi operations with 9 monetized endpoints: gas estimates, yield farming, token analysis, contract audit, wallet health, DEX quotes, price feeds, mnemonic generation. Built with FastMCP Python SDK.
Crypto data & trading MCP with 42+ tools: prices, DeFi, NFTs, Solana swaps
DeFi execution on Base, Citrea, HyperEVM and Monad via Fibrous aggregation: swap quotes, swaps, transfers, cross-chain portfolio and Aave V3.
MCP server for Fuse Network: balances, tokens, staking, DeFi data, swaps and on-chain transactions.
Free token-safety scans plus paid x402 verdicts, signals, radar and EVM swap quotes for AI agents.
MCP server for the Ophis intent-based DEX aggregator: quotes and gasless, MEV-protected swap orders across 11 chains.
On-chain Solana token safety: screens a token for rug pulls, honeypots and mint/freeze authority traps before an agent trades.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



