mcpbeat Sign in

Avalanche AVAX MCP Server

answering

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

Search and retrieve Avalanche blockchain documentation for building on AVAX.

Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
47
Tools
read from the server
288 ms
Response time
average over 24h
0
Stars
last commit 7 Feb 2026

What changed 24

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

22 Oct 2 tools changed the parameters they ask for chain_stats, onchain_activity
22 Oct 2 tool descriptions were rewritten chain_stats, onchain_activity
22 Oct a tool changed version
22 Oct a tool disappeared onchain_query
19 Aug 9 tool descriptions were rewritten blockchain_lookup_chain, platform_get_current_supply, platform_get_current_validators and 6 more
19 Aug 8 tools changed the parameters they ask for platform_get_current_supply, platform_get_current_validators, platform_get_min_stake and 5 more
9 Aug the owner changed

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add avalanche-docs --transport http https://build.avax.network/api/mcp
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "avalanche-docs": {
      "type": "http",
      "url": "https://build.avax.network/api/mcp"
    }
  }
}

Available tools 47

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.
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.
onchain
onchain_activity
Recent on-chain activity. scope=chain returns the transaction COUNT over the last `hours` (closed hours, max 720h = 30 days; for longer windows use chain_stats window=series) plus the latest transactions. scope=address returns the latest transactions of the address, with no time window. 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.
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
Chain statistics from the Avalanche Stats API (pre-aggregated; closed periods only, so the current hour or day is not included). target=chain: tx count, gas used, fees paid and average gas price over the last `hours` (window=recent, max 720h = 30 days), or a time-series that also has active senders (window=series, `days` max 365; timeInterval=hour max 90 days). target=network: current P-chain validator snapshot. There are no per-contract stats here; for those, run SQL in the Builder Hub explorer Query page. Note: C-Chain gasUsed is gas-target-regulated, so daily gas is about stable even as tx count varies. That is 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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

onchain_query
removed 22 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://build.avax.network/api/mcp streamable-http answering 247 ms 15 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
Documentation Search
by alyiox

Local RAG MCP for markdown documentation. Retrieval only; host synthesizes answers.

263 installs/wk local only
MCP Docs Server
by praveenc

MCP server for searching MCP protocol documentation

43 installs/wk local only
Qiskit Documentation MCP Server
by qiskit

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

761 installs/wk local only
MTA:SA Documentation MCP Server
by luminaire1337

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

53 installs/wk local only
Docmancer
by docmancer

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

570 installs/wk local only
MCP Plesk Dev Docs
by barateza

An MCP server that indexes and retrieves Plesk documentation.

132 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 47 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 41 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 288 ms. The bar chart above shows every period we have measured.
Did Avalanche AVAX MCP ever remove tools?
Yes. onchain_query is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
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 in the form 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 47 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 288 ms on average, which is faster than 47% 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?
The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at build.avax.network, which runs on its operator's own terms.