Avalanche AVAX MCP

io.github.AirpotePublished by GitHub account Airpotev1.0.1Updated Oct 24, 2026

Search and retrieve Avalanche blockchain documentation for building on AVAX.

VerifiedStreamable HTTPWeb executableFinanceKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Remote MCP server that lets an assistant search Avalanche documentation and ACP proposals and look up on-chain transactions, Subnets, validators and P-Chain stA

What you can do
Search and read Avalanche documentation pages, and list documentation sections with page counts. Look up Avalanche CLI, Platform CLI and tmpnet command guidance, plus C/P/X-Chain, Subnet-EVM and node RPC methods. Look up ACP proposals by number, title or topic, and list proposals filtered by status or track. Look up transactions by hash, and Subnets/L1s, blockchains and validators by ID. Query P-Chain block height, blocks, Subnets, validators, staking amounts, balances, UTXOs and transaction status. Query node version, network ID and name, blockchain ID, bootstrapping status, transaction fees and peers.
When to use it
Useful when you need Avalanche documentation, ACP proposals, CLI command or RPC method guidance, or want to inspect on-chain transactions, Subnets, validators and P-Chain staking data directly.
Requirements
Network access to the remote endpoint at build.avax.network; no accounts, API keys or environment variables are declared.
Before you install
Several tools query public on-chain data (transactions, address balances, validators, node peers), and those lookups go to a third-party endpoint. The listed tools are read-only lookups; no writing, sending or deleting of data is shown.

Installation

In SourceWeft

  1. Open Avalanche AVAX MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Airpote%2Favalanche-docs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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!

Source: README.md at commit 1b822fe

Tools

47

docs_fetch

Fetch a specific documentation page as markdown

Parametersurlrequired

docs_list_sections

List available documentation sections and their page counts

Takes no parameters.

cli_lookup_command

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

Parametersclilimitqueryrequired

rpc_lookup_method

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

Parameterschainlimitqueryrequired

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

Parameterslimitquerynumber

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

Parameterslimittrackstatus

avalanche_docs_fetch

Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.

Parametersurlrequired

avalanche_docs_list_sections

Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.

Takes no parameters.

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

ParameterstxHashrequirednetwork

blockchain_lookup_subnet

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

ParametersnetworksubnetIdrequired

blockchain_lookup_chain

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

ParameterschainIdrequirednetwork

blockchain_lookup_validator

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

ParametersnodeIdrequirednetworksubnetId

platform_get_height

Get the current P-Chain block height

Parametersnetwork

platform_get_block

Get a P-Chain block by its block ID

ParametersblockIDrequirednetworkencoding

platform_get_block_by_height

Get a P-Chain block by its height

Parametersheightrequirednetworkencoding

platform_get_blockchains

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

Parameterslimitoffsetnetwork

platform_get_subnets

Get information about Subnets/L1s on the P-Chain

Parametersidslimitoffsetnetwork

platform_get_current_validators

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

ParameterslimitoffsetnetworknodeIDssubnetID

platform_get_pending_validators

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

ParameterslimitoffsetnetworknodeIDssubnetID

platform_get_staking_asset_id

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

ParametersnetworksubnetID

platform_get_min_stake

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

ParametersnetworksubnetID

platform_get_total_stake

Get the total amount staked on a Subnet/L1

ParametersnetworksubnetID

platform_get_balance

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

Parametersnetworkaddressesrequired

platform_get_utxos

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

ParameterslimitnetworkaddressesrequiredsourceChain

platform_get_tx

Get a P-Chain transaction by its transaction ID

ParameterstxIDrequirednetworkencoding

platform_get_tx_status

Get the status of a P-Chain transaction

ParameterstxIDrequirednetwork

platform_get_current_supply

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

ParametersnetworksubnetID

platform_get_validators_at

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

ParametersheightrequirednetworksubnetID

info_get_node_version

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

Parametersnetwork

info_get_network_id

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

Parametersnetwork

info_get_network_name

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

Parametersnetwork

info_get_blockchain_id

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

Parametersaliasrequirednetwork

info_is_bootstrapped

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

Parameterschainrequirednetwork

info_get_tx_fee

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

Parametersnetwork

info_peers

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

ParametersnetworknodeIDs

info_acps

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

Parametersnetwork

blockchain_get_native_balance

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

ParametersaddressrequiredchainId

blockchain_get_contract_info

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

ParametersaddressrequiredchainId

blockchain_lookup_address

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

ParametersaddressrequiredchainId

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.

ParameterskindvaluerequiredchainIdincludenetworktokenId

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.

ParametersfeedhoursscoperequiredvaluechainIdnetworkpageSizetoTimestampblockchainIdfromTimestamp

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.

ParametersdayshourstargetwindowchainIdnetworktimeInterval

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.

ParameterstovmnametypestaketokenamountnodeIdchainIdexamplenetworkduration+7 more

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.

Parametersflow

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts