Connect Avalanche Documentation and your agent gets 48 tools, among them acp_list, acp_lookup, avalanche_docs_fetch. It answers at https://build.avax.network/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Search and retrieve Avalanche blockchain documentation for building on AVAX.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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). Inputs: status, track, limit |
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). Inputs: query, number, limit |
avalanche_docs_fetch | Compatibility alias for docs_fetch. Prefer docs_fetch for new clients. Inputs: url |
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. Inputs: query, source, limit |
blockchain_get_contract_info | Compatibility alias for onchain_lookup contract metadata. Prefer onchain_lookup for new clients. Inputs: address, chainId |
blockchain_get_native_balance | Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients. Inputs: address, chainId |
blockchain_lookup_address | Compatibility alias for onchain_lookup address details. Prefer onchain_lookup for new clients. Inputs: address, chainId |
blockchain_lookup_chain | Look up a blockchain by its ID — name, VM type, and Subnet/L1. Inputs: chainId, network |
blockchain_lookup_subnet | Look up a Subnet / L1 by its ID — validators, chains, and configuration. Inputs: subnetId, network |
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). Inputs: txHash, network |
blockchain_lookup_validator | Look up a validator by node ID — stake, uptime, delegation info. Inputs: nodeId, subnetId, network |
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 i Inputs: operation, network, name, vm, validatorManager, chainId |
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=recen Inputs: target, window, chainId, value, timeInterval, hours |
cli_lookup_command | Look up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs. Returns cited command references and task docs. Inputs: query, cli, limit |
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 Inputs: flow |
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. Inputs: flow, network, validatorManager |
docs_fetch | Fetch a specific documentation page as markdown Inputs: url |
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. Inputs: query, source, limit |
info_acps | Get information about Avalanche Community Proposals (ACPs), including their status and vote counts. Inputs: network |
info_get_blockchain_id | Get the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C"). Inputs: alias, network |
info_get_network_id | Get the numeric ID of the Avalanche network this node is participating in. Inputs: network |
info_get_network_name | Get the human-readable name of the Avalanche network this node is participating in. Inputs: network |
info_get_node_version | Get the version of the node, including the database version, git commit, and API compatibility info. Inputs: network |
info_get_tx_fee | Get the current transaction fees for the network, returned in both nAVAX and AVAX. Inputs: network |
info_is_bootstrapped | Check whether a given chain has finished bootstrapping on the node. Inputs: chain, network |
info_peers | Get a list of peers this node is connected to. Optionally filter by specific NodeIDs. Inputs: nodeIDs, network |
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/contra Inputs: scope, value, feed, network, chainId, blockchainId |
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 tra Inputs: value, kind, network, chainId, tokenId, include |
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 metric Inputs: op, params |
platform_get_balance | Get the AVAX balance of one or more P-Chain addresses Inputs: addresses, network |
platform_get_block | Get a P-Chain block by its block ID Inputs: blockID, encoding, network |
platform_get_block_by_height | Get a P-Chain block by its height Inputs: height, encoding, network |
platform_get_blockchains | Get all blockchains that exist on the P-Chain (paginated; use limit/offset) Inputs: network, limit, offset |
platform_get_current_supply | Get the current total supply of AVAX on a Subnet/L1 Inputs: subnetID, network |
platform_get_current_validators | Get the current validators of a Subnet/L1 (paginated; use limit/offset) Inputs: subnetID, nodeIDs, network, limit, offset |
platform_get_height | Get the current P-Chain block height Inputs: network |
platform_get_min_stake | Get the minimum staking amounts for validators and delegators on a Subnet/L1 Inputs: subnetID, network |
platform_get_pending_validators | Get the pending validators of a Subnet/L1 (paginated; use limit/offset) Inputs: subnetID, nodeIDs, network, limit, offset |
platform_get_staking_asset_id, platform_get_subnets, platform_get_total_stake, platform_get_tx, platform_get_tx_status, platform_get_utxos, platform_get_validators_at, rpc_lookup_method
Every block below points at https://build.avax.network/api/mcp. Pick your client and copy.
claude mcp add --transport http avalanche-documentation https://build.avax.network/api/mcp
{
"mcpServers": {
"avalanche-documentation": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://build.avax.network/api/mcp"]
}
}
}{
"mcpServers": {
"avalanche-documentation": {
"url": "https://build.avax.network/api/mcp"
}
}
}{
"servers": {
"avalanche-documentation": {
"type": "http",
"url": "https://build.avax.network/api/mcp"
}
}
}{
"context_servers": {
"avalanche-documentation": {
"url": "https://build.avax.network/api/mcp"
}
}
}{
"mcpServers": {
"avalanche-documentation": {
"serverUrl": "https://build.avax.network/api/mcp"
}
}
}{
"mcpServers": {
"avalanche-documentation": {
"url": "https://build.avax.network/api/mcp"
}
}
}name: Avalanche Documentation
version: 0.0.1
schema: v1
mcpServers:
- name: Avalanche Documentation
type: streamable-http
url: https://build.avax.network/api/mcp{
"mcpServers": {
"avalanche-documentation": {
"httpUrl": "https://build.avax.network/api/mcp"
}
}
}{
"mcpServers": {
"avalanche-documentation": {
"type": "http",
"url": "https://build.avax.network/api/mcp"
}
}
}{
"mcpServers": {
"avalanche-documentation": {
"url": "https://build.avax.network/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbuild.avax.network%2Fapi%2Fmcp&type=streamable_http&id=avalanche-documentation&name=Avalanche%20Documentation
It answered our last check on 18 October 2026 in 239 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
48, as returned by the server's own tools/list on 31 August 2026: acp_list, acp_lookup, avalanche_docs_fetch, avalanche_docs_list_sections, avalanche_docs_search, blockchain_get_contract_info, blockchain_get_native_balance, blockchain_lookup_address, and 40 more.
It answered our last check on 18 October 2026 in 239 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://build.avax.network/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.airpote. Endpoint host: build.avax.network. ARD identifier: urn:air:io.github.airpote:mcp:avalanche-docs.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.