Avalanche AVAX MCP

安装

选择你使用的 AI 应用，然后复制设置。

通过 4/5 项检查 · 你的提问会经过开发者的服务器（build.avax.network）

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

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

{
  "servers": {
    "avalanche-docs": {
      "type": "http",
      "url": "https://build.avax.network/api/mcp"
    }
  }
}

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档，检查于 2026年11月10日。

通过互联网连接，适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月10日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• docs_search

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

• docs_fetch

  Fetch a specific documentation page as markdown

• docs_list_sections

  List available documentation sections and their page counts

• cli_lookup_command

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

• rpc_lookup_method

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

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

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

• avalanche_docs_search

  Compatibility alias for docs_search. Prefer docs_search for new clients.

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

• 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_subnet

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

• blockchain_lookup_chain

  Look up a blockchain by its ID — name, VM type, and Subnet/L1.

• blockchain_lookup_validator

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

• platform_get_height

  Get the current P-Chain block height

• 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_subnets

  Get information about Subnets/L1s on the P-Chain

• platform_get_current_validators

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

• 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_min_stake

  Get the minimum staking amounts for validators and delegators on a Subnet/L1

• platform_get_total_stake

  Get the total amount staked on a Subnet/L1

• platform_get_balance

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

• platform_get_utxos

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

• 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_current_supply

  Get the current total supply of AVAX on a Subnet/L1

• platform_get_validators_at

  Get the validators and their weights of a Subnet/L1 at a given P-Chain height

• info_get_node_version

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

• 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_blockchain_id

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

• info_is_bootstrapped

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

• info_get_tx_fee

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

• info_peers

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

• info_acps

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

• blockchain_get_native_balance

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

• blockchain_get_contract_info

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

• blockchain_lookup_address

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

• 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),

• 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

• 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

• 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-CHAI

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

• 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, multi

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月12日

• ✓ 通过

  作者与仓库一致

  注册名称已通过 GitHub 账户 yassirboudda 验证，该账户拥有此仓库

• ! 注意

  仍在维护

  代码最后更新于9个月前，已超过 6 个月

• ✓ 通过

  有许可证

  使用 MIT

• ✓ 通过

  端点有响应

  在 53 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 47 个工具描述，未发现针对 AI 的隐藏指令

用户评价

还没有评价

用 Google 登录后写评价

与“加密货币与区块链”中的其他服务器比较i

• 星标数多于此分类中其他 1663 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1663 个服务器的 1% 更新
• 基础检查结果等于或优于此分类中其他 1663 个服务器的 60%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

同类别的其他选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Solana MCP by Vybe

Solana MCP developer toolkit: wallets, trades, markets, PnL, transfers, onchain, swaps & API tools.

作者：vybenetwork·正在增长·★ 2628 整个仓库的星标·6个月前更新

在云端运行

安装

Oracle3 prediction-market arbitrage checks

Kalshi and Polymarket data, venue fees, no-arbitrage checks and paper execution for AI agents.

作者：YichengYang-Ethan·正在增长·↓ 35/周·★ 569·42天前更新

在你的电脑上运行

安装

Polymarket Paper Trader

Polymarket paper trading for AI agents: $10k paper money, real order books, official fees.

作者：agent-next·正在增长·↓ 226/周·★ 506·27天前更新

在你的电脑上运行

安装

作者的 README

# Start full development environment

# Run latest stable release

# Build the latest CLI

# Run lint, unit tests and integration tests

├── cmd/                     # Application entry points