Portal MCP Server for AI Agents

The Portal MCP server is experimental. Available tools and behavior may change.

Connect the Portal MCP server to your favorite AI coding clients. MCP (Model Context Protocol) is an open-source standard for connecting AI applications to external systems. The Portal MCP server gives your agent direct access to blockchain data across 130+ networks. Discover datasets, query transactions and logs, analyze wallets, and compare chains.

Using an AI coding client? Install SQD for Claude Code, Codex, Grok Build, Gemini CLI, or Cursor to get the MCP server and agent skills together.

Connect Portal MCP

MCP endpoint: https://portal.sqd.dev/mcp
Server version: 0.8.4
Authentication: none on the public server

Claude Code
Claude
Grok
Cursor
VS Code

claude mcp add --transport http sqd-portal https://portal.sqd.dev/mcp

Test the connection:

claude mcp list

See the Claude Code documentation for more details.

SQD is in the Claude Directory. Add it in one click, no custom connector setup. See the Claude Connector guide.

Add the SQD connector from the directory

Open the SQD connector in the Claude Directory and select Connect. No sign-in or API key is required.

Enable it in your chat

Select the + button (or type /) in the message box.
Hover over Connectors and toggle on SQD.
Ask Claude questions about blockchain data from Portal.

Prefer to add it by URL instead? Add a custom connector pointing at https://portal.sqd.dev/mcp. See the Model Context Protocol documentation for more details.

Open Grok Connectors

Go to grok.com/connectors, select New Connector, then choose Custom.

Add SQD

Name the connector SQD and enter https://portal.sqd.dev/mcp as the MCP server URL. No authentication is required.

Try the connection

Start a new conversation and ask “Which blockchain networks can SQD query?” Grok should use the SQD tools to answer.

Using Grok Build instead? Install the SQD plugin for Grok to get the MCP tools and four coding skills together.

Open MCP settings

Use Command + Shift + P (Ctrl + Shift + P on Windows) to open the command palette.
Search for “Open MCP settings”.
Select Add custom MCP. This opens the mcp.json file.

Configure the Portal MCP server

In mcp.json, add:

{
  "mcpServers": {
    "sqd-portal": {
      "url": "https://portal.sqd.dev/mcp"
    }
  }
}

Test the connection

In Cursor’s chat, ask “What tools do you have available?” Cursor should show the Portal MCP server as an available tool.

See the Cursor documentation for more details.

Create a .vscode/mcp.json file and add:

{
  "servers": {
    "sqd-portal": {
      "type": "http",
      "url": "https://portal.sqd.dev/mcp"
    }
  }
}

See the VS Code documentation for more details.

Factuality and completeness in v0.8.4

Portal MCP v0.8.4 checks the data behind an answer instead of treating a successful request as proof that the answer is complete.

Verified time windows. Timestamp boundaries are checked against indexed block timestamps across live datasets. The response shows the requested and analyzed window and rejects a future start time instead of silently moving it to the indexed head.
Stable evidence identities. Normalized transactions, logs, calls, events, instructions, inputs, outputs, fills, and actions have stable row identifiers. Missing or duplicate identifiers fail the request rather than producing ambiguous evidence.
Exact continuation. Cursor pages preserve every accepted row without duplicates or gaps, including multiple matching records in one block.
Reconciled totals. Wallet quantities, transaction counts, aggregates, and OHLC summaries use the returned evidence and exact integer units where required. Release checks reproduce material results from direct Portal queries.
Bounded, honest failures. Response limits are measured on the actual MCP payload. Upstream overloads, timeouts, and incomplete results return structured retry guidance instead of partial data presented as complete.
Current MCP protocol. Stateless HTTP supports MCP 2026-07-28, including server discovery, request metadata, routing headers, and cache hints. Older clients continue through the SDK compatibility path.

Blockchain Activity Explorer

