SQD
REMOTE · PORTAL.SQD.DEV · SCANNED SEP 24
Query 130+ SQD Portal datasets across blockchains, including native Tron transactions and events.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- 55% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 17519 tokens (~449/item across 39 items; 31 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management86
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 8 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 31 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SQD MCP server?
SQD is a hosted endpoint at https://portal.sqd.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · portal.sqd.dev
claude mcp add --transport http subsquid-labs-portal-mcp-server 'https://portal.sqd.dev/mcp'
{
"mcpServers": {
"subsquid-labs-portal-mcp-server": {
"url": "https://portal.sqd.dev/mcp"
}
}
} {
"servers": {
"subsquid-labs-portal-mcp-server": {
"type": "http",
"url": "https://portal.sqd.dev/mcp"
}
}
} [mcp_servers.subsquid-labs-portal-mcp-server] url = "https://portal.sqd.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"subsquid-labs-portal-mcp-server": {
"type": "remote",
"url": "https://portal.sqd.dev/mcp",
"enabled": true
}
}
} openclaw mcp add subsquid-labs-portal-mcp-server --url 'https://portal.sqd.dev/mcp' --transport streamable-http
mcp_servers:
subsquid-labs-portal-mcp-server:
url: "https://portal.sqd.dev/mcp" {
"McpServers": {
"subsquid-labs-portal-mcp-server": {
"Transport": "http",
"Url": "https://portal.sqd.dev/mcp"
}
}
} assistant mcp add subsquid-labs-portal-mcp-server -t streamable-http -u 'https://portal.sqd.dev/mcp'
{
"mcpServers": {
"subsquid-labs-portal-mcp-server": {
"type": "http",
"url": "https://portal.sqd.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 8 Sept 26 0
- Resource “sqd-blockchain-activity-explorer” now points somewhere else: ui://sqd/activity-explorer.2739daedf676.html → ui://sqd/activity-explorer.7e6b85590c27.html security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 404 → 449 ▼ functional
- Server version: 0.8.4 → 0.8.5 functional
- New tool “portal_evm_query_traces” functional
- New tool “portal_tron_query_logs” functional
- New tool “portal_tron_query_transactions” functional
- “portal_bitcoin_query_transactions” reworded the description of “limit” cosmetic
- “portal_get_time_series” reworded the description of “duration” cosmetic
- “portal_get_time_series” reworded the description of “metric” cosmetic
- 2 Sept 26 +1
- Resource “sqd-blockchain-activity-explorer” now points somewhere else: ui://sqd/activity-explorer.383ddd6e2c61.html → ui://sqd/activity-explorer.2739daedf676.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “portal_bitcoin_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_bitcoin_query_transactions” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_contract_activity” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_contract_deployment” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_ohlc” rewrote its description, which is the text the model reads security
- Tool “portal_evm_query_logs” rewrote its description, which is the text the model reads security
- Tool “portal_evm_query_token_transfers” rewrote its description, which is the text the model reads security
- Tool “portal_evm_query_transactions” rewrote its description, which is the text the model reads security
- Tool “portal_get_recent_activity” rewrote its description, which is the text the model reads security
- Tool “portal_get_time_series” rewrote its description, which is the text the model reads security
- Tool “portal_get_wallet_summary” rewrote its description, which is the text the model reads security
- Tool “portal_hyperliquid_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_hyperliquid_get_ohlc” rewrote its description, which is the text the model reads security
- Tool “portal_hyperliquid_query_fills” rewrote its description, which is the text the model reads security
- Tool “portal_solana_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_solana_query_instructions” rewrote its description, which is the text the model reads security
- Tool “portal_solana_query_transactions” rewrote its description, which is the text the model reads security
- Tool “portal_substrate_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_substrate_query_calls” rewrote its description, which is the text the model reads security
- Tool “portal_substrate_query_events” rewrote its description, which is the text the model reads security
- Schema quality: 456 → 404 ▲ functional
- Schema quality: 44% → 55% ▲ functional
- New resource “sqd-blockchain-activity-explorer-compat-1” functional
- New resource “sqd-blockchain-activity-explorer-compat-2” functional
- “portal_hyperliquid_get_ohlc” added an optional parameter “from_timestamp” cosmetic
- “portal_hyperliquid_get_ohlc” added an optional parameter “to_timestamp” cosmetic
- “portal_get_wallet_summary” reworded the description of “limit_per_type” cosmetic
- “portal_hyperliquid_get_ohlc” reworded the description of “duration” cosmetic
- “portal_hyperliquid_query_fills” reworded the description of “limit” cosmetic
- 31 Aug 26 −2
- Stability: pass → fail ▼ security
- Resource “sqd-blockchain-activity-explorer” now points somewhere else: ui://sqd/activity-explorer.457443ca1623.html → ui://sqd/activity-explorer.383ddd6e2c61.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “portal_bitcoin_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_bitcoin_query_transactions” rewrote its description, which is the text the model reads security
- Tool “portal_debug_hyperliquid_query_replica_commands” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_contract_activity” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_contract_deployment” rewrote its description, which is the text the model reads security
- Tool “portal_evm_get_ohlc” rewrote its description, which is the text the model reads security
- Tool “portal_evm_query_logs” rewrote its description, which is the text the model reads security
- Tool “portal_evm_query_token_transfers” rewrote its description, which is the text the model reads security
- Tool “portal_evm_query_transactions” rewrote its description, which is the text the model reads security
- Tool “portal_get_recent_activity” rewrote its description, which is the text the model reads security
- Tool “portal_get_time_series” rewrote its description, which is the text the model reads security
- Tool “portal_get_wallet_summary” rewrote its description, which is the text the model reads security
- Tool “portal_hyperliquid_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_hyperliquid_get_ohlc” rewrote its description, which is the text the model reads security
- Tool “portal_hyperliquid_query_fills” rewrote its description, which is the text the model reads security
- Tool “portal_solana_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_solana_query_instructions” rewrote its description, which is the text the model reads security
- Tool “portal_solana_query_transactions” rewrote its description, which is the text the model reads security
- Tool “portal_substrate_get_analytics” rewrote its description, which is the text the model reads security
- Tool “portal_substrate_query_calls” rewrote its description, which is the text the model reads security
- Tool “portal_substrate_query_events” rewrote its description, which is the text the model reads security
- “portal_debug_hyperliquid_query_replica_commands” changed the type of “limit”: number → integer ▼ functional
- “portal_evm_query_logs” changed the type of “limit”: number → integer ▼ functional
- “portal_evm_query_transactions” changed the type of “limit”: number → integer ▼ functional
- “portal_get_recent_activity” changed the type of “limit”: number → integer ▼ functional
- “portal_get_wallet_summary” changed the type of “limit_per_type”: number → integer ▼ functional
- “portal_solana_query_instructions” changed the type of “limit”: number → integer ▼ functional
- “portal_substrate_query_calls” changed the type of “limit”: number → integer ▼ functional
- “portal_substrate_query_events” changed the type of “limit”: number → integer ▼ functional
- Server version: 0.8.3 → 0.8.4 functional
- “portal_bitcoin_query_transactions” reworded the description of “limit” cosmetic
- “portal_debug_hyperliquid_query_replica_commands” reworded the description of “limit” cosmetic
- “portal_evm_query_logs” reworded the description of “limit” cosmetic
- “portal_evm_query_transactions” reworded the description of “limit” cosmetic
- “portal_get_recent_activity” reworded the description of “limit” cosmetic
- “portal_get_wallet_summary” reworded the description of “limit_per_type” cosmetic
- “portal_hyperliquid_query_fills” reworded the description of “limit” cosmetic
- “portal_solana_query_instructions” reworded the description of “limit” cosmetic
- “portal_solana_query_transactions” reworded the description of “limit” cosmetic
- “portal_substrate_query_calls” reworded the description of “limit” cosmetic
- “portal_substrate_query_events” reworded the description of “limit” cosmetic
- 30 Aug 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 0% → 44% ▲ functional
- The server now declares the “completions” capability functional
- The server now declares the “prompts” capability functional
- First check of Capabilities: pass functional
- New prompt “investigate-contract” functional
- New prompt “investigate-market” functional
- New prompt “investigate-wallet” functional
- New resource “investigation-guide” functional
- New resource “sqd-blockchain-activity-explorer” functional
- Server version: 0.8.2 → 0.8.3 functional
- 28 Aug 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “portal_bitcoin_get_analytics” now declares an output schema ▲ functional
- Tool “portal_bitcoin_query_transactions” now declares an output schema ▲ functional
- Tool “portal_debug_hyperliquid_query_replica_commands” now declares an output schema ▲ functional
- Tool “portal_debug_query_blocks” now declares an output schema ▲ functional
- Tool “portal_debug_resolve_time_to_block” now declares an output schema ▲ functional
- Tool “portal_evm_get_analytics” now declares an output schema ▲ functional
- Tool “portal_evm_get_contract_activity” now declares an output schema ▲ functional
- Tool “portal_evm_get_contract_deployment” now declares an output schema ▲ functional
- Tool “portal_evm_get_ohlc” now declares an output schema ▲ functional
- Tool “portal_evm_query_logs” now declares an output schema ▲ functional
- Tool “portal_evm_query_token_transfers” now declares an output schema ▲ functional
- Tool “portal_evm_query_transactions” now declares an output schema ▲ functional
- Tool “portal_get_head” now declares an output schema ▲ functional
- Tool “portal_get_network_info” now declares an output schema ▲ functional
- Tool “portal_get_recent_activity” now declares an output schema ▲ functional
- Tool “portal_get_time_series” now declares an output schema ▲ functional
- Tool “portal_get_wallet_summary” now declares an output schema ▲ functional
- Tool “portal_hyperliquid_get_analytics” now declares an output schema ▲ functional
- Tool “portal_hyperliquid_get_ohlc” now declares an output schema ▲ functional
- Tool “portal_hyperliquid_query_fills” now declares an output schema ▲ functional
- Tool “portal_list_networks” now declares an output schema ▲ functional
- Tool “portal_resolve_entity” now declares an output schema ▲ functional
- Tool “portal_solana_get_analytics” now declares an output schema ▲ functional
- Tool “portal_solana_query_instructions” now declares an output schema ▲ functional
- Tool “portal_solana_query_transactions” now declares an output schema ▲ functional
- Tool “portal_substrate_get_analytics” now declares an output schema ▲ functional
- Tool “portal_substrate_query_calls” now declares an output schema ▲ functional
- Tool “portal_substrate_query_events” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.8.1 → 0.8.2 functional
- Server version: 0.8.0 → 0.8.1 functional
- Server version: 0.7.9 → 0.8.0 functional
- “portal_list_networks” added an optional parameter “cursor” cosmetic
- “portal_evm_query_logs” added an optional parameter “max_scan_blocks” cosmetic
- “portal_evm_query_logs” reworded the description of “timeframe” cosmetic
- “portal_evm_query_transactions” reworded the description of “timeframe” cosmetic
- Tool “portal_bitcoin_get_analytics” changed its title: Analyze Bitcoin activity cosmetic
- Tool “portal_bitcoin_query_transactions” changed its title: Find Bitcoin transactions cosmetic
- Tool “portal_debug_hyperliquid_query_replica_commands” changed its title: Inspect Hyperliquid command records cosmetic
- Tool “portal_debug_query_blocks” changed its title: Inspect raw blocks cosmetic
- Tool “portal_debug_resolve_time_to_block” changed its title: Match a time to a block cosmetic
- Tool “portal_evm_get_analytics” changed its title: Analyze Ethereum and Base activity cosmetic
- Tool “portal_evm_get_contract_activity” changed its title: Review smart contract activity cosmetic
- Tool “portal_evm_get_contract_deployment” changed its title: Find a contract deployment cosmetic
- Tool “portal_evm_get_ohlc” changed its title: Chart token price history cosmetic
- Tool “portal_evm_query_logs” changed its title: Find smart contract events cosmetic
- Tool “portal_evm_query_token_transfers” changed its title: Find token transfers cosmetic
- Tool “portal_evm_query_transactions” changed its title: Find Ethereum and Base transactions cosmetic
- Tool “portal_get_head” changed its title: Get the latest block cosmetic
- Tool “portal_get_network_info” changed its title: Check network status cosmetic
- Tool “portal_get_recent_activity” changed its title: View recent blockchain activity cosmetic
- Tool “portal_get_time_series” changed its title: Chart blockchain activity cosmetic
- Tool “portal_get_wallet_summary” changed its title: Review wallet activity cosmetic
- Tool “portal_hyperliquid_get_analytics” changed its title: Analyze Hyperliquid trading cosmetic
- Tool “portal_hyperliquid_get_ohlc” changed its title: Chart Hyperliquid prices cosmetic
- Tool “portal_hyperliquid_query_fills” changed its title: Find Hyperliquid trades cosmetic
- Tool “portal_list_networks” changed its title: Find blockchain networks cosmetic
- Tool “portal_resolve_entity” changed its title: Find a token or contract cosmetic
- Tool “portal_solana_get_analytics” changed its title: Analyze Solana activity cosmetic
- Tool “portal_solana_query_instructions” changed its title: Find Solana program activity cosmetic
- Tool “portal_solana_query_transactions” changed its title: Find Solana transactions cosmetic
- Tool “portal_substrate_get_analytics” changed its title: Analyze Polkadot activity cosmetic
- Tool “portal_substrate_query_calls” changed its title: Find Polkadot calls cosmetic
- Tool “portal_substrate_query_events” changed its title: Find Polkadot events cosmetic
- 26 Aug 26 69
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://portal.sqd.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sqd.dev | CN=WE1,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fd9170d4196a777313bdef361ea10f84 |
| SANs: sqd.dev, *.sqd.dev, *.docs.sqd.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of portal.sqd.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| sqd.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://portal.sqd.dev/mcp | Verified | 200 | |
| http (plaintext) | http://portal.sqd.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
portal_get_time_series Chart blockchain activity ~645
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. - You want a simple activity chart for a network, defaulting to a 6h interactive window unless a longer window is explicitly requested. - You want to compare the current period to the previous period. DON'T USE: - You need raw record lists instead of aggregated buckets. - You need DEX pool candles or OHLC output. EXAMPLES: - Base transactions per 15m bucket: {"network":"base-mainnet","metric":"transaction_count","duration":"6h","interval":"15m"} - Compare two periods: {"network":"solana-mainnet","metric":"transaction_count","duration":"1h","interval":"5m","compare_previous":true}
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: Filter to specific contract address for contract-specific trends |
| compare_previous | boolean | – | Compare the selected window against the immediately previous window |
| duration | string | – | 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 Eth… |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "24h ago". |
| group_by | string | – | Optional grouping mode. contract is currently supported only for EVM transaction_count |
| group_limit | number | – | Maximum number of contract groups when group_by=contract |
| interval | string | yes | Time bucket interval (5m, 15m, 1h, 6h, 1d) |
| 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_addres… |
| mode | string | – | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| network | string | yes | Network name (supports short names: 'ethereum', 'polygon', 'base', etc.) |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_get_wallet_summary Review wallet activity ~549
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 pivots before drilling into raw records WHEN TO USE: - You want a single high-level answer about what one wallet has been doing and where value appears to move. - You want inbound/outbound flow, activity and asset-movement counterparties, largest movements within each asset, and exact next pivots before drilling into raw transactions or fills. - The user asks to investigate a suspicious wallet, stolen-funds path, exploit counterparty, or incident address. DON'T USE: - You need every raw record with full chain-specific fields and no summarization. EXAMPLES: - EVM wallet fund-flow triage: {"network":"base-mainnet","address":"0xabc...","timeframe":"24h"} - Solana wallet activity and fee flow: {"network":"solana-mainnet","address":"Vote111...","timeframe":"6h"}
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Wallet address to analyze. Optional when continuing with cursor. |
| cursor | string | – | Continuation cursor from a previous response |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_nfts | boolean | – | Include NFT transfers (ERC721/1155) |
| include_tokens | boolean | – | Include ERC20 token transfers |
| limit_per_type | integer | – | 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 | – | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| network | string | – | Network name or alias. Optional when continuing with cursor. |
| response_format | string | – | Response format: defaults to 'compact' for a readable wallet investigation. Use 'summary' for headline flow only or 'full' for all returned activity rows. |
| timeframe | string | – | Look-back period as timeframe or block count. Examples: '1h', '24h', '7d', '3d', '1000'. |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_hyperliquid_get_analytics Analyze Hyperliquid trading ~385
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 yourself. DON'T USE: - You need individual fill records or OHLC candles. EXAMPLES: - Hyperliquid fill snapshot: {"network":"hyperliquid-fills","timeframe":"1h"} - Who traded the most?: {"network":"hyperliquid-fills","timeframe":"1h"}
| Name | Type | Req | Description |
|---|---|---|---|
| coin | array | – | Filter by asset symbols (e.g., ["BTC", "ETH"]) |
| cursor | string | – | Continuation cursor for ranked analytics sections |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". |
| mode | string | – | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| network | string | – | Network name (default: 'hyperliquid-fills') |
| response_format | string | – | Response format: 'summary' (smallest snapshot), 'compact' (chat-sized ranked sections, default), 'full' (complete analytics). |
| section_limit | number | – | Per-section page size for ranked sections. Default: 6 |
| timeframe | string | – | Time range: '1h', '6h', '24h'. Default: '1h' |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_hyperliquid_get_ohlc Chart Hyperliquid prices ~351
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","interval":"auto"}
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | Asset symbol to build candles for (for example: "BTC", "ETH", "SOL"). Optional when continuing with cursor. |
| cursor | string | – | Continuation cursor from a previous candle page |
| duration | string | – | 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 | – | – | Exact candle-window start. Use together with to_timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input. |
| interval | string | – | Candle interval. Use auto for chart-friendly defaults: 1h→5m, 6h→15m, 12h→30m, 24h→1h. |
| network | string | – | Network name (default: 'hyperliquid-fills') |
| to_timestamp | – | – | Exact inclusive candle-window end. Use together with from_timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input. |
| user | string | – | Optional trader wallet address (0x-prefixed, lowercase) |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_hyperliquid_query_fills Find Hyperliquid trades ~516
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: {"network":"hyperliquid-fills","timeframe":"1h","coin":["BTC"],"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| builder | array | – | Builder addresses (0x-prefixed, lowercase) |
| cloid | array | – | Client order IDs (0x-prefixed hex) |
| coin | array | – | Asset symbols (e.g., "ETH", "BTC", "SOL") |
| cursor | string | – | Continuation cursor from a previous response |
| dir | array | – | Trade direction: "Open Long", "Close Long", "Open Short", "Close Short" |
| fee_token | array | – | Fee token symbols |
| finalized_only | boolean | – | Only query finalized blocks |
| from_block | number | – | Starting block number (use this OR timeframe) |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_builder_info | boolean | – | Include builder and builderFee fields |
| include_pnl | boolean | – | Include closedPnl and startPosition fields |
| limit | integer | – | 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. |
| network | string | – | Network name (default: 'hyperliquid-fills'). Optional when continuing with cursor. |
| response_format | string | – | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for aggregate stats or 'full' when you truly need every fill field. |
| timeframe | string | – | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| to_block | number | – | Ending block number |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| user | array | – | Trader wallet addresses (0x-prefixed, lowercase) |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_list_networks Find blockchain networks ~284
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 type, or real-time availability. DON'T USE: - You already know the exact network and want live data from that network. EXAMPLES: - Find Base-like networks: {"query":"base","limit":10} - Show Solana mainnets: {"vm":"solana","network_type":"mainnet"} - Show Substrate mainnets: {"vm":"substrate","network_type":"mainnet"}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continuation cursor from a previous network catalog page |
| limit | number | – | Max results to return (default: 25, max: 100) |
| network_type | string | – | Filter by network type |
| query | string | – | Search by name, alias, or chain ID |
| real_time_only | boolean | – | Only show networks with a real-time indexed head |
| vm | string | – | Filter by VM family |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_resolve_entity Find a token or contract ~464
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 which token-list addresses a symbol maps to before querying logs or transfers - turning a user-friendly token name into deterministic EVM filters WHEN TO USE: - The user names a token symbol such as USDC, WETH, DAI, or PEPE and you need contract addresses before querying raw data. - The user names a well-known EVM contract, protocol, pool identifier, or Hyperliquid ticker and you need a deterministic follow-up filter. - You need to disambiguate bridged token variants on an EVM network. - You want a source-backed token address rather than relying on memory or hardcoded constants. DON'T USE: - You already have the exact address, pool id, protocol slug, or coin filter and can pass it directly. EXAMPLES: - Resolve USDC on Base: {"network":"base-mainnet","kind":"token","query":"USDC","limit":10} - Resolve WETH on Ethereum: {"network":"ethereum-mainnet","kind":"token","query":"WETH","limit":5} - Resolve BAYC contract: {"network":"ethereum-mainnet","kind":"contract","query":"bored apes"} - Resolve Hyperliquid coin: {"kind":"hyperliquid_coin","query":"bitcoin"}
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Entity kind to resolve: token, contract alias/address, pool identifier, protocol name, or Hyperliquid coin/ticker. |
| limit | number | – | Maximum matches to return. |
| network | string | – | Network name or alias when the entity is network-scoped, e.g. "base", "ethereum", "arbitrum-one", or "hyperliquid-fills". |
| query | string | yes | Entity string to resolve, e.g. "USDC", "bayc", "uniswap", "BTC", or "0x...". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_solana_get_analytics Analyze Solana activity ~427
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 analytics rather than raw records. DON'T USE: - You want chart buckets or raw transaction/instruction records. EXAMPLES: - Solana network snapshot: {"network":"solana-mainnet","timeframe":"1h"} - Include top programs: {"network":"solana-mainnet","timeframe":"1h","include_programs":true}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continuation cursor for paginating top_programs |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_compute_units | boolean | – | Include average compute-unit stats across the full range (disabled by default for speed) |
| include_programs | boolean | – | Include top programs by instruction count (requires an extra instruction scan and is slower) |
| mode | string | – | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| network | string | – | Network name (default: solana-mainnet) |
| program_limit | number | – | Max top-program rows to return per page when include_programs is enabled |
| response_format | string | – | Response format: 'summary' (high-level metrics), 'compact' (core sections), 'full' (complete analytics). |
| timeframe | string | – | Time range. Accepts compact durations like '15m' or natural phrases like 'past 30 minutes'. Optional; defaults to a 1h analysis window. |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_solana_query_instructions Find Solana program activity ~931
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 instructions: {"network":"solana-mainnet","timeframe":"1h","program_id":["TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"],"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| a0 | – | – | Account at index 0. You can pass a single string or an array. |
| a1 | – | – | Account at index 1. You can pass a single string or an array. |
| a10 | – | – | Account at index 10. You can pass a single string or an array. |
| a11 | – | – | Account at index 11. You can pass a single string or an array. |
| a12 | – | – | Account at index 12. You can pass a single string or an array. |
| a13 | – | – | Account at index 13. You can pass a single string or an array. |
| a14 | – | – | Account at index 14. You can pass a single string or an array. |
| a15 | – | – | Account at index 15. You can pass a single string or an array. |
| a2 | – | – | Account at index 2. You can pass a single string or an array. |
| a3 | – | – | Account at index 3. You can pass a single string or an array. |
| a4 | – | – | Account at index 4. You can pass a single string or an array. |
| a5 | – | – | Account at index 5. You can pass a single string or an array. |
| a6 | – | – | Account at index 6. You can pass a single string or an array. |
| a7 | – | – | Account at index 7. You can pass a single string or an array. |
| a8 | – | – | Account at index 8. You can pass a single string or an array. |
| a9 | – | – | Account at index 9. You can pass a single string or an array. |
| cursor | string | – | Continuation cursor from a previous response |
| d1 | – | – | 1-byte discriminator filter (0x-prefixed hex). You can pass a single string or an array. |
| d2 | – | – | 2-byte discriminator filter (0x-prefixed hex). You can pass a single string or an array. |
| d4 | – | – | 4-byte discriminator filter (0x-prefixed hex). You can pass a single string or an array. |
| d8 | – | – | 8-byte discriminator filter - Anchor (0x-prefixed hex). You can pass a single string or an array. |
| finalized_only | boolean | – | Only query finalized slots |
| from_block | number | – | Starting slot number (use this OR timeframe) |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_inner_instructions | boolean | – | Include inner (CPI) instructions |
| include_logs | boolean | – | Include program logs |
| include_transaction | boolean | – | Include transaction data |
| include_transaction_balances | boolean | – | Include SOL balance changes |
| include_transaction_instructions | boolean | – | Include all instructions from the parent transaction (sibling instructions) |
| include_transaction_token_balances | boolean | – | Include token balance changes |
| is_committed | boolean | – | Only committed transactions |
| limit | integer | – | Max instructions (default: 20, max: 25) |
| mentions_account | – | – | Accounts mentioned anywhere in the instruction. You can pass a single string or an array. |
| network | string | – | Network name or alias. Optional when continuing with cursor. |
| program_id | – | – | Program IDs. You can pass a single string or an array. |
| timeframe | string | – | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. Solana slots are ~400ms. |
| to_block | number | – | Ending slot number. Keep ranges reasonable for performance. |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| transaction_fee_payer | – | – | Fee payer filter. You can pass a single string or an array. |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_solana_query_transactions Find Solana transactions ~490
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: - Recent Solana transactions: {"network":"solana-mainnet","timeframe":"1h","limit":20} - Filter by program: {"network":"solana-mainnet","timeframe":"1h","program_id":["TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA"],"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continuation cursor from a previous response |
| fee_payer | array | – | Fee payer addresses |
| finalized_only | boolean | – | Only query finalized slots |
| from_block | number | – | Starting slot number (use this OR timeframe) |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_balances | boolean | – | Include SOL balance changes |
| include_instructions | boolean | – | Include instruction data |
| include_logs | boolean | – | Include program logs |
| include_rewards | boolean | – | Include block rewards (validator staking rewards). Filter by pubkey using mentions_account. |
| include_token_balances | boolean | – | Include SPL token balance changes |
| limit | integer | – | Max transactions to return (default: 20, max: 25) |
| mentions_account | array | – | Accounts mentioned anywhere in the transaction |
| network | string | – | Network name or alias. Optional when continuing with cursor. |
| response_format | string | – | 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. |
| timeframe | string | – | Time range (e.g., '1h', '24h'). Alternative to from_block/to_block. |
| to_block | number | – | Ending slot number |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_substrate_get_analytics Analyze Polkadot activity ~492
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 Polkadot or another Substrate network in an indexed window WHEN TO USE: - You want Polkadot activity analytics in a selected indexed window. - You want to ask "how is Polkadot doing in this indexed window?" and get an analytics answer rather than just network freshness metadata. - You want a quick Substrate network snapshot or health check. - You want top pallet events and calls rather than raw rows. - You want to know how a Substrate network is doing in the selected indexed window. DON'T USE: - You need full raw event or call records. EXAMPLES: - Polkadot activity snapshot: {"network":"polkadot","timeframe":"1h"} - Big picture for Polkadot activity: {"network":"polkadot","timeframe":"1h"} - How is Polkadot doing?: {"network":"polkadot","timeframe":"6h"}
| Name | Type | Req | Description |
|---|---|---|---|
| from_block | number | – | Starting block number (use this OR timeframe) |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". |
| mode | string | – | Execution depth. Defaults to complete requested-window analysis; the optional fast value is only for explicitly bounded previews. |
| network | string | – | Substrate network name (default: polkadot) |
| response_format | string | – | Response format: 'summary' (headline metrics only), 'compact' (core sections), 'full' (full dashboard payload) |
| section_limit | number | – | Max rows to keep in ranked event and call sections |
| timeframe | string | – | Time range like '1h', '6h', or '24h'. Default: '1h' |
| to_block | number | – | Ending block number |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_substrate_query_calls Find Polkadot calls ~525
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 want pallet call activity like Balances.transfer_keep_alive or Ethereum.transact. - You want calls plus the events emitted by those calls. DON'T USE: - You want events or aggregate analytics rather than call rows. EXAMPLES: - Recent Balances calls: {"network":"polkadot","timeframe":"1h","call_names":["Balances.transfer_keep_alive"],"limit":20} - Polkadot calls with emitted events: {"network":"polkadot","timeframe":"1h","call_names":["ParaInherent.enter"],"include_events":true,"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| call_names | array | – | Optional qualified call names like Timestamp.set or Balances.transfer_keep_alive |
| cursor | string | – | Continuation cursor from a previous response |
| finalized_only | boolean | – | Only query finalized blocks |
| from_block | number | – | Starting block number |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". |
| include_events | boolean | – | Attach events emitted directly by each matching call |
| include_extrinsic | boolean | – | Attach the parent extrinsic inline for each matching call |
| include_stack | boolean | – | Attach the parent call stack for each matching call |
| include_subcalls | boolean | – | Attach direct descendant calls inline for each matching call |
| limit | integer | – | Max calls to return (max: 10; use compact mode for context-rich rows) |
| network | string | – | Substrate network name or alias. Optional when continuing with cursor. |
| response_format | string | – | Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested subcalls, events, and extrinsic context in a smaller inline shape. |
| timeframe | string | – | Time range (e.g. '1h', '24h'). Alternative to from_block/to_block. |
| to_block | number | – | Ending block number |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_substrate_query_events Find Polkadot events ~467
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 Balances.Transfer or Contracts.ContractEmitted. - You want event rows first, even if the network is a Polkadot-family chain. DON'T USE: - You want calls or aggregate analytics rather than event rows. EXAMPLES: - Balances.Transfer events on Polkadot: {"network":"polkadot","timeframe":"1h","event_names":["Balances.Transfer"],"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Continuation cursor from a previous response |
| event_names | array | – | Optional qualified event names like Balances.Transfer or System.ExtrinsicSuccess |
| finalized_only | boolean | – | Only query finalized blocks |
| from_block | number | – | Starting block number |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "6h ago". |
| include_call | boolean | – | Attach the emitting call inline when the event has call context |
| include_extrinsic | boolean | – | Attach the parent extrinsic inline for each matching event |
| include_stack | boolean | – | Attach the parent call stack when the event has nested call context |
| limit | integer | – | Max events to return (max: 10; use compact mode for context-rich rows) |
| network | string | – | Substrate network name or alias. Optional when continuing with cursor. |
| response_format | string | – | Response format: defaults to 'compact' for chat-friendly output. Compact mode keeps requested extrinsic or call context in a smaller inline shape. |
| timeframe | string | – | Time range (e.g. '1h', '24h'). Alternative to from_block/to_block. |
| to_block | number | – | Ending block number |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_tron_query_logs Find Tron contract events ~801
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 USE: - You need TRC-20 Transfer or Approval events for a token such as USDT on Tron. - You need event logs from a Tron contract filtered by topic signature or indexed address. - You want the exact transaction hash behind each Tron event. DON'T USE: - You want native TRX transfers or contract calls; use portal_tron_query_transactions. - You need an Ethereum-compatible network; use portal_evm_query_logs. EXAMPLES: - Recent USDT transfers on Tron: {"network":"tron-mainnet","timeframe":"5m","addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"event":"transfer","decode":true,"limit":20} - USDT transfers received by one wallet: {"network":"tron-mainnet","from_block":84000000,"to_block":84000100,"addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"event":"transfer","topic2":["TJLuVi6UhS3UTx5EUXNCoz9VNqP2gnPmyf"],"decode":true,"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | – | 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. |
| cursor | string | – | Continuation cursor from a previous response |
| decode | boolean | – | Decode known event signatures inline with Base58 addresses |
| event | – | – | FILTER: common event alias (transfer, approval, swap, mint, burn) or a topic0 hash. Merges with topic0. |
| finalized_only | boolean | – | Only query finalized blocks |
| from_block | number | – | Starting block number |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_transaction | boolean | – | Attach the parent transaction (type, caller, contract, result, fee). The hash is always attached. |
| limit | integer | – | Max logs to return (default: 20, max: 25) |
| max_scan_blocks | integer | – | Safety cap for filtered latest-first scans. Default: min(window, 50000). |
| network | string | – | Network name (default: tron-mainnet). Optional when continuing with cursor. |
| response_format | string | – | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for counts by contract and event. |
| timeframe | string | – | Time range (e.g., '5m', '1h'). Alternative to from_block/to_block. |
| to_block | number | – | Ending block number. Tron produces a block every 3 seconds. |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| topic0 | array | – | FILTER: event signature hashes, with or without 0x. |
| topic1 | array | – | FILTER: indexed parameter 1 (often the sender). An address in any form is padded to a topic. |
| topic2 | array | – | FILTER: indexed parameter 2 (often the recipient). An address in any form is padded to a topic. |
| topic3 | array | – | FILTER: indexed parameter 3. |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
portal_tron_query_transactions Find Tron transactions ~939
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 calls on Tron - who sent TRX to an address on Tron, or which wallets called a Tron contract WHEN TO USE: - You need raw Tron transaction records with sender, recipient, amount in TRX, fee, energy, and success. - You want native TRX transfers to or from a wallet in a bounded window. - You want calls to a Tron contract such as USDT filtered by method (transfer, approve) or caller. - You want TRC-10 asset transfers by asset id. DON'T USE: - You need TRC-20 token events; those are logs, so use portal_tron_query_logs. - You need an Ethereum-compatible network; use portal_evm_query_transactions. EXAMPLES: - Recent native TRX transfers: {"network":"tron-mainnet","timeframe":"5m","kind":"transfer","limit":20} - USDT transfer calls in a block window: {"network":"tron-mainnet","from_block":84000000,"to_block":84000010,"contract_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"method":"transfer","limit":20} - TRX sent from one wallet: {"network":"tron-mainnet","timeframe":"1h","kind":"transfer","from_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"limit":20}
| Name | Type | Req | Description |
|---|---|---|---|
| asset | array | – | FILTER (transfer_asset): TRC-10 asset id such as 1005157, or the raw hex asset name. |
| contract_addresses | array | – | FILTER (trigger_smart_contract): called contract addresses in any accepted form, e.g. USDT. |
| cursor | string | – | Continuation cursor from a previous response |
| finalized_only | boolean | – | Only query finalized blocks |
| from_addresses | array | – | FILTER: sender or caller addresses. Accepts Base58 (T...), 41-prefixed hex, or 0x/bare 20-byte hex. |
| from_block | number | – | Starting block number |
| from_timestamp | – | – | Starting timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "1h ago". |
| include_internal_transactions | boolean | – | Attach the internal transactions of each transaction |
| include_logs | boolean | – | Attach the event logs each transaction emitted |
| kind | string | – | 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 fil… |
| limit | integer | – | Max transactions to return (default: 20, max: 25) |
| max_scan_blocks | integer | – | Safety cap for filtered latest-first scans. Default: min(window, 50000). |
| method | – | – | FILTER (trigger_smart_contract): method alias such as transfer, approve, transferFrom, or a 4-byte sighash. |
| network | string | – | Network name (default: tron-mainnet). Optional when continuing with cursor. |
| response_format | string | – | Response format: defaults to 'compact' for chat-friendly output. Use 'summary' for counts by type, TRX moved, and top callers. |
| sighash | array | – | FILTER (trigger_smart_contract): 4-byte method selectors, with or without 0x. Merges with method. |
| timeframe | string | – | Time range (e.g., '5m', '1h'). Alternative to from_block/to_block. |
| to_addresses | array | – | FILTER (transfer, transfer_asset): recipient addresses in any accepted form. |
| to_block | number | – | Ending block number. Tron produces a block every 3 seconds. |
| to_timestamp | – | – | Ending timestamp. Accepts Unix seconds, Unix milliseconds, ISO datetime, or relative input like "now". |
| types | array | – | FILTER (kind=all): Tron contract types such as TransferContract, TriggerSmartContract, DelegateResourceContract. |
| Name | Type | Req | Description |
|---|---|---|---|
| _app | – | – | SQD Explorer identity and host-render state. |
| _coverage | – | – | Window and result completeness. |
| _evidence | – | – | Replayable arguments, digest, row count, and receipt. |
| _execution | – | – | Bounded execution and scan details. |
| _freshness | – | – | Freshness and finality. |
| _llm | – | – | Hints to locate the primary evidence. |
| _meta | – | – | Network, block range, timing, and row counts. |
| _notice | string | – | Limitation or truncation notice. |
| _notices | array | – | Limitation or truncation notices. |
| _ordering | – | – | Ordering guarantees. |
| _pagination | – | – | Pagination state and next_cursor. |
| _server | object | – | SQD server name, exact version, and git commit. |
| _summary | string | – | Human-readable summary. |
| _tool_contract | – | – | Tool identity, intent, and chain families. |
| _ui | – | – | Chart, table, and follow-up presentation metadata. |
| answer | string | – | Answer grounded in the returned data. |
| display | – | – | Labels for presenting the result. |
| error | object | – | Structured failure details. |
| investigation | – | – | Evidence paths, pivots, and limitations. |
| items | array | – | Primary rows for list results. |
| next_steps | – | – | Safe follow-up actions and continuation guidance. |
| pipes_handoff | – | – | SQD Pipes guidance for custom data needs. |
| value | – | – | Primary scalar result. |
No examples provided.
What is the SQD MCP server?
SQD is an MCP server listed in the public MCP registry as io.github.subsquid-labs/portal-mcp-server. Query 130+ SQD Portal datasets across blockchains, including native Tron transactions and events. This page covers its hosted endpoint (https://portal.sqd.dev/mcp).
Is the SQD MCP server safe to use?
SQD scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SQD MCP server expose?
SQD exposes 31 tools: portal_list_networks, portal_get_network_info, portal_get_head, portal_resolve_entity, portal_get_recent_activity, and 26 more. Their descriptions and schemas cost roughly 17,229 tokens of context every time the server is loaded.
Does the SQD MCP server require authentication?
No. We connected to SQD without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SQD MCP server still maintained?
SQD is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.