# Avalanche AVAX MCP (remote · build.avax.network)

Search and retrieve Avalanche blockchain documentation for building on AVAX.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `build.avax.network`: 67/100 (this document), [markdown](https://verifymcp.io/servers/airpote-avalanche-docs/api-mcp.md), [page](https://verifymcp.io/servers/airpote-avalanche-docs/api-mcp)

## Channel facts

- Endpoint: `https://build.avax.network/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 48 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 4919 tokens (~89/item across 55 items; 48 tools + 7 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability check failed: schema churn in the 8 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 7 additions.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "airpote-avalanche-docs": {
      "type": "remote",
      "url": "https://build.avax.network/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add airpote-avalanche-docs --url https://build.avax.network/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  airpote-avalanche-docs:
    url: "https://build.avax.network/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "airpote-avalanche-docs": {
      "type": "http",
      "url": "https://build.avax.network/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.

### 2026-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13.

### 2026-07-31 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7.

### 2026-07-29 (score 64, −1)

- [security regression] Stability: 0.07 → fail
- [security regression] Tool “github_get_file” was removed
- [security regression] Tool “github_list_repositories” was removed
- [security regression] Tool “github_search_code” was removed
- [security] Tool “blockchain_get_contract_info” rewrote its description, which is the text the model reads
- [security] Tool “blockchain_get_native_balance” rewrote its description, which is the text the model reads
- [security] Tool “blockchain_lookup_address” rewrote its description, which is the text the model reads
- [security] Tool “platform_get_blockchains” rewrote its description, which is the text the model reads
- [security] Tool “platform_get_current_validators” rewrote its description, which is the text the model reads
- [security] Tool “platform_get_pending_validators” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 56 → 89
- [functional] Schema quality: excellent → good
- [functional] Server version: 2.1.0 → 2.4.0
- [functional] New tool “build_plan”
- [functional] New tool “chain_stats”
- [functional] New tool “console_flow”
- [functional] New tool “console_link”
- [functional] New tool “onchain_activity”
- [functional] New tool “onchain_lookup”
- [functional] New tool “onchain_query”
- [cosmetic] “platform_get_blockchains” added an optional parameter “limit”
- [cosmetic] “platform_get_blockchains” added an optional parameter “offset”
- [cosmetic] “platform_get_current_validators” added an optional parameter “limit”
- [cosmetic] “platform_get_current_validators” added an optional parameter “offset”
- [cosmetic] “platform_get_pending_validators” added an optional parameter “limit”
- [cosmetic] “platform_get_pending_validators” added an optional parameter “offset”
- [cosmetic] “platform_get_subnets” added an optional parameter “limit”
- [cosmetic] “platform_get_subnets” added an optional parameter “offset”
- [cosmetic] “blockchain_get_contract_info” reworded the description of “address”
- [cosmetic] “blockchain_get_contract_info” reworded the description of “chainId”
- [cosmetic] “blockchain_get_native_balance” reworded the description of “chainId”
- [cosmetic] “blockchain_lookup_address” reworded the description of “address”
- [cosmetic] “blockchain_lookup_address” reworded the description of “chainId”

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (48)

### `docs_search` (~72 tokens)

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

Input parameters:

- `limit` (number): Maximum number of chunk results (default: 10)
- `query` (string, required): The search query
- `source` (string): Filter by documentation source (optional)

### `docs_fetch` (~38 tokens)

Fetch a specific documentation page as markdown

Input parameters:

- `url` (string, required): The page URL path (e.g., /docs/primary-network/overview)

### `docs_list_sections` (~18 tokens)

List available documentation sections and their page counts

### `cli_lookup_command` (~81 tokens)

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

Input parameters:

- `cli` (string): CLI surface to search. Defaults to all.
- `limit` (number): Maximum number of results (default: 8)
- `query` (string, required): Command, flag, or task to look up

### `rpc_lookup_method` (~88 tokens)

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

Input parameters:

- `chain` (string): RPC area to search. Defaults to all.
- `limit` (number): Maximum number of results (default: 8)
- `query` (string, required): RPC method, namespace, or task to look up

### `acp_lookup` (~93 tokens)

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).

Input parameters:

- `limit` (number): Maximum number of results (default: 8)
- `number` (number): ACP number, if known
- `query` (string): ACP title, topic, or keyword

### `acp_list` (~107 tokens)

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

Input parameters:

- `limit` (number): Maximum number of ACPs to return (default: 50)
- `status` (string): Filter by ACP status (case-insensitive)
- `track` (string): Filter by ACP track. Matches Standards, Best Practices, Meta, or Subnet.

### `avalanche_docs_search` (~62 tokens)

Compatibility alias for docs_search. Prefer docs_search for new clients.

Input parameters:

- `limit` (number): Maximum number of chunk results (default: 10)
- `query` (string, required): The search query
- `source` (string): Filter by documentation source (optional)

### `avalanche_docs_fetch` (~44 tokens)

Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.

Input parameters:

- `url` (string, required): The page URL path (e.g., /docs/primary-network/overview)

### `avalanche_docs_list_sections` (~25 tokens)

Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.

### `blockchain_lookup_transaction` (~87 tokens)

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).

Input parameters:

- `network` (string): Network to search
- `txHash` (string, required): Transaction hash (0x... for C-Chain, CB58 for P/X-Chain)

### `blockchain_lookup_subnet` (~48 tokens)

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

Input parameters:

- `network` (string)
- `subnetId` (string, required): The Subnet ID

### `blockchain_lookup_chain` (~43 tokens)

Look up a blockchain by its ID — name, VM type, and subnet.

Input parameters:

- `chainId` (string, required): The blockchain ID
- `network` (string)

### `blockchain_lookup_validator` (~64 tokens)

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

Input parameters:

- `network` (string)
- `nodeId` (string, required): Node ID (e.g. NodeID-...)
- `subnetId` (string): Subnet ID (default: Primary Network)

### `platform_get_height` (~34 tokens)

Get the current P-Chain block height

Input parameters:

- `network` (string): Avalanche network to query (default: mainnet)

### `platform_get_block` (~67 tokens)

Get a P-Chain block by its block ID

Input parameters:

- `blockID` (string, required): The CB58-encoded block ID
- `encoding` (string): Encoding format for the block (default: json)
- `network` (string): Avalanche network to query (default: mainnet)

### `platform_get_block_by_height` (~66 tokens)

Get a P-Chain block by its height

Input parameters:

- `encoding` (string): Encoding format for the block (default: json)
- `height` (string, required): The block height as a string
- `network` (string): Avalanche network to query (default: mainnet)

### `platform_get_blockchains` (~90 tokens)

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

Input parameters:

- `limit` (number): Max items to return (default: 50). Use with "offset" to page.
- `network` (string): Avalanche network to query (default: mainnet)
- `offset` (number): Number of items to skip from the start (default: 0).

### `platform_get_subnets` (~96 tokens)

Get information about subnets on the P-Chain

Input parameters:

- `ids` (array): Optional list of subnet IDs to filter by
- `limit` (number): Max items to return (default: 50). Use with "offset" to page.
- `network` (string): Avalanche network to query (default: mainnet)
- `offset` (number): Number of items to skip from the start (default: 0).

### `platform_get_current_validators` (~123 tokens)

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

Input parameters:

- `limit` (number): Max items to return (default: 50). Use with "offset" to page.
- `network` (string): Avalanche network to query (default: mainnet)
- `nodeIDs` (array): Optional list of node IDs to filter by
- `offset` (number): Number of items to skip from the start (default: 0).
- `subnetID` (string): The subnet ID to query validators for (default: Primary Network)

### `platform_get_pending_validators` (~124 tokens)

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

Input parameters:

- `limit` (number): Max items to return (default: 50). Use with "offset" to page.
- `network` (string): Avalanche network to query (default: mainnet)
- `nodeIDs` (array): Optional list of node IDs to filter by
- `offset` (number): Number of items to skip from the start (default: 0).
- `subnetID` (string): The subnet ID to query pending validators for (default: Primary Network)

### `platform_get_staking_asset_id` (~64 tokens)

Get the asset ID of the token used for staking on a subnet

Input parameters:

- `network` (string): Avalanche network to query (default: mainnet)
- `subnetID` (string): The subnet ID to query the staking asset for (default: Primary Network)

### `platform_get_min_stake` (~62 tokens)

Get the minimum staking amounts for validators and delegators on a subnet

Input parameters:

- `network` (string): Avalanche network to query (default: mainnet)
- `subnetID` (string): The subnet ID to query minimum stake for (default: Primary Network)

### `platform_get_total_stake` (~58 tokens)

Get the total amount staked on a subnet

Input parameters:

- `network` (string): Avalanche network to query (default: mainnet)
- `subnetID` (string): The subnet ID to query total stake for (default: Primary Network)

### `platform_get_balance` (~63 tokens)

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

Input parameters:

- `addresses` (array, required): List of P-Chain addresses to query (e.g. P-avax1...)
- `network` (string): Avalanche network to query (default: mainnet)

### `platform_get_utxos` (~97 tokens)

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

Input parameters:

- `addresses` (array, required): List of P-Chain addresses to get UTXOs for
- `limit` (number): Maximum number of UTXOs to return
- `network` (string): Avalanche network to query (default: mainnet)
- `sourceChain` (string): If fetching atomic UTXOs, the chain they were exported from

### `platform_get_tx` (~67 tokens)

Get a P-Chain transaction by its transaction ID

Input parameters:

- `encoding` (string): Encoding format for the transaction (default: json)
- `network` (string): Avalanche network to query (default: mainnet)
- `txID` (string, required): The CB58-encoded transaction ID

### `platform_get_tx_status` (~51 tokens)

Get the status of a P-Chain transaction

Input parameters:

- `network` (string): Avalanche network to query (default: mainnet)
- `txID` (string, required): The CB58-encoded transaction ID

### `platform_get_current_supply` (~59 tokens)

Get the current total supply of AVAX on a subnet

Input parameters:

- `network` (string): Avalanche network to query (default: mainnet)
- `subnetID` (string): The subnet ID to query current supply for (default: Primary Network)

### `platform_get_validators_at` (~83 tokens)

Get the validators and their weights of a subnet at a given P-Chain height

Input parameters:

- `height` (required): The P-Chain height to query validators at, or "proposed"
- `network` (string): Avalanche network to query (default: mainnet)
- `subnetID` (string): The subnet ID to query validators for (default: Primary Network)

### `info_get_node_version` (~47 tokens)

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

Input parameters:

- `network` (string): The Avalanche network to query (default: mainnet)

### `info_get_network_id` (~41 tokens)

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

Input parameters:

- `network` (string): The Avalanche network to query (default: mainnet)

### `info_get_network_name` (~42 tokens)

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

Input parameters:

- `network` (string): The Avalanche network to query (default: mainnet)

### `info_get_blockchain_id` (~82 tokens)

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

Input parameters:

- `alias` (string, required): The blockchain alias (e.g., "X", "P", "C", or a full blockchain name)
- `network` (string): The Avalanche network to query (default: mainnet)

### `info_is_bootstrapped` (~68 tokens)

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

Input parameters:

- `chain` (string, required): The chain ID or alias to check (e.g., "X", "P", "C")
- `network` (string): The Avalanche network to query (default: mainnet)

### `info_get_tx_fee` (~46 tokens)

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

Input parameters:

- `network` (string): The Avalanche network to query (default: mainnet)

### `info_peers` (~80 tokens)

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

Input parameters:

- `network` (string): The Avalanche network to query (default: mainnet)
- `nodeIDs` (array): Optional list of NodeIDs to filter peers by (e.g., ["NodeID-AbC..."]). If omitted, all peers are returned.

### `info_acps` (~44 tokens)

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

Input parameters:

- `network` (string): The Avalanche network to query (default: mainnet)

### `blockchain_get_native_balance` (~63 tokens)

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

Input parameters:

- `address` (string, required): EVM address (0x...)
- `chainId` (string): 43114 for C-Chain mainnet, 43113 for Fuji

### `blockchain_get_contract_info` (~62 tokens)

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

Input parameters:

- `address` (string, required): Contract address (0x...)
- `chainId` (string): 43114 for C-Chain mainnet, 43113 for Fuji

### `blockchain_lookup_address` (~62 tokens)

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

Input parameters:

- `address` (string, required): EVM address (0x...)
- `chainId` (string): 43114 for C-Chain mainnet, 43113 for Fuji

### `onchain_lookup` (~277 tokens)

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.

Input parameters:

- `chainId` (string): EVM chain ID for EVM kinds (default: C-Chain for the network)
- `include` (array): Extra data for an address (e.g. ["nfts"])
- `kind` (string): Entity kind (default: auto-detect from value)
- `network` (string): Network (default: mainnet)
- `tokenId` (string): NFT token ID (kind=nft)
- `value` (string, required): The identifier: 0x address / 0x tx hash / NodeID-… / subnetId / chain name or id

### `onchain_activity` (~295 tokens)

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.

Input parameters:

- `blockchainId` (string): Blockchain ID for scope=primary (default: P-Chain)
- `chainId` (string): EVM chain ID (default: C-Chain for the network)
- `feed` (string): transactions (default) | transfers | erc20Transfers | nftTransfers
- `fromTimestamp` (number): Unix start time (scope=primary)
- `hours` (number): Look-back window in hours for EVM transaction feeds (default: 2 for chain, max 720)
- `network` (string): Network (default: mainnet)
- `pageSize` (number): Max rows (default: 25)
- `scope` (string, required): address | chain | token | contract | primary
- `toTimestamp` (number): Unix end time (scope=primary)
- `value` (string): Address/contract/token (omit for scope=chain)

### `chain_stats` (~340 tokens)

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.

Input parameters:

- `chainId` (string): EVM chain ID (default: C-Chain for the network)
- `days` (number): Look-back days for series / contract (default: 30, max 365)
- `hours` (number): Look-back hours for window=recent (default: 24, max 720)
- `network` (string): Network (default: mainnet)
- `target` (string): chain (default) | contract | network
- `timeInterval` (string): Bucket size for window=series (default: day)
- `value` (string): Contract address (target=contract)
- `window` (string): chain: recent aggregate (default) or series

### `onchain_query` (~550 tokens)

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).

Input parameters:

- `op` (string, required): The query operation
- `params` (object, required): Op-specific parameters (see description); validated server-side.

### `build_plan` (~434 tokens)

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.

Input parameters:

- `amount` (string): transfer: amount
- `chainId` (string): create-l1: EVM chain ID
- `duration` (string): staking: staking period (e.g. 336h)
- `example` (string): interchain-kit: which example to run
- `homeChain` (string): ictt: home chain (where the token originates)
- `name` (string): create-l1: L1 name (default: myL1)
- `network` (string): Target network (default: fuji)
- `nodeId` (string): staking: NodeID-…
- `operation` (string, required): Which runbook to generate
- `remoteChain` (string): ictt: destination chain (required for operation=ictt)
- `stake` (string): staking: stake amount
- `to` (string): transfer: destination address (transferKind=send)
- `token` (string): ictt: token contract address (or "native")
- `tokenSymbol` (string): create-l1: native token symbol
- `tokenType` (string): ictt: token type (default: erc20)
- `transferKind` (string): transfer: kind (default: send)
- `type` (string): validator-manager: manager type (alias of validatorManager)
- `validatorManager` (string): create-l1 / validator-manager: model (default: poa)
- `vm` (string): create-l1: VM type (default: subnet-evm)

### `console_link` (~111 tokens)

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.

Input parameters:

- `flow` (string, required): The console flow to link to
- `network` (string): Network (only affects faucet; default: fuji)
- `validatorManager` (string): Validator-manager variant (default: poa)

### `console_flow` (~105 tokens)

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.

Input parameters:

- `flow` (string): Flow key to explain. Omit to list all flows.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/airpote-avalanche-docs/api-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 65
- 2026-07-29: 64
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://build.avax.network/api/mcp
- Repository: https://github.com/Airpote/avalanche-mcp-vscode
- Website: https://build.avax.network/
- Changelog RSS feed: https://verifymcp.io/servers/airpote-avalanche-docs/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/airpote-avalanche-docs/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/airpote-avalanche-docs/api-mcp