avalanche-mcp-server
Avalanche MCP is a read-only Model Context Protocol server that gives AI agents the full Avalanche stack — documentation search, protocol knowledge, L1/ICM workflows, and live on-chain data.
Documentation & knowledge: full-text search over Avalanche docs, Academy, integrations, blog, ACPs, AvalancheGo/Subnet-EVM, ICM, and CLI sources; read/list doc pages; curated guides for architecture, L1 launches, precompiles, ICM, troubleshooting, and gas/fees.
Protocol & upgrades: list and look up all 36 ACPs with status/track/authors, check live ACP signaling from nodes, and view the Banff → Helicon upgrade timeline with versions and developer impact.
L1 & ICM workflows: generate valid Subnet-EVM genesis.json files, get step-by-step L1 launch plans, Teleporter/ICM sender-receiver recipes, error troubleshooting, and Builder Console deep links.
Live EVM chain access: query balances, blocks, transactions, receipts, contract code, read-only
eth_call, and gas estimates on C-Chain, Fuji, known L1s, or any RPC URL.P-Chain / X-Chain / node data: list validators and subnets, get staking economics and supply, check transaction status, P/X-Chain balances, and node/network info.
Avalanche Data API: discover indexed chains, list ERC-20 balances, transaction history, token/contract metadata, and sovereign L1 validators.
Hosted federation: proxy tools from Ava Labs' official hosted Avalanche MCP for current docs search, CLI/RPC lookup, and build plan runbooks.
Safety: every tool is read-only — nothing signs or broadcasts transactions, with SSRF protection and input validation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@avalanche-mcp-server how do I launch an L1 on Avalanche?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Install
Hosted — nothing to install. Same shape as Ava Labs' build.avax.network/api/mcp: a public Streamable HTTP endpoint, no API key.
claude mcp add avalanche --transport http https://avalanche-mcp.dev/mcpClient | Configuration |
Claude Code | Command above, or commit |
Cursor / Windsurf |
|
Claude Desktop |
|
Local / offline |
|
Any HTTP client |
|
Run /mcp in Claude Code to verify — you should see avalanche · 41 tools.
Related MCP server: Avalanche MCP Tools
What it does
Ask in plain language; the agent picks the tools and cites its sources.
› What changes in the Helicon upgrade for my C-Chain indexer?
⏺ avax_upgrade_lookup(query: "Helicon")
⏺ avax_acp_lookup(query: "ACP-194")
⏺ avax_get_doc(content/docs/primary-network/helicon-upgrade.mdx)
Helicon (AvalancheGo v1.15.0-fuji) is live on Fuji since 2026-07-28; mainnet is not
scheduled yet. ACP-194 Continuous Execution decouples consensus from execution, so a
block's state root settles after a τ delay (~5 s) — don't treat "latest" as executed
state. ACP-283 makes the minimum gas price dynamic, so never hardcode a fee floor.
Sources: build.avax.network/docs/primary-network/helicon-upgrade
build.avax.network/docs/acps/194-continuous-executionOther things to ask on day one:
"Plan a permissioned enterprise L1 on Fuji with five validators, then generate the genesis."
"Explain the NativeMinter precompile and how to enable it after launch with upgrade.json."
"Send a message from Fuji C-Chain to Dispatch with Teleporter, with relayer setup."
"Which ACPs are activated, and what does ACP-176 change about gas?"
"My CLI says
subnet not trackedwhen I hit the RPC. What's wrong?""Chart C-Chain active addresses for the last 90 days, and which L1s have the most bot traffic?"
Capabilities
45 tools, every one read-only. Nothing signs or broadcasts transactions.
Area | Tools | What you get |
Knowledge | 7 | Full-text search over a bundled index of build.avax.network (docs, Academy, 234 integrations, blog), Subnet-EVM precompile docs, ICM contracts, Avalanche CLI reference — 9.9k chunks, every hit with its source URL. Curated guides for architecture, L1 launch, precompiles, ICM, gas and troubleshooting. |
Protocol & upgrades | 4 | All 36 ACPs with structured status / track / authors; the Banff → Helicon upgrade timeline with dates, versions and developer impact; live ACP signaling from nodes. |
Workflows | 6 | Tailored L1 launch plans, valid |
Live EVM | 8 | C-Chain, Fuji, known L1s or any RPC URL: balances, blocks, receipts, |
P-Chain · X-Chain · node | 8 | Validators, subnets and L1s, staking economics, tx status, UTXO balances, node and network info. |
Avalanche Data API | 5 | Indexed chains, ERC-20 balances, transaction history, token metadata, L1 validators. |
Network stats | 4 | C-Chain metric time series (transactions, active addresses/senders, fees, gas, TPS, cumulative addresses/contracts/deployers), Primary Network staking history since 2020, a 30-day ranking of every Avalanche L1 with market share, concentration and estimated bot-traffic share, and an SVG chart + table renderer so stats show up as UI. Backed by SOCI4L's public API (a daily snapshot of the Ava Labs Metrics API, P-Chain cross-checked). |
Hosted federation | 3 | Proxy to Ava Labs' official MCP for |
Plus MCP resources (avax://docs/{path}, avax://guides/{name}, avax://networks) and prompts (avalanche_launch_l1, avalanche_deploy_contract, avalanche_icm_bridge, avalanche_learn). The full tool list is at avalanche-mcp.dev/#tools or via tools/list.
Verified, not guessed
Facts that models commonly get wrong are pinned in code and checked against the docs: the C-Chain minimum base fee is 1 wei since Fortuna (ACP-176), not 25 nAVAX; subnet-evm and icm-contracts now live in avalanchego/graft and icm-services; Helicon is Fuji-only as of August 2026. Every answer carries the build.avax.network or GitHub URL it came from.
Knowledge sources
The index is built by npm run build-index from official repositories and ships inside the package, so the first search works offline:
Source | Content |
| docs, Academy (L1 and blockchain tracks), integrations, blog |
| every ACP README, parsed into structured metadata |
| README, |
| Teleporter / ICTT contracts, relayer, signature aggregator |
| command reference, templates |
soci4l.net/api/avalanche (live) | C-Chain metrics, L1 rankings, staking series — |
avax_list_topics reports the index build date so the agent knows how fresh it is; avax_fetch_live_doc fetches the current version of any page when that matters. Credential-shaped strings in documentation examples are redacted at build time.
Configuration
No configuration is required. Optional environment variables (local mode):
Variable | Purpose |
| Higher rate limits for the Avalanche Data API tools. Free key at build.avax.network. ( |
| Override the Data API base URL |
| Override the hosted Avalanche MCP endpoint used by |
|
|
| Comma-separated extra RPC hostnames to allow when custom RPCs are disabled |
| Max |
Self-hosting
Run the HTTP transport anywhere Node runs:
npx -y avalanche-mcp-server --http # POST http://localhost:3333/mcp (PORT to change)Or mount it in any web-standard runtime — Next.js route handlers, Cloudflare Workers, Hono:
import { handleMcpRequest } from "avalanche-mcp-server";
export const POST = (req: Request) => handleMcpRequest(req);This is exactly how avalanche-mcp.dev serves it (source). Responses are stateless JSON with CORS open, so browser-based clients work too.
Works with the official Avalanche MCPs
Ava Labs' hosted MCP is always current for Builder Hub search, CLI / RPC lookup and runbooks; this server adds offline knowledge, structured ACPs and upgrades, live EVM tools and end-to-end workflows. They compose:
claude mcp add avalanche --transport http https://avalanche-mcp.dev/mcp
claude mcp add avalanche-hosted --transport http https://build.avax.network/api/mcp
claude mcp add avalanche-chainkit -- npx -y @avalanche-sdk/chainkit mcp-server
claude mcp add avalanche-avacloud -- npx -y @avalabs/avacloud-sdk mcp-server --apikey $AVACLOUD_API_KEYavax_hosted_call already proxies the hosted server from inside this one, so a single registration covers most setups.
Development
git clone https://github.com/Eelvanpsd/Avalanche-mcp.git && cd Avalanche-mcp
npm install && npm run build # the index ships in the repo
npm run dev # stdio server via tsx
npm run inspect # MCP Inspector UI
npx tsx scripts/smoke.ts # end-to-end tool check over stdio
REFRESH=1 npm run build-index # re-download sources and rebuild the indexExtending it is one file each: curated guides in src/knowledge/guides.ts, the network registry in src/config/networks.ts, upgrade timeline in src/knowledge/upgrades.ts, new sources in scripts/build-index.ts.
Security
Every tool is read-only — the server never holds a private key, signs, or broadcasts. Additional hardening for public deployments:
SSRF protection — the
networkargument may be a raw RPC URL, which the server fetches. Loopback, private, link-local and cloud-metadata targets are always refused; setAVAX_ALLOW_CUSTOM_RPC=falseto allow only built-in chains (recommended when exposing the HTTP endpoint publicly).Rate limiting — the server throttles its own calls to Ava Labs' hosted MCP to stay under the shared 60/min budget. The HTTP endpoint itself is unauthenticated, so put a per-IP rate limiter in front (the reference deployment ships one; Upstash Ratelimit is a good managed option).
Input validation — addresses and identifiers are validated with zod/viem before any upstream request.
Report vulnerabilities via a private GitHub security advisory on the repo.
License
MIT. Avalanche MCP is an independent, community-built project and is not affiliated with or endorsed by Ava Labs or the Avalanche Foundation. Avalanche and the Avalanche mark are trademarks of their respective owners.
Available Tools
41 toolsavax_acp_listList Avalanche Community ProposalsARead-onlyIdempotent
List all ACPs (Avalanche Community Proposals) with structured fields: number, title, status (Activated | Implementable | Proposed | Stale), track (Standards | Best Practices | Meta | Subnet), authors, replaces/dependencies. Offline — parsed from avalanche-foundation/ACPs. Use to answer 'which upgrades are live?', 'what changed in Etna/Fortuna?'.
Inputs: track, status.
avax_acp_lookupLook up an ACPARead-onlyIdempotent
Get one ACP by number or title keyword: preamble fields (status, track, authors, replaces, dependencies, discussion link), abstract, and the full text (truncated). Offline.
Inputs: query (required), full_text.
avax_acp_votesLive ACP signaling (info.acps)ARead-onlyIdempotent
Query a public node's info.acps for ACPs currently being signaled (supported/objected weight) on mainnet or fuji. Empty when no ACP vote is in progress.
Inputs: network.
avax_call_contractRead contract (eth_call)BRead-onlyIdempotent
Call a read-only (view/pure) contract function. Provide the function as a human-readable ABI signature, e.g. 'function balanceOf(address) view returns (uint256)', plus args.
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL.
Inputs: address (required), signature (required), args, network.
avax_console_flowsBuilder Console flows & deep linksARead-onlyIdempotent
List Builder Console (build.avax.network/console) no-code flows with deep links: create-l1, convert-to-l1, validator-manager, ictt, faucet, multisig, unit-converter, icm-relayer. Also returns platform-cli equivalents for scriptable automation. Pass flow for one entry.
Inputs: flow.
avax_data_get_token_metadataGet contract / token metadataARead-onlyIdempotent
Get metadata for a contract address (ERC-20/721/1155 type, name, symbol, decimals, deployment tx) via Avalanche Data API.
Inputs: address (required), chain_id.
avax_data_list_chainsList chains indexed by Avalanche Data APIARead-onlyIdempotent
List every chain (C-Chain + L1s) indexed by the Avalanche Data API (Glacier), with chain ID, name, RPC, explorer, native token and whether it's testnet. Best way to discover L1s beyond the built-in registry.
Inputs: network.
avax_data_list_erc20_balancesList ERC-20 balancesARead-onlyIdempotent
List all ERC-20 token balances held by an address on a chain (Avalanche Data API). Returns token address, symbol, decimals, and balance.
Inputs: address (required), chain_id, page_size.
avax_data_list_l1_validatorsList L1 validators (Data API)ARead-onlyIdempotent
List sovereign L1 validators (post-Etna ACP-77) from the Data API, optionally filtered by subnet ID or node ID. Shows weight, balance, and remaining balance owner.
Inputs: network, node_id, page_size, subnet_id.
avax_data_list_transactionsList address transactionsARead-onlyIdempotent
List recent transactions of an address on a chain (native + contract interactions) via Avalanche Data API. Paginated.
Inputs: address (required), chain_id, page_size, page_token.
avax_estimate_gasEstimate gasARead-onlyIdempotent
Estimate gas for a transaction (to, data, value, from). Also returns current base fee so the agent can compute a fee budget.
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL.
Inputs: to, data, from, network, +1 more.
avax_explain_precompileExplain a Subnet-EVM precompileARead-onlyIdempotent
Reference card for one Subnet-EVM precompile: address, genesis config key, purpose, example genesis snippet, Solidity interface notes, plus the most relevant doc hits.
Inputs: name (required).
avax_fetch_live_docFetch a live build.avax.network page as markdownARead-onlyIdempotent
Fetch the CURRENT version of any build.avax.network page (docs, academy, integrations, blog, acps) as clean markdown via the official .md endpoint. Use when the local index may be stale (check builtAt in avax_list_topics) or for pages not indexed. Accepts a full URL or a site path like /docs/primary-network/overview.
Inputs: url (required), offset.
avax_generate_genesisGenerate Subnet-EVM genesis.jsonARead-onlyIdempotent
Generate a valid Subnet-EVM genesis.json for a new Avalanche L1. Choose a fee preset (low|medium|high|gasless) or override feeConfig, allocate initial balances, and enable precompiles (deployer allow-list, tx allow-list, native minter, fee manager, reward manager, warp). Warp is enabled by default because ICM/Teleporter needs it. Returns the JSON plus next-step CLI commands.
Inputs: chain_id (required), fee_preset, allocations, enable_warp, +10 more.
avax_get_balanceGet native balanceARead-onlyIdempotent
Get the native token balance (AVAX on C-Chain/Fuji, or the L1's native token) of an address on an Avalanche EVM chain.
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL. Returns wei and a formatted value.
Inputs: address (required), network. Returns: wei, symbol, address, chainId, +2 more
avax_get_blockGet blockARead-onlyIdempotent
Fetch a block by number, hash, or tag ('latest'). Returns header fields and transaction hashes (set include_transactions=true for full tx objects).
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL.
Inputs: block, network, include_transactions.
avax_get_chain_statusGet chain statusARead-onlyIdempotent
Get live status of an Avalanche EVM chain: reported chainId, latest block number, base fee, gas price. Useful to verify an RPC works and to pick gas settings.
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL.
Inputs: network.
avax_get_codeGet contract code / check if contractARead-onlyIdempotent
Return whether an address is a contract and its bytecode size (and bytecode prefix). Use to verify deployments.
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL.
Inputs: address (required), network.
avax_get_docRead a full documentation pageARead-onlyIdempotent
Return the full text of a documentation page by its path (from avax_search_docs / avax_list_docs) or its build.avax.network URL. Long pages are truncated at 25k chars; use offset to continue.
Inputs: path (required), offset.
avax_get_guideGet curated Avalanche guideARead-onlyIdempotent
Return a curated, condensed guide bundled with this server. Available: architecture (Primary Network (P/X/C), L1s, VMs, consensus – the mental model every builder needs.); launch-l1 (From avalanche blockchain create to a sovereign L1 on Fuji/mainnet, with validators and ICM.); precompiles (Addresses, genesis keys and when to use each of the 6 built-in precompiles.); icm (Send a message or tokens between C-Chain and an L1 (or L1↔L1) with Teleporter, with addresses and a Solidity recipe.); troubleshooting (Fast lookup of frequent failures on C-Chain, L1s, CLI, ICM and RPC.); gas-and-fees (How fees work on C-Chain vs L1s and how to pick feeConfig values in genesis.). Prefer this for orientation, then avax_search_docs for details.
Inputs: name (required).
avax_get_transactionGet transactionARead-onlyIdempotent
Fetch a transaction and its receipt by hash (status, gas used, logs, contract address created).
Network: "mainnet" (C-Chain), "fuji" (testnet C-Chain), a known L1 key (mainnet, c-chain, fuji, dexalot, beam, dfk, dispatch-fuji, echo-fuji), or a full RPC URL.
Inputs: hash (required), network.
avax_hosted_callCall a tool on the official hosted Avalanche MCPARead-onlyIdempotent
Proxy a tool call to Ava Labs' hosted Avalanche MCP (https://build.avax.network/api/mcp). Best for things the local index lacks: build_plan (platform-cli runbooks; pass chainId as a STRING), cli_lookup_command, rpc_lookup_method, docs_search (always-current), platform_get_validators_at, platform_get_pending_validators, info_peers, onchain_activity. On 429 fall back to local tools.
Inputs: name (required), arguments.
avax_hosted_list_toolsList tools of the official hosted Avalanche MCPARead-onlyIdempotent
List the ~48 tools exposed by Ava Labs' hosted MCP (https://build.avax.network/api/mcp): docs_search (incl. blog/integrations), cli_lookup_command (avalanche-cli/platform-cli/tmpnet), rpc_lookup_method, acp_lookup, platform_get_* (incl. get_validators_at, get_utxos, get_pending_validators), info_* (info_peers, info_is_bootstrapped), onchain_*/chain_stats, build_plan (runbooks), console_flow/console_link. (GitHub code-search tools are documented but not currently exposed.) Then call avax_hosted_call. Rate limit 60/min — prefer local tools when equivalent.
Inputs: no named parameters.
avax_hosted_read_indexRead a hosted Avalanche MCP index resourceARead-onlyIdempotent
Read one of the hosted MCP's index resources: docs://index, academy://index, integrations://index, blog://index, rpcs://index, cli://index, acps://index — markdown link lists of every page, always current.
Inputs: uri (required).
avax_icm_recipeICM/Teleporter integration recipeBRead-onlyIdempotent
Return the addresses, blockchain-ID lookup steps, Solidity sender/receiver skeleton and relayer commands for sending ICM messages between two Avalanche chains.
Inputs: source, destination, payload_kind.
avax_list_docsList documentation pagesARead-onlyIdempotent
List documentation pages under a path prefix (e.g. 'content/docs/avalanche-l1s', 'content/docs/rpcs', 'content/academy/avalanche-l1', 'graft/subnet-evm'). Use to browse a section's table of contents.
Inputs: limit, path_prefix.
avax_list_networksList Avalanche networksARead-onlyIdempotent
List all networks this server knows: Avalanche Mainnet C-Chain, Fuji testnet, and well-known L1s, with chain IDs, RPC URLs, explorers and faucets. Call this first when unsure which network value to use.
Inputs: no named parameters.
avax_list_topicsList knowledge-base topicsARead-onlyIdempotent
Overview of the indexed Avalanche knowledge base: top-level sections with document counts, plus index build date. Use to orient before searching.
Inputs: no named parameters.
avax_node_infoGet node / network infoARead-onlyIdempotent
Query the public API node's info.* endpoints: node version, network ID/name, blockchain IDs for X/C/P, and tx fees (info.getTxFee). Useful to confirm which network you're on and current P-Chain fees.
Inputs: network.
avax_pchain_get_balanceGet P-Chain balanceARead-onlyIdempotent
Get P-Chain balance of a P-addr (e.g. P-fuji1...): unlocked, locked stakeable, locked not stakeable. Needed before creating subnets/chains or adding validators.
Inputs: address (required), network.
avax_pchain_get_stake_infoGet staking parameters & supply (P-Chain)ARead-onlyIdempotent
Return P-Chain staking economics: min validator/delegator stake, min/max stake durations, current supply, and total stake. Use when designing validator economics or answering 'how much AVAX do I need to validate?'.
Inputs: network.
avax_pchain_get_subnetGet Subnet / L1 info (P-Chain)ARead-onlyIdempotent
Get Subnet details via platform.getSubnet: control keys, threshold, whether it has been converted to a sovereign L1 (isPermissioned=false), manager chain/address, and blockchains in the subnet.
Inputs: subnet_id (required), network.
avax_pchain_get_tx_statusGet P-Chain tx statusARead-onlyIdempotent
Check a P-Chain transaction (platform.getTxStatus): Committed, Processing, Dropped, or Unknown, with reason when dropped. Use after AddSubnetValidator/ConvertSubnetToL1/CreateChain transactions.
Inputs: tx_id (required), network.
avax_pchain_get_validatorsList current validators (P-Chain)ARead-onlyIdempotent
List current validators of the Primary Network or of a specific Subnet/L1 via platform.getCurrentValidators. Returns nodeID, stake, uptime, end time, delegation fee. Use subnet_id to inspect an L1's validator set; omit for Primary Network.
Inputs: limit, network, node_ids, subnet_id.
avax_pchain_list_blockchainsList blockchains (P-Chain)ARead-onlyIdempotent
List all blockchains registered on the P-Chain (platform.getBlockchains) with their subnet and VM IDs. Supports name filtering and pagination.
Inputs: limit, offset, network, name_contains.
avax_plan_l1_launchPlan an L1 launchARead-onlyIdempotent
Produce a tailored, step-by-step launch plan for a new Avalanche L1 given the use case: consensus mode (PoA/PoS), validator count, gas/token choices, precompile recommendations, ICM, cost estimate and exact CLI commands. Use before avax_generate_genesis.
Inputs: use_case (required), target, needs_icm, validators, +1 more.
avax_search_docsSearch Avalanche documentationARead-onlyIdempotent
Full-text search over the official Avalanche knowledge base (build.avax.network docs, Academy, 234 integrations, blog, all ACPs, AvalancheGo/Subnet-EVM READMEs & precompile docs, ICM/Teleporter contracts, Avalanche CLI command reference, starter kit).
Use this FIRST for any "how do I…", "what is…", "which precompile/config/command…" question about Avalanche, L1s/Subnets, Subnet-EVM, ICM/Teleporter/Warp, P-Chain staking, validators, Avalanche CLI, SDKs, RPC methods.
Args:
query: natural language or keywords (e.g. "native minter precompile genesis", "convert subnet to L1", "teleporter send message fuji")
source: optional filter: docs | academy | integrations (234 ecosystem integrations: oracles, bridges, indexers, wallets, RPC providers…) | blog | acps (Avalanche Community Proposals) | avalanchego | icm | cli | starter-kit
path_prefix: optional path filter, e.g. "content/docs/avalanche-l1s", "content/academy/avalanche-l1", "graft/subnet-evm"
limit: max hits (default 8)
Returns ranked snippets with title, heading, url and path. Call avax_get_doc with a hit's path to read the full page.
Inputs: query (required), limit, source, path_prefix.
avax_search_integrationsSearch ecosystem integrationsARead-onlyIdempotent
Find Avalanche ecosystem integrations (234 entries: oracles, bridges, indexers, RPC providers, wallets, account abstraction, x402, analytics…) by keyword or category. Offline. Returns name, category, chains available, website/docs links.
Inputs: query (required), limit.
avax_troubleshootTroubleshoot an Avalanche errorARead-onlyIdempotent
Given an error message or symptom (RPC error, CLI output, revert reason, ICM delivery issue), return likely causes, fixes, and matching documentation.
Inputs: error_text (required), context.
avax_upgrade_lookupNetwork upgrade timeline (Banff → Helicon)ARead-onlyIdempotent
Structured history of Avalanche Primary Network upgrades: name, AvalancheGo version, Fuji/mainnet activation dates, status, chains affected (P/X/C/L1s), included ACPs, developer impact and source docs. Omit query for the full timeline; pass an upgrade name ('Helicon', 'Etna'), version ('v1.14.0') or ACP number ('ACP-194') for one entry. Pair with avax_acp_lookup and avax_get_doc for full detail.
Inputs: query.
avax_xchain_get_balanceGet X-Chain balanceBRead-onlyIdempotent
Get X-Chain AVAX (or any asset) balance for an X-addr (avm.getBalance).
Inputs: address (required), network, asset_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 41 tools
Most tools map clearly to distinct resources: docs, ACPs, upgrades, EVM reads, P-Chain, X-Chain, and Data API. A few pairs overlap conceptually, such as `avax_get_doc` vs `avax_fetch_live_doc` or the separate balance tools, but the descriptions and prefixes make the intended boundaries clear.
The server consistently uses an `avax_` prefix and mostly follows a verb-first pattern such as `get_*`, `list_*`, `search_*`, and `generate_*`. A few noun-style names like `avax_icm_recipe`, `avax_console_flows`, `avax_acp_votes`, and `avax_node_info` break the pattern, but the overall style remains readable and predictable.
With 41 tools, the server is too heavy and will create selection burden for agents. The many `data_*`, `pchain_*`, and hosted-proxy tools are individually useful but could be consolidated or exposed as parametrized sub-resources to reduce the surface.
The server covers the Avalanche documentation, ACPs, upgrades, network registry, EVM read operations, P-Chain/X-Chain reads, ecosystem integrations, and live data API access. Minor gaps exist, such as missing direct action for some hosted capabilities, but the available surface is comprehensive for a read-oriented knowledge and data server.
Maintenance
Related MCP Connectors
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
17 pay-per-call web, finance, legal and onchain tools for AI agents. USDC on Base via x402/MPP.
Build, validate, and deploy multi-agent AI solutions from any AI environment.
Pay-per-call tools for AI agents, paid in USDC on Base or Solana. Web search, page and PDF reading, crypto news, Hyperliquid perps, market pulse, Chainlink price history, token checks, SEC filings, weather and more. Free calls every day, and a failed call costs nothing. Works with Tollkit Wallet.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive toolkit for building AI agents with blockchain capabilities, enabling interactions with multiple blockchain networks for tasks like wallet management, fund transfers, smart contract interactions, and cross-chain asset bridging.5GPL 3.0
- FlicenseNot gradedqualityNot gradedmaintenanceEnables natural language interaction with the Avalanche blockchain through AI assistants, allowing users to execute Avalanche CLI commands and AvalancheJS API operations without technical knowledge.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the Somnia blockchain network, including documentation search, blockchain queries, wallet management, cryptographic signing, and on-chain operations.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query on-chain data across EVM chains like Base, Optimism, Avalanche, Celo, and Arbitrum, including balances, transactions, gas, and smart contract interactions.53 npmMIT