Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Avalanche AVAX MCP

by Airpoteversion 1.0.1i★ 0iRuns in the cloud
Registry nameio.github.Airpote/avalanche-docs

Install

Overview

Description from the maker (original English)

Search and retrieve Avalanche blockchain documentation for building on AVAX.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Crypto & blockchain

Install

Pick the AI app you use, then copy the settings.

Before you install

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3Connect4
https://build.avax.network/api/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3Connect4
https://build.avax.network/api/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

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

All apps, with pros and cons →

What it can do

Tool names and descriptions exactly as the server reported them on Nov 10, 2026. The maker wrote them, not us; we show them as plain text.

  • 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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Airpote, which owns the repo

  • ! Caution

    Still maintained

    Code last changed 9 months ago, more than 6 months ago

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 53 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 47 tool descriptions and found no hidden instructions to the AI

Compared with others in Crypto & blockchaini

  • More stars than 0% of the other 1635 servers in this category
  • Published to the registry more recently than 2% of the other 1635 servers in this category
  • Basic checks equal to or better than 52% of the other 1635 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Avalanche AVAX MCP safe?

It passed 3 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 9 months ago, and the latest version (1.0.1) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Solana MCP by Vybe, Solana MCP by Vybe, Oracle3 prediction-market arbitrage checks

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Solana MCP by Vybe

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

by vybenetworkWidely used★ 2.6KUpdated 6 months ago

Runs in the cloud

Solana MCP by Vybe

Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools.

by vybenetworkWidely used★ 2.6KUpdated 7 months ago

Runs in the cloud

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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](./docs)

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](https://modelcontextprotocol.io/community/communication) - Real-time community discussions
  • [Discussions](https://github.com/modelcontextprotocol/registry/discussions) - Propose and discuss product/technical requirements
  • [Issues](https://github.com/modelcontextprotocol/registry/issues) - Track well-scoped technical work
  • [Pull Requests](https://github.com/modelcontextprotocol/registry/pulls) - Contribute work towards issues
Quick start:
Pre-requisites
Running the server
# Start full development environment

make 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:

# Run latest stable release

docker 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 version

docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0

Run development build from main branch

docker 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- - (specific commit builds)
Publishing a server

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

# Build the latest CLI

make publisher

Use it!

./bin/mcp-publisher --help

See the publisher guide for more details.

Other commands
# Run lint, unit tests and integration tests

make 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!