Avalanche AVAX MCP

io.github.Airpote由 GitHub 帳號 Airpote 發布v1.0.1更新於 Oct 24, 2026

Search and retrieve Avalanche blockchain documentation for building on AVAX.

已驗證Streamable HTTP可網頁執行金融知識與記憶開發者工具

概覽

AI 產生的概覽

遠端 MCP 伺服器，讓助理搜尋 Avalanche 文件與 ACP 提案，並查詢鏈上交易、Subnet、驗證者與 P-Chain 質押資料。

可以做什麼
搜尋、讀取 Avalanche 文件頁面並列出文件章節與篇數。查詢 Avalanche CLI、Platform CLI 與 tmpnet 指令，以及 C/P/X 鏈、Subnet-EVM 與節點 RPC 方法。依編號、標題或主題查詢 ACP 提案，並依狀態或類別列出提案。依雜湊查詢交易，依 ID 查詢 Subnet/L1、區塊鏈與驗證者。查詢 P-Chain 區塊高度、區塊、Subnet、驗證者、質押金額、餘額、UTXO 與交易狀態。查詢節點版本、網路 ID 與名稱、區塊鏈 ID、開機同步狀態、手續費與對等節點。
適用情境
當你需要查詢 Avalanche 文件、ACP 提案、CLI 指令或 RPC 方法，或想直接查看鏈上交易、Subnet、驗證者與 P-Chain 質押資料時，適合加入此伺服器。
執行需求
需要可連線至 build.avax.network 遠端端點的網路存取；宣告中未要求帳號、API 金鑰或環境變數。
安裝前請注意
部分工具會查詢公開鏈上資料（交易、地址餘額、驗證者、節點對等資訊），這些查詢會送往第三方端點。工具皆為唯讀查詢，未顯示寫入、發送或刪除資料的能力。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Avalanche AVAX MCP，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.Airpote%2Favalanche-docs/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

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

README

MCP Registry

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.

📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation

Development Status

2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!

2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).

Current key maintainers:

Contributing

We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.

Often (but not always) ideas flow through this pipeline:

  • Discord - Real-time community discussions
  • Discussions - Propose and discuss product/technical requirements
  • Issues - Track well-scoped technical work
  • Pull Requests - Contribute work towards issues

Quick start:

Pre-requisites
Running the server
bash
# Start full development environmentmake dev-compose

This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.

The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.

Alternative: Running a pre-built Docker image

Pre-built Docker images are automatically published to GitHub Container Registry:

bash
# Run latest stable releasedocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
# Run latest from main branch (continuous deployment)docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
# Run specific release versiondocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
# Run development build from main branchdocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d

Available tags:

  • Releases: latest, v1.0.0, v1.1.0, etc.
  • Continuous: main (latest main branch build)
  • Development: main-<date>-<sha> (specific commit builds)
Publishing a server

To publish a server, we've built a simple CLI. You can use it with:

bash
# Build the latest CLImake publisher
# Use it!./bin/mcp-publisher --help

See the publisher guide for more details.

Other commands
bash
# Run lint, unit tests and integration testsmake check

There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.

Architecture

Project Structure

├── cmd/                     # Application entry points│   └── publisher/           # Server publishing tool├── data/                    # Seed data├── deploy/                  # Deployment configuration (Pulumi)├── docs/                    # Documentation├── internal/                # Private application code│   ├── api/                 # HTTP handlers and routing│   ├── auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)│   ├── config/              # Configuration management│   ├── database/            # Data persistence (PostgreSQL)│   ├── service/             # Business logic│   ├── telemetry/           # Metrics and monitoring│   └── validators/          # Input validation├── pkg/                     # Public packages│   ├── api/                 # API types and structures│   │   └── v0/              # Version 0 API types│   └── model/               # Data models for server.json├── scripts/                 # Development and testing scripts├── tests/                   # Integration tests└── tools/                   # CLI tools and utilities    └── validate-*.sh        # Schema validation tools

Authentication

Publishing supports multiple authentication methods:

  • GitHub OAuth - For publishing by logging into GitHub
  • GitHub OIDC - For publishing from GitHub Actions
  • DNS verification - For proving ownership of a domain and its subdomains
  • HTTP verification - For proving ownership of a domain

The registry validates namespace ownership when publishing. E.g. to publish...:

  • io.github.domdomegg/my-cool-mcp you must login to GitHub as domdomegg, or be in a GitHub Action on domdomegg's repos
  • me.adamjones/my-cool-mcp you must prove ownership of adamjones.me via DNS or HTTP challenge

Community Projects

Check out community projects to explore notable registry-related work created by the community.

More documentation

See the documentation for more details if your question has not been answered here!

來源：README.md，提交 1b822fe

工具

47

docs_fetch

Fetch a specific documentation page as markdown

輸入參數url必填

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.

輸入參數clilimitquery必填

rpc_lookup_method

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

輸入參數chainlimitquery必填

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

輸入參數limitquerynumber

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

輸入參數limittrackstatus

avalanche_docs_fetch

Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.

輸入參數url必填

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

輸入參數txHash必填network

blockchain_lookup_subnet

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

輸入參數networksubnetId必填

blockchain_lookup_chain

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

輸入參數chainId必填network

blockchain_lookup_validator

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

輸入參數nodeId必填networksubnetId

platform_get_height

Get the current P-Chain block height

輸入參數network

platform_get_block

Get a P-Chain block by its block ID

輸入參數blockID必填networkencoding

platform_get_block_by_height

Get a P-Chain block by its height

輸入參數height必填networkencoding

platform_get_blockchains

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

輸入參數limitoffsetnetwork

platform_get_subnets

Get information about Subnets/L1s on the P-Chain

輸入參數idslimitoffsetnetwork

platform_get_current_validators

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

輸入參數limitoffsetnetworknodeIDssubnetID

platform_get_pending_validators

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

輸入參數limitoffsetnetworknodeIDssubnetID

platform_get_staking_asset_id

Get the asset ID of the token used for staking on a Subnet/L1

輸入參數networksubnetID

platform_get_min_stake

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

輸入參數networksubnetID

platform_get_total_stake

Get the total amount staked on a Subnet/L1

輸入參數networksubnetID

platform_get_balance

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

輸入參數networkaddresses必填

platform_get_utxos

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

輸入參數limitnetworkaddresses必填sourceChain

platform_get_tx

Get a P-Chain transaction by its transaction ID

輸入參數txID必填networkencoding

platform_get_tx_status

Get the status of a P-Chain transaction

輸入參數txID必填network

platform_get_current_supply

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

輸入參數networksubnetID

platform_get_validators_at

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

輸入參數height必填networksubnetID

info_get_node_version

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

輸入參數network

info_get_network_id

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

輸入參數network

info_get_network_name

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

輸入參數network

info_get_blockchain_id

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

輸入參數alias必填network

info_is_bootstrapped

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

輸入參數chain必填network

info_get_tx_fee

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

輸入參數network

info_peers

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

輸入參數networknodeIDs

info_acps

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

輸入參數network

blockchain_get_native_balance

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

輸入參數address必填chainId

blockchain_get_contract_info

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

輸入參數address必填chainId

blockchain_lookup_address

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

輸入參數address必填chainId

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

輸入參數kindvalue必填chainIdincludenetworktokenId

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

輸入參數feedhoursscope必填valuechainIdnetworkpageSizetoTimestampblockchainIdfromTimestamp

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 has active senders (window=series, `days` max 365; timeInterval=hour max 90 days). target=network: current P-chain validator snapshot. There are no per-contract stats here; for those, run SQL in the Builder Hub explorer Query page. Note: C-Chain gasUsed is gas-target-regulated, so daily gas is about stable even as tx count varies. That is expected, not an error.

輸入參數dayshourstargetwindowchainIdnetworktimeInterval

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

輸入參數tovmnametypestaketokenamountnodeIdchainIdexamplenetworkduration另有 7 個

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, multisig, staking, transfers, interchain-kit-local.

輸入參數flow

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分