Skip to content

Avalanche AVAX MCP server

io.github.Airpote/avalanche-docsAirpotestreamable-httpv1.0.1Scanned

Search and retrieve Avalanche blockchain documentation for building on AVAX.

47 tools: 1 do something that can't be undone, 5 change things and 41 only read.

Tools: 0 delete, 1 irreversible, 5 write, 41 read.
  • Reads private data · 9
  • Reads text others write · 3
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Avalanche AVAX MCP server can do

The Avalanche AVAX MCP server is published by the GitHub account Airpote. It has 47 tools. It can do things that cannot be undone, such as sending, paying or publishing (build_plan) and create or change data (5 tools: info_is_bootstrapped, onchain_activity, chain_stats, console_link and 1 more), but cannot delete data. 41 tools only read.

9 tools read private data (docs_search, docs_fetch, docs_list_sections and 6 more); 3 tools bring in text other people can write (docs_search, docs_fetch and avalanche_docs_fetch); 3 tools can send data out of your system (docs_fetch, avalanche_docs_fetch and build_plan). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

47 tools

Can't be undone 1Claude Code: ask
  • build_planGenerate 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.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    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.
Changes things 5Claude Code: ask
  • chain_statsChain statistics from the Avalanche Stats API (pre-aggregated; closed periods only, so the current hour or day is not included).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • console_flowBuilder Console flow knowledge.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • info_is_bootstrappedCheck whether a given chain has finished bootstrapping on the node.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Check whether a given chain has finished bootstrapping on the node.
  • onchain_activityRecent on-chain activity.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 41Show 41 read-only tools
  • acp_listList Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices,…No findings

    Why it is in this group

    • The name "acp_list" says "list": a word for reading.
    Description, as the server wrote it
    List Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices, Meta, Subnet).
  • acp_lookupLook up Avalanche Community Proposals (ACPs) by number, title, or topic.No findings

    Why it is in this group

    • The name "acp_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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).
  • avalanche_docs_fetchCompatibility alias for docs_fetch.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "avalanche_docs_fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe name "avalanche_docs_fetch" says "fetch" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.
  • avalanche_docs_list_sectionsCompatibility alias for docs_list_sections.Reads private dataNo findings

    Why it is in this group

    • The name "avalanche_docs_list_sections" says "list": a word for reading.

    What it can reach

    • private-dataThe name "avalanche_docs_list_sections" says "list" and "doc": it reads documents.
    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.
  • blockchain_get_contract_infoCompatibility alias for onchain_lookup contract metadata.No findings

    Why it is in this group

    • The name "blockchain_get_contract_info" says "get": a word for reading.
    Description, as the server wrote it
    Compatibility alias for onchain_lookup contract metadata. Prefer onchain_lookup for new clients.
  • blockchain_get_native_balanceCompatibility alias for onchain_lookup address balances.No findings

    Why it is in this group

    • The name "blockchain_get_native_balance" says "get": a word for reading.
    Description, as the server wrote it
    Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients.
  • blockchain_lookup_addressCompatibility alias for onchain_lookup address details.No findings

    Why it is in this group

    • The name "blockchain_lookup_address" says "lookup": a word for reading.
    Description, as the server wrote it
    Compatibility alias for onchain_lookup address details. Prefer onchain_lookup for new clients.
  • blockchain_lookup_chainLook up a blockchain by its ID — name, VM type, and Subnet/L1.No findings

    Why it is in this group

    • The name "blockchain_lookup_chain" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up a blockchain by its ID — name, VM type, and Subnet/L1.
  • blockchain_lookup_subnetLook up a Subnet / L1 by its ID — validators, chains, and configuration.No findings

    Why it is in this group

    • The name "blockchain_lookup_subnet" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up a Subnet / L1 by its ID — validators, chains, and configuration.
  • blockchain_lookup_transactionLook up a transaction by hash on Avalanche (C-Chain, P-Chain, or X-Chain).No findings

    Why it is in this group

    • The name "blockchain_lookup_transaction" says "lookup": a word for reading.
    Description, as the server wrote it
    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_validatorLook up a validator by node ID — stake, uptime, delegation info.No findings

    Why it is in this group

    • The name "blockchain_lookup_validator" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up a validator by node ID — stake, uptime, delegation info.
  • cli_lookup_commandLook up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs.Reads private dataNo findings

    Why it is in this group

    • The name "cli_lookup_command" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    Look up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs. Returns cited command references and task docs.
  • docs_fetchFetch a specific documentation page as markdownReads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "docs_fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe name "docs_fetch" says "fetch" and "doc": it reads documents.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Fetch a specific documentation page as markdown
  • docs_list_sectionsList available documentation sections and their page countsReads private dataNo findings

    Why it is in this group

    • The name "docs_list_sections" says "list": a word for reading.

    What it can reach

    • private-dataThe name "docs_list_sections" says "list" and "doc": it reads documents.
    Description, as the server wrote it
    List available documentation sections and their page counts
  • info_acpsGet information about Avalanche Community Proposals (ACPs), including their status and vote counts.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get information about Avalanche Community Proposals (ACPs), including their status and vote counts.
  • info_get_blockchain_idGet the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C").No findings

    Why it is in this group

    • The name "info_get_blockchain_id" says "get": a word for reading.
    Description, as the server wrote it
    Get the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C").
  • info_get_network_idGet the numeric ID of the Avalanche network this node is participating in.No findings

    Why it is in this group

    • The name "info_get_network_id" says "get": a word for reading.
    Description, as the server wrote it
    Get the numeric ID of the Avalanche network this node is participating in.
  • info_get_network_nameGet the human-readable name of the Avalanche network this node is participating in.No findings

    Why it is in this group

    • The name "info_get_network_name" says "get": a word for reading.
    Description, as the server wrote it
    Get the human-readable name of the Avalanche network this node is participating in.
  • info_get_node_versionGet the version of the node, including the database version, git commit, and API compatibility info.Reads private dataNo findings

    Why it is in this group

    • The name "info_get_node_version" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "database": it reads databases.
    Description, as the server wrote it
    Get the version of the node, including the database version, git commit, and API compatibility info.
  • info_get_tx_feeGet the current transaction fees for the network, returned in both nAVAX and AVAX.No findings

    Why it is in this group

    • The name "info_get_tx_fee" says "get": a word for reading.
    Description, as the server wrote it
    Get the current transaction fees for the network, returned in both nAVAX and AVAX.
  • info_peersGet a list of peers this node is connected to.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get a list of peers this node is connected to. Optionally filter by specific NodeIDs.
  • onchain_lookupPRIMARY 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 + isCon…No findings

    Why it is in this group

    • The name "onchain_lookup" says "lookup": a word for reading.
    Description, as the server wrote it
    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.
  • platform_get_balanceGet the AVAX balance of one or more P-Chain addressesNo findings

    Why it is in this group

    • The name "platform_get_balance" says "get": a word for reading.
    Description, as the server wrote it
    Get the AVAX balance of one or more P-Chain addresses
  • platform_get_blockGet a P-Chain block by its block IDNo findings

    Why it is in this group

    • The name "platform_get_block" says "get": a word for reading.
    Description, as the server wrote it
    Get a P-Chain block by its block ID
  • platform_get_block_by_heightGet a P-Chain block by its heightNo findings

    Why it is in this group

    • The name "platform_get_block_by_height" says "get": a word for reading.
    Description, as the server wrote it
    Get a P-Chain block by its height
  • platform_get_blockchainsGet all blockchains that exist on the P-Chain (paginated; use limit/offset)No findings

    Why it is in this group

    • The name "platform_get_blockchains" says "get": a word for reading.
    Description, as the server wrote it
    Get all blockchains that exist on the P-Chain (paginated; use limit/offset)
  • platform_get_current_supplyGet the current total supply of AVAX on a Subnet/L1No findings

    Why it is in this group

    • The name "platform_get_current_supply" says "get": a word for reading.
    Description, as the server wrote it
    Get the current total supply of AVAX on a Subnet/L1
  • platform_get_current_validatorsGet the current validators of a Subnet/L1 (paginated; use limit/offset)No findings

    Why it is in this group

    • The name "platform_get_current_validators" says "get": a word for reading.
    Description, as the server wrote it
    Get the current validators of a Subnet/L1 (paginated; use limit/offset)
  • platform_get_heightGet the current P-Chain block heightNo findings

    Why it is in this group

    • The name "platform_get_height" says "get": a word for reading.
    Description, as the server wrote it
    Get the current P-Chain block height
  • platform_get_min_stakeGet the minimum staking amounts for validators and delegators on a Subnet/L1No findings

    Why it is in this group

    • The name "platform_get_min_stake" says "get": a word for reading.
    Description, as the server wrote it
    Get the minimum staking amounts for validators and delegators on a Subnet/L1
  • platform_get_pending_validatorsGet the pending validators of a Subnet/L1 (paginated; use limit/offset)No findings

    Why it is in this group

    • The name "platform_get_pending_validators" says "get": a word for reading.
    Description, as the server wrote it
    Get the pending validators of a Subnet/L1 (paginated; use limit/offset)
  • platform_get_staking_asset_idGet the asset ID of the token used for staking on a Subnet/L1No findings

    Why it is in this group

    • The name "platform_get_staking_asset_id" says "get": a word for reading.
    Description, as the server wrote it
    Get the asset ID of the token used for staking on a Subnet/L1
  • platform_get_subnetsGet information about Subnets/L1s on the P-ChainNo findings

    Why it is in this group

    • The name "platform_get_subnets" says "get": a word for reading.
    Description, as the server wrote it
    Get information about Subnets/L1s on the P-Chain
  • platform_get_total_stakeGet the total amount staked on a Subnet/L1No findings

    Why it is in this group

    • The name "platform_get_total_stake" says "get": a word for reading.
    Description, as the server wrote it
    Get the total amount staked on a Subnet/L1
  • platform_get_txGet a P-Chain transaction by its transaction IDNo findings

    Why it is in this group

    • The name "platform_get_tx" says "get": a word for reading.
    Description, as the server wrote it
    Get a P-Chain transaction by its transaction ID
  • platform_get_tx_statusGet the status of a P-Chain transactionNo findings

    Why it is in this group

    • The name "platform_get_tx_status" says "get": a word for reading.
    Description, as the server wrote it
    Get the status of a P-Chain transaction
  • platform_get_utxosGet UTXOs that reference a given set of P-Chain addressesNo findings

    Why it is in this group

    • The name "platform_get_utxos" says "get": a word for reading.
    Description, as the server wrote it
    Get UTXOs that reference a given set of P-Chain addresses
  • platform_get_validators_atGet the validators and their weights of a Subnet/L1 at a given P-Chain heightNo findings

    Why it is in this group

    • The name "platform_get_validators_at" says "get": a word for reading.
    Description, as the server wrote it
    Get the validators and their weights of a Subnet/L1 at a given P-Chain height
  • rpc_lookup_methodLook up Avalanche RPC methods and API guides across C-Chain, P-Chain, X-Chain, Subnet-EVM, and node RPC docs.Reads private dataNo findings

    Why it is in this group

    • The name "rpc_lookup_method" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "doc": it reads documents.
    Description, as the server wrote it
    Look up Avalanche RPC methods and API guides across C-Chain, P-Chain, X-Chain, Subnet-EVM, and node RPC docs.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

81 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 3 outbound tools breaks every one.

Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__avalanche-docs__avalanche_docs_fetch",
      "mcp__avalanche-docs__build_plan",
      "mcp__avalanche-docs__docs_fetch"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:56 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2024-11-05
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://build.avax.network/api/mcp: tools/list returned 47 tools to an anonymous client, including build_plan (irreversible), info_is_bootstrapped (write), onchain_activity (write), chain_stats (write), console_link (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 removed, 2 changed.−1 removed~2 changedView diff
    • Removed:onchain_query
    • Changed:chain_statsChanges thingsdescriptioninputSchema
    • Changed:onchain_activityChanges thingsdescriptioninputSchema

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__avalanche-docs__docs_search",
      "mcp__avalanche-docs__docs_list_sections",
      "mcp__avalanche-docs__cli_lookup_command",
      "mcp__avalanche-docs__rpc_lookup_method",
      "mcp__avalanche-docs__acp_lookup",
      "mcp__avalanche-docs__acp_list",
      "mcp__avalanche-docs__avalanche_docs_search",
      "mcp__avalanche-docs__avalanche_docs_list_sections",
      "mcp__avalanche-docs__blockchain_lookup_transaction",
      "mcp__avalanche-docs__blockchain_lookup_subnet",
      "mcp__avalanche-docs__blockchain_lookup_chain",
      "mcp__avalanche-docs__blockchain_lookup_validator",
      "mcp__avalanche-docs__platform_get_height",
      "mcp__avalanche-docs__platform_get_block",
      "mcp__avalanche-docs__platform_get_block_by_height",
      "mcp__avalanche-docs__platform_get_blockchains",
      "mcp__avalanche-docs__platform_get_subnets",
      "mcp__avalanche-docs__platform_get_current_validators",
      "mcp__avalanche-docs__platform_get_pending_validators",
      "mcp__avalanche-docs__platform_get_staking_asset_id",
      "mcp__avalanche-docs__platform_get_min_stake",
      "mcp__avalanche-docs__platform_get_total_stake",
      "mcp__avalanche-docs__platform_get_balance",
      "mcp__avalanche-docs__platform_get_utxos",
      "mcp__avalanche-docs__platform_get_tx",
      "mcp__avalanche-docs__platform_get_tx_status",
      "mcp__avalanche-docs__platform_get_current_supply",
      "mcp__avalanche-docs__platform_get_validators_at",
      "mcp__avalanche-docs__info_get_node_version",
      "mcp__avalanche-docs__info_get_network_id",
      "mcp__avalanche-docs__info_get_network_name",
      "mcp__avalanche-docs__info_get_blockchain_id",
      "mcp__avalanche-docs__info_get_tx_fee",
      "mcp__avalanche-docs__info_peers",
      "mcp__avalanche-docs__info_acps",
      "mcp__avalanche-docs__blockchain_get_native_balance",
      "mcp__avalanche-docs__blockchain_get_contract_info",
      "mcp__avalanche-docs__blockchain_lookup_address",
      "mcp__avalanche-docs__onchain_lookup"
    ],
    "ask": [
      "mcp__avalanche-docs__docs_fetch",
      "mcp__avalanche-docs__avalanche_docs_fetch",
      "mcp__avalanche-docs__info_is_bootstrapped",
      "mcp__avalanche-docs__onchain_activity",
      "mcp__avalanche-docs__chain_stats",
      "mcp__avalanche-docs__build_plan",
      "mcp__avalanche-docs__console_link",
      "mcp__avalanche-docs__console_flow"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as avalanche-docs. Review it before you use it.

Capability tags behind 10 rules
  • mcp__avalanche-docs__docs_search private-data, untrusted-input
  • mcp__avalanche-docs__docs_fetch private-data, untrusted-input, outbound
  • mcp__avalanche-docs__docs_list_sections private-data
  • mcp__avalanche-docs__cli_lookup_command private-data
  • mcp__avalanche-docs__rpc_lookup_method private-data
  • mcp__avalanche-docs__avalanche_docs_search private-data
  • mcp__avalanche-docs__avalanche_docs_fetch private-data, untrusted-input, outbound
  • mcp__avalanche-docs__avalanche_docs_list_sections private-data
  • mcp__avalanche-docs__info_get_node_version private-data
  • mcp__avalanche-docs__build_plan outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Airpote/avalanche-docs/verify?hash=d2c0d1662c59174e84e879dafccef789430059cfb3842ab7efe8690f7d041510" | jq -e '.changed == false'

Pinned hash d2c0d1662c59, from Nov 15, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Airpote/avalanche-docs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Airpote/avalanche-docs
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Airpote/avalanche-docs.svg)](https://radar.anlyon.com/servers/io.github.Airpote/avalanche-docs)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.

Avalanche AVAX MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Avalanche AVAX MCP server safe?

No scan can promise that. What its definitions show: 47 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Avalanche AVAX MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Avalanche AVAX MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: build_plan.

What tools does the Avalanche AVAX MCP server have?

47 tools: 1 irreversible, 5 write, 41 read. build_plan, info_is_bootstrapped, onchain_activity, chain_stats, console_link, console_flow, docs_search, docs_fetch and 39 more.

Does the Avalanche AVAX MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Avalanche AVAX MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): docs_fetch, avalanche_docs_fetch and build_plan.

Has the Avalanche AVAX MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.