Home / MCP registry index / io.github.Airpote/avalanche-docs

Avalanche AVAX MCP

io.github.Airpote/avalanche-docs in the official MCP registry. Endpoint https://build.avax.network/api/mcp. Source: github.com/Airpote/avalanche-mcp-vscode.

The registry describes it as: Search and retrieve Avalanche blockchain documentation for building on AVAX.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

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

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

code --add-mcp '{"name":"avalanche-docs","type":"http","url":"https://build.avax.network/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

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

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-airpote-avalanche-docs/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-airpote-avalanche-docs)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers