Avalanche AVAX MCP
Search and retrieve Avalanche blockchain documentation for building on AVAX.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://build.avax.network/api/mcp | registry |
|---|---|---|
| Website | build.avax.network | registry |
| Handshake | Answers the MCP handshake and lists its tools (708 ms) | our check, 2026-11-18 |
| Protocol version | 2024-11-05 | our check, 2026-11-18 |
| Tools (47) | docs_search, docs_fetch, docs_list_sections, cli_lookup_command, rpc_lookup_method, acp_lookup, acp_list, avalanche_docs_search, avalanche_docs_fetch, avalanche_docs_list_sections, blockchain_lookup_transaction, blockchain_lookup_subnet, blockchain_lookup_chain, blockchain_lookup_validator, platform_get_height, platform_get_block, platform_get_block_by_height, platform_get_blockchains, platform_get_subnets, platform_get_current_validators, platform_get_pending_validators, platform_get_staking_asset_id, platform_get_min_stake, platform_get_total_stake, platform_get_balance, platform_get_utxos, platform_get_tx, platform_get_tx_status, platform_get_current_supply, platform_get_validators_at, info_get_node_version, info_get_network_id, info_get_network_name, info_get_blockchain_id, info_is_bootstrapped, info_get_tx_fee, info_peers, info_acps, blockchain_get_native_balance, blockchain_get_contract_info, blockchain_lookup_address, onchain_lookup, onchain_activity, chain_stats, build_plan, console_link, console_flow | tools/list, 2026-11-18 |
| GitHub stars | 0 | github.com/Airpote/avalanche-mcp-vscode |
| Last push | 2026-02-07 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 1.0.1 · active · updated 2026-02-05 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http avalanche-docs https://build.avax.network/api/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Avalanche Forecast and Danger Rating MCP Avalanche forecast: danger rating by zone and elevation, problems and bottom line…
- avalanche Act on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/io.github.Airpote/avalanche-docs)<a href="https://openforallofus.com/tools/io.github.Airpote/avalanche-docs"><img src="https://openforallofus.com/badge/io.github.Airpote/avalanche-docs.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.Airpote/avalanche-docs.