Avalanche AVAX MCP Server

by airpote Your server? Claim it

answering

Avalanche AVAX MCP is answering right now. Last checked 14 min ago. It exposes 48 tools. Last commit 7 Feb 2026.

Search and retrieve Avalanche blockchain documentation for building on AVAX.

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

252 ms

Response time

average over 24h

Stars

last commit 7 Feb 2026

What changed 58

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

18 Sep the owner changed

17 Sep the owner changed

16 Sep the owner changed

15 Sep the owner changed

14 Sep the owner changed

13 Sep the owner changed

12 Sep the owner changed

11 Sep the owner changed

10 Sep the owner changed

9 Sep the owner changed

and 48 more, back to 9 August 2026

Nothing serious here today

Today is the operative word: we check Avalanche AVAX MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add avalanche-docs --transport http https://build.avax.network/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "avalanche-docs": {
      "url": "https://build.avax.network/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.avalanche-docs]
url = "https://build.avax.network/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "avalanche-docs": {
      "url": "https://build.avax.network/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "avalanche-docs": {
      "url": "https://build.avax.network/api/mcp"
    }
  }
}

Available tools 48

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

platform

platform_get_balance

Get the AVAX balance of one or more P-Chain addresses

platform_get_block

Get a P-Chain block by its block ID

platform_get_block_by_height

Get a P-Chain block by its height

platform_get_blockchains

Get all blockchains that exist on the P-Chain (paginated; use limit/offset)

platform_get_current_supply

Get the current total supply of AVAX on a Subnet/L1

platform_get_current_validators

Get the current validators of a Subnet/L1 (paginated; use limit/offset)

platform_get_height

Get the current P-Chain block height

platform_get_min_stake

Get the minimum staking amounts for validators and delegators on a Subnet/L1

platform_get_pending_validators

Get the pending validators of a Subnet/L1 (paginated; use limit/offset)

platform_get_staking_asset_id

Get the asset ID of the token used for staking on a Subnet/L1

platform_get_subnets

Get information about Subnets/L1s on the P-Chain

platform_get_total_stake

Get the total amount staked on a Subnet/L1

platform_get_tx

Get a P-Chain transaction by its transaction ID

platform_get_tx_status

Get the status of a P-Chain transaction

platform_get_utxos

Get UTXOs that reference a given set of P-Chain addresses

platform_get_validators_at

Get the validators and their weights of a Subnet/L1 at a given P-Chain height

info

info_acps

Get information about Avalanche Community Proposals (ACPs), including their status and vote counts.

info_get_blockchain_id

Get the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C").

info_get_network_id

Get the numeric ID of the Avalanche network this node is participating in.

info_get_network_name

Get the human-readable name of the Avalanche network this node is participating in.

info_get_node_version

Get the version of the node, including the database version, git commit, and API compatibility info.

info_get_tx_fee

Get the current transaction fees for the network, returned in both nAVAX and AVAX.

info_is_bootstrapped

Check whether a given chain has finished bootstrapping on the node.

info_peers

Get a list of peers this node is connected to. Optionally filter by specific NodeIDs.

blockchain

blockchain_get_contract_info

Compatibility alias for onchain_lookup contract metadata. Prefer onchain_lookup for new clients.

blockchain_get_native_balance

Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients.

blockchain_lookup_address

Compatibility alias for onchain_lookup address details. Prefer onchain_lookup for new clients.

blockchain_lookup_chain

Look up a blockchain by its ID — name, VM type, and Subnet/L1.

blockchain_lookup_subnet

Look up a Subnet / L1 by its ID — validators, chains, and configuration.

blockchain_lookup_transaction

Look up a transaction by hash on Avalanche (C-Chain, P-Chain, or X-Chain). Supports 0x format (C-Chain) and CB58 format (P/X-Chain).

blockchain_lookup_validator

Look up a validator by node ID — stake, uptime, delegation info.

avalanche