MCP App hosts can show SQD results in the Blockchain Activity Explorer. It presents exact metrics, multi-series charts, price candles with volume, evidence tables, timelines, coverage, freshness, and continuation controls without changing the underlying answer. The explorer covers wallet and contract activity, token flows, network metrics, Bitcoin, Solana, Substrate, Hyperliquid fills, analytics, and price candles. Tron dataset discovery, head, freshness, and timestamp evidence remain available through the MCP metadata tools. Use linked overview, chart, evidence, and investigation sections; inspect exact chart values with a pointer or keyboard; sort and filter evidence; run a range-focused follow-up; retain investigations during the current app session; export received evidence as JSON or CSV; and request the next signed page when one is available. Missing time buckets remain visible as gaps, and local display limits are separate from server completeness. The explorer uses the SQD Design System and stays on a compact dark surface inside both light and dark hosts. App support depends on the client. Clients that support only standard MCP tools still receive the same data. Clients without MCP App support receive the same structured result and text fallback. The server never depends on the visual interface to provide blockchain data.

Reproducible investigations

Three built-in MCP prompts provide guided starting points without adding more query tools:

investigate-wallet for a wallet’s bounded activity and evidence trail
investigate-contract for interactions, callers, and emitted events
investigate-market for fills, candles, volume, and market context

Material successful results include an _evidence receipt. It records the canonical tool arguments, argument and exact-data digests, source and analyzed windows, row reconciliation, completeness, and whether replay uses a pinned evidence window or a moving semantic window. Use the receipt together with _coverage, _freshness, _ordering, and _pagination before treating an answer as complete.

Available tools

The server exposes 28 read-only tools: 25 query and analytics tools plus 3 low-level diagnostic tools. They cover EVM, Solana, Bitcoin, Substrate, and Hyperliquid data. Every tool uses the same pagination, error, and coverage format so the client can tell whether a result is complete or partial.

Discovery & shared

Tool	Description
`portal_list_networks`	Find the right network or alias across EVM, Solana, Bitcoin, Substrate, and Hyperliquid. First stop when you’re not sure which dataset to query.
`portal_get_network_info`	Check if a network is indexed, fresh, caught up, or behind, and see which tables are available.
`portal_get_head`	Get just the latest or finalized head block or slot for a network.
`portal_resolve_entity`	Resolve token symbols, contract aliases, pool IDs, protocol names, and Hyperliquid coins into query-ready addresses and filters before building a query.
`portal_get_recent_activity`	Cross-VM recent-activity feed with chronological paging. Simplest answer to “what’s been happening on X lately?”.
`portal_get_wallet_summary`	One-call wallet analysis across supported VMs. Overview, activity, and assets.
`portal_get_time_series`	Chart-ready metric buckets over time with optional compare-to-previous and EVM contract grouping.

EVM

Tool	Description
`portal_evm_query_transactions`	Query raw EVM transactions with optional logs, traces, and state-diff context via include flags.
`portal_evm_query_logs`	Query raw EVM logs with address/topic filters and optional inline decoding.
`portal_evm_query_token_transfers`	Token-transfer activity on EVM without needing to remember the Transfer event signature.
`portal_evm_get_analytics`	Network-wide EVM snapshot with ranked top contracts and compact overview metrics.
`portal_evm_get_contract_activity`	Contract-centric summary: recent interactions, unique callers, and optional event activity.
`portal_evm_get_contract_deployment`	Look up the deployment block, transaction, and deployer for any EVM contract address.
`portal_evm_get_ohlc`	Experimental. DEX OHLC candles plus a recent-trade tape from Uniswap v2/v3/v4 and Aerodrome Slipstream swaps.

Solana

Tool	Description
`portal_solana_query_transactions`	Query raw Solana transactions with optional balances, token balances, rewards, logs, and instruction context.
`portal_solana_query_instructions`	Query raw instructions with program, account, and Anchor-discriminator filters.
`portal_solana_get_analytics`	Solana throughput, fee, wallet activity, and optional top-program snapshot.

Bitcoin

