Skip to main content
The server exposes ~83 tools over the Voyager API. Every tool takes an optional network (mainnet default, or sepolia); addresses and hashes are 0x-prefixed felts. See the Quickstart to connect a client first — the package is on npm as voyager-mcp.
Building an agent? This page doubles as the agent guide. The MCP server also ships these usage hints in its instructions, so most clients surface them on connect — your agent gets the tool list plus the call-chaining playbook (the Recipes section below) without extra prompting.

​
Tool groups

The optional groups are controlled by the VOYAGER_TOOLS env var — see Selecting tools below.

​
Core

Transactions — list_transactions, get_transaction, get_transaction_trace (call tree), get_transaction_messages (L1↔L2), get_transaction_storage_diffs (state changes), list_meta_transactions. Blocks — list_blocks, get_block (by number, 0x hash, or pre_confirmed). Contracts & accounts — list_contracts, get_contract, get_contract_code, get_contract_functions (ABI), get_contract_token_balances, get_contract_portfolio, get_contract_holders, get_contract_transfers, get_contract_transfer_tokens, get_contract_class_history, get_contract_bridge_transactions, get_contract_erc20_balance_history, get_contract_erc20_tokens_held, list_protocols, get_top_contracts_stats. Classes & Cairo code — list_classes, get_class, get_class_code (verified Cairo — key for codegen), get_class_functions, get_class_decompiled, get_class_contracts. Tokens — list_tokens, list_tokens_v2, get_token_holders, get_token_transfers, get_token_security (risk scan), get_token_functions. Events & messages — list_events, get_event, list_messages, get_message, get_message_bridge_transactions. Network, stats & L1 — get_stats, get_daily_stats, get_today_stats, get_network_status, get_indexer_lagging, get_cairo_v1_contracts_count, get_api_status, get_account_call, get_l1_transaction, get_l1_bridge_transactions, get_l1_state_updates.

​
NFT

list_nfts, get_nft_contract, get_nft, list_nft_items, list_nft_balances, list_nft_holders, get_nft_contract_balance, list_nft_events, list_nft_transfers, get_nft_stats, get_marketplace_stats.

​
Staking

get_staking_overview, list_validators, get_validator_details, get_validator_pool_info, get_validator_activity, list_delegators, get_delegators_over_time, get_stake_over_time, list_attestations. search (everything), plus typed variants: search_contracts, search_transactions, search_classes, search_tokens, search_messages, search_blocks, search_validators, search_domains, search_protocols, search_nft_contracts.

​
Selecting tools

Trim the tool set with the VOYAGER_TOOLS env var (in your MCP client config):

​
Recipes — chain calls for the full picture

A single call rarely tells the whole story. Common chains the agent follows:
  1. get_transaction — status, type, fee, block, calldata.
  2. get_transaction_trace — the nested call tree (what it actually invoked).
  3. get_transaction_messages — L1↔L2 messages it sent/consumed.
  4. get_transaction_storage_diffs — exact state changes (great for debugging effects/reverts).
  5. list_events with contract=<addr> — emitted events.
  1. get_contract — class hash, type (account/erc20/…), proxy info, aliases.
  2. get_class_code (verified Cairo) or get_contract_functions (ABI) — to read/call it.
  3. get_contract_token_balances / get_contract_portfolio — what it holds.
  4. get_contract_class_history — upgrade history if it’s a proxy.
  1. get_token_holders — distribution.
  2. get_token_transfers — activity (needs a time window, see below).
  3. get_token_security — risk scan before trusting a token.
  4. get_token_functions — ABI.
get_contract_portfolio (holdings) + get_contract_token_balances + get_contract_transfers (movements) + list_transactions with to=<addr>.
get_staking_overview → list_validators → get_validator_details / list_delegators.
Start with search (or a typed variant like search_contracts / search_tokens / search_domains) to resolve an address, hash, or name.

​
Performance & limits

High-volume endpoints can time out. get_token_transfers and busy NFT collections (list_nft_holders, list_nft_events) scan a lot — pass a narrow time window (timestampFrom/timestampTo) or a small pageSize. Without a window the request can hit the timeout and return an error suggesting you narrow the query.
  • Pagination: list tools take page + pageSize (10/25/50/100); some token/NFT-transfer tools use a cursor. Keep page sizes small to save the agent’s context.
  • Rate limiting is enforced upstream. The client auto-retries 429/5xx with backoff, so transient limits are handled — just avoid firing huge bursts.