avalanche_docs_fetch

Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.

avalanche_docs_list_sections

Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.

avalanche_docs_search

Compatibility alias for docs_search. Prefer docs_search for new clients.

docs

docs_fetch

Fetch a specific documentation page as markdown

docs_list_sections

List available documentation sections and their page counts

docs_search

Search body-level chunks across Avalanche documentation, academy courses, integrations, and blog posts. Returns source citations and matching excerpts.

onchain

onchain_activity

Time-windowed on-chain activity. scope=chain/address returns the transaction COUNT over the last `hours` (max 720h = 30 days; for longer windows use chain_stats series or onchain_query day-based ops) plus a recent sample. For a token/contract use scope=token (transfers). scope=primary covers P/X-chain and DEFAULTS to P-Chain when no blockchainId is given (so "last N P-chain transactions" just works). A value with no scope defaults to address.

onchain_lookup

PRIMARY lookup tool — use this (not raw RPC) to resolve/describe any on-chain identifier in one call: an EVM address (native + token balances, recent txs, contract metadata + isContract), a contract/token (metadata + deployment + recent transfers), an NFT (collection + tokenId), a tx hash, a subnet ID, a NodeID validator, a P-/X-Chain account (P-…/X-… → P-Chain balance), or a chain name/id. Use this for any address balance / contract-info / token / identity question. `kind` auto-detects; network is inferred from P-/X-Chain prefixes. Backed by Glacier + P-Chain RPC.

onchain_query

PRIMARY tool for indexed on-chain stats/activity/totals — prefer this over raw RPC for chain data. Each `op` is a backend-agnostic intent: the query gateway selects the most accurate live source per field (indexed DB / pre-aggregated metrics / Data API), stamps every field (`sources`), and flags any caveat (`warnings`) — relay warnings to the user, never present a flagged value as exact. Pick an `op` and pass its `params`; `chainId` is an allowlisted EVM chain (43114 C-Chain, 43113 Fuji, + L1s). Lookback: hour-based ops (chainStatsRecent/chainActivity/addressActivity) max 720h (30 days); day-based ops (chainStatsSeries/contractStats/chainGasTotal/protocolRanking/contractGasFlow/topUnknownContracts) max 365 days — use a day-based op for windows over 30 days. Ops: chainStatsRecent {chainId, hours≤720} — tx count/gas/fees/active senders/avg gas price over the last N hours; chainStatsSeries {chainId, days≤365, bucket: hour|day|week|month} — bucketed time-series of the same; addressActivity {chainId, address, hours≤720, limit≤100} — tx count + recent sample for an address in a window; chainActivity {chainId, hours≤720, limit≤100} — tx count + recent sample chain-wide in a window; contractStats {chainId, contract, days≤365} — tx/unique-sender/gas totals for a contract; protocolRanking {chainId, contracts[≤25], days≤365, orderBy: txCount|gasUsed|uniqueSenders|feesPaidAvax, dir: asc|desc, limit≤100} — rank a set of contracts; contractGasFlow {chainId, contract, days≤365, limit≤100} — gas received/given per counterparty; topUnknownContracts {chainId, exclude[≤25], days≤365, limit≤100} — top contracts by gas excluding a set; chainGasTotal {chainId, days≤365} OR {chainId, fromDate, toDate} — total tx/gas/fees over N days or a YYYY-MM-DD range (≤365d). Note: C-Chain gasUsed is gas-target-regulated → ~stable day-to-day even as txCount varies (expected, not a bug).

acp

acp_list

List Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices, Meta, Subnet).

acp_lookup

Look up Avalanche Community Proposals (ACPs) by number, title, or topic. When a number is provided the structured ACP record is returned (title, status, track, authors, cross-references).

console

console_flow

Builder Console flow knowledge. Call with NO `flow` to list every flow (summaries + deep-links); call with a `flow` key to explain it (ordered steps, equivalent CLI, whether it signs transactions, deep-link). Flows: create-l1, convert-to-l1, validator-manager, ictt, faucet, multisig, staking, transfers, interchain-kit-local.