Tool	Description
`portal_bitcoin_query_transactions`	Query raw Bitcoin transactions with optional inline inputs and outputs.
`portal_bitcoin_get_analytics`	Bitcoin block cadence, fees, SegWit/Taproot adoption, and address activity snapshot.

Hyperliquid

Tool	Description
`portal_hyperliquid_query_fills`	Query trade fills with PnL, fees, and routing.
`portal_hyperliquid_get_analytics`	Trading volume, top coins, and trader rankings.
`portal_hyperliquid_get_ohlc`	OHLC candles for Hyperliquid markets.

Substrate

Tool	Description
`portal_substrate_query_calls`	Query Polkadot-, Kusama-, and other Substrate-style extrinsic calls with pallet and method filters.
`portal_substrate_query_events`	Query Substrate events emitted by runtime pallets.
`portal_substrate_get_analytics`	Substrate network-wide snapshot: block cadence, extrinsic volume, and top pallets.

Debug

Tool	Description
`portal_debug_query_blocks`	Inspect raw blocks across VMs for schema debugging.
`portal_debug_resolve_time_to_block`	Resolve a timestamp to a block or slot for any supported network.
`portal_debug_hyperliquid_query_replica_commands`	Low-level access to Hyperliquid replica commands (orders, cancels, transfers, leverage updates).

Response size and pagination

The MCP query tools return a bounded page of results plus a _pagination.next_cursor when more matching rows are available. The page is sized to fit an AI context window, so one call may return a preview rather than the whole range. Pass next_cursor back until _coverage.result_complete is true, or tighten the filters. Check _coverage.window_complete separately. A complete result page can still cover only the scanned part of a wider requested window. The server keeps this distinction explicit and never silently removes rows to fit a response. Heavy ranges are not hard-rejected. A wide request, such as a large Solana slot range, returns data together with a soft notice that results are capped by limit and the query may still be heavy. There is no fixed slot-range guard that refuses the query. The underlying Stream API behaves differently: it has no per-response page cap and streams the full result at HTTP 200 (bounded only server-side), and you paginate it by resuming from lastBlock + 1 rather than a cursor. The MCP’s paging is a separate convenience layer for AI clients, not a limit on the HTTP API.

Known limitations

Portal MCP is designed for bounded answers inside an AI conversation. Broad, unfiltered scans on dense networks can return partial coverage or reach the request timeout. Check the coverage and pagination fields, narrow the filters, or request the next page. Use the raw Portal Stream API or an indexer for complete exports and recurring workloads.

Claude Code Plugin. One-command plugin install for Claude Code
Codex Plugin. One-command plugin install for Codex
Grok Plugin. Install SQD in Grok Build or connect Grok on the web
Gemini CLI Extension. Install SQD in Gemini CLI
Cursor Plugin. Install SQD in Cursor
AI Development Overview. Resources for building AI agents with SQD
Portal API Reference. HTTP API for blockchain data
Documentation MCP Server. Search SQD documentation
Pipes SDK. TypeScript SDK for custom pipelines
llms.txt. Documentation index for LLMs

AI Development

MCP Servers

Plugins

OpenAPI Schemas

Portal MCP Server for AI Agents

Connect Portal MCP

Factuality and completeness in v0.8.4

Blockchain Activity Explorer

Reproducible investigations

Available tools

Discovery & shared

EVM

Solana

Bitcoin

Hyperliquid

Substrate

Debug

Known limitations

​Connect Portal MCP

​Factuality and completeness in v0.8.4

​Blockchain Activity Explorer

​Reproducible investigations

​Available tools

​Discovery & shared

​EVM

​Solana

​Bitcoin

​Hyperliquid

​Substrate

​Debug

​Response size and pagination

​Known limitations

​Related

Connect Portal MCP

Factuality and completeness in v0.8.4

Blockchain Activity Explorer

Reproducible investigations

Available tools

Discovery & shared

EVM

Solana

Bitcoin

Hyperliquid

Substrate

Debug

Response size and pagination

Known limitations

Related