console_link

Return a deep-link into a specific Builder Console flow (create-l1, convert-to-l1, validator-manager, ictt, faucet, multisig, staking, transfers, interchain-kit-local). For faucet on mainnet, returns a note that there is no mainnet faucet.

build

build_plan

Generate a step-by-step, copy-pasteable runbook for an Avalanche operation — Builder Console (no-code) path plus the equivalent platform-cli / SDK / interchain-kit commands. Read-only: never signs. operation: create-l1 (launch an L1); use ictt or interchain-kit for any CROSS-CHAIN / interoperability work — bridging tokens, sending cross-chain (ICM / Teleporter / Warp) messages, or connecting your L1 to C-Chain or other L1s (interchain-kit also lets you iterate locally first); validator-manager; staking; transfer.

chain

chain_stats

On-chain statistics via the query gateway, which picks the most accurate live source PER FIELD and stamps it (sources/warnings in the response). target=chain: tx count/gas/fees/active senders/avg gas price over a recent window (window=recent, `hours`, max 720h = 30 days) OR a time-series (window=series, `days`, max 365). target=contract: per-contract tx/sender/gas totals (`days`, max 365 — use this for contract activity beyond 30 days). target=network: current P-chain validator snapshot. IMPORTANT: relay any `warnings` notes to the user verbatim-in-substance (e.g. gas coverage windows or accuracy caveats) — never present a flagged value as exact. Note: C-Chain gasUsed is gas-target-regulated, so daily gas is ~stable even as tx count varies — expected, not an error.

cli

cli_lookup_command

Look up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs. Returns cited command references and task docs.

rpc

rpc_lookup_method

Look up Avalanche RPC methods and API guides across C-Chain, P-Chain, X-Chain, Subnet-EVM, and node RPC docs.

Endpoints

URL	Transport	State	Latency	Checked
https://build.avax.network/api/mcp	streamable-http	answering	212 ms	14 min ago

Alternatives to Avalanche AVAX MCP

same job, measured the same way

Mst MCP

by vipulsutar11

MCP server for the MST Chain ecosystem providing search and retrieval tools for documentation.

local only

DevExpress Documentation

by devexpress

Streamable HTTP MCP server for DevExpress documentation search and retrieval.

2 tools answering

MCP Docs Server

by praveenc

MCP server for searching MCP protocol documentation

46 installs/wk local only

Qiskit Documentation MCP Server

by qiskit

MCP server for querying and retrieving Qiskit documentation, guides, and API references

131 installs/wk local only

MTA:SA Documentation MCP Server

by luminaire1337

MCP server for MTA:SA documentation with intelligent search and caching

45 installs/wk local only

Docmancer

by docmancer

Local-only MCP server for source-attributed Markdown memory and documentation retrieval.

1 149 installs/wk local only

MCP Plesk Dev Docs

by barateza

An MCP server that indexes and retrieves Plesk documentation.

89 installs/wk local only

Data

by vdappdev2

MCP server for Verus on-chain data retrieval, decryption, signing, and verification

50 installs/wk local only

Avalanche AVAX MCP — questions

Answers built from our own checks of this server.

What can Avalanche AVAX MCP do?

It exposes 48 tools, read directly from the server on our last check. Among them: acp_list, acp_lookup, avalanche_docs_fetch, avalanche_docs_list_sections, avalanche_docs_search, blockchain_get_contract_info and 42 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Avalanche AVAX MCP mostly used for?

Its tools cluster around platform, info and blockchain. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Avalanche AVAX MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 252 ms. The bar chart above shows every period we have measured.

How do I connect Avalanche AVAX MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Avalanche AVAX MCP need an API key?

No. Avalanche AVAX MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 48 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Avalanche AVAX MCP?

It answers our handshake in 252 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Avalanche AVAX MCP open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.