Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Avalanche AVAX is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search and retrieve Avalanche blockchain documentation for building on AVAX.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http avalanche-avax-mcp https://build.avax.network/api/mcp
# 2 — ask your agent for something these tools do
# docs_search, docs_fetch, docs_list_sections and 45 more
Avalanche AVAX costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http avalanche-avax-mcp https://build.avax.network/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
48 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search body-level chunks across Avalanche documentation, academy courses, integrations, and blog posts. Returns source citations and matching excerpts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The search query |
| source | string | no | Filter by documentation source (optional) |
| limit | number | no | Maximum number of chunk results (default: 10) |
Fetch a specific documentation page as markdown
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page URL path (e.g., /docs/primary-network/overview) |
List available documentation sections and their page counts
No parameter schema on file.
Look up Avalanche CLI, Platform CLI, and tmpnet command guidance in the docs. Returns cited command references and task docs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Command, flag, or task to look up |
| cli | string | no | CLI surface to search. Defaults to all. |
| limit | number | no | Maximum number of results (default: 8) |
Look up Avalanche RPC methods and API guides across C-Chain, P-Chain, X-Chain, Subnet-EVM, and node RPC docs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | RPC method, namespace, or task to look up |
| chain | string | no | RPC area to search. Defaults to all. |
| limit | number | no | Maximum number of results (default: 8) |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | ACP title, topic, or keyword |
| number | number | no | ACP number, if known |
| limit | number | no | Maximum number of results (default: 8) |
List Avalanche Community Proposals with structured fields, optionally filtered by status (Activated, Implementable, Proposed, Stale, Withdrawn) or track (Standards, Best Practices, Meta, Subnet).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by ACP status (case-insensitive) |
| track | string | no | Filter by ACP track. Matches Standards, Best Practices, Meta, or Subnet. |
| limit | number | no | Maximum number of ACPs to return (default: 50) |
Compatibility alias for docs_search. Prefer docs_search for new clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The search query |
| source | string | no | Filter by documentation source (optional) |
| limit | number | no | Maximum number of chunk results (default: 10) |
Compatibility alias for docs_fetch. Prefer docs_fetch for new clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The page URL path (e.g., /docs/primary-network/overview) |
Compatibility alias for docs_list_sections. Prefer docs_list_sections for new clients.
No parameter schema on file.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| txHash | string | yes | Transaction hash (0x... for C-Chain, CB58 for P/X-Chain) |
| network | string | no | Network to search |
Look up a Subnet / L1 by its ID — validators, chains, and configuration.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetId | string | yes | The Subnet ID |
| network | string | no | — |
Look up a blockchain by its ID — name, VM type, and Subnet/L1.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chainId | string | yes | The blockchain ID |
| network | string | no | — |
Look up a validator by node ID — stake, uptime, delegation info.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nodeId | string | yes | Node ID (e.g. NodeID-...) |
| subnetId | string | no | Subnet ID (default: Primary Network) |
| network | string | no | — |
Get the current P-Chain block height
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Avalanche network to query (default: mainnet) |
Get a P-Chain block by its block ID
| Parameter | Type | Required | Notes |
|---|---|---|---|
| blockID | string | yes | The CB58-encoded block ID |
| encoding | string | no | Encoding format for the block (default: json) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get a P-Chain block by its height
| Parameter | Type | Required | Notes |
|---|---|---|---|
| height | string | yes | The block height as a string |
| encoding | string | no | Encoding format for the block (default: json) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get all blockchains that exist on the P-Chain (paginated; use limit/offset)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | Avalanche network to query (default: mainnet) |
| limit | number | no | Max items to return (default: 50). Use with "offset" to page. |
| offset | number | no | Number of items to skip from the start (default: 0). |
Get information about Subnets/L1s on the P-Chain
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | no | Optional list of Subnet IDs to filter by |
| network | string | no | Avalanche network to query (default: mainnet) |
| limit | number | no | Max items to return (default: 50). Use with "offset" to page. |
| offset | number | no | Number of items to skip from the start (default: 0). |
Get the current validators of a Subnet/L1 (paginated; use limit/offset)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetID | string | no | The Subnet ID to query validators for (default: Primary Network) |
| nodeIDs | array | no | Optional list of node IDs to filter by |
| network | string | no | Avalanche network to query (default: mainnet) |
| limit | number | no | Max items to return (default: 50). Use with "offset" to page. |
| offset | number | no | Number of items to skip from the start (default: 0). |
Get the pending validators of a Subnet/L1 (paginated; use limit/offset)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetID | string | no | The Subnet ID to query pending validators for (default: Primary Network) |
| nodeIDs | array | no | Optional list of node IDs to filter by |
| network | string | no | Avalanche network to query (default: mainnet) |
| limit | number | no | Max items to return (default: 50). Use with "offset" to page. |
| offset | number | no | Number of items to skip from the start (default: 0). |
Get the asset ID of the token used for staking on a Subnet/L1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetID | string | no | The Subnet ID to query the staking asset for (default: Primary Network) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the minimum staking amounts for validators and delegators on a Subnet/L1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetID | string | no | The Subnet ID to query minimum stake for (default: Primary Network) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the total amount staked on a Subnet/L1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetID | string | no | The Subnet ID to query total stake for (default: Primary Network) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the AVAX balance of one or more P-Chain addresses
| Parameter | Type | Required | Notes |
|---|---|---|---|
| addresses | array | yes | List of P-Chain addresses to query (e.g. P-avax1...) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get UTXOs that reference a given set of P-Chain addresses
| Parameter | Type | Required | Notes |
|---|---|---|---|
| addresses | array | yes | List of P-Chain addresses to get UTXOs for |
| limit | number | no | Maximum number of UTXOs to return |
| sourceChain | string | no | If fetching atomic UTXOs, the chain they were exported from |
| network | string | no | Avalanche network to query (default: mainnet) |
Get a P-Chain transaction by its transaction ID
| Parameter | Type | Required | Notes |
|---|---|---|---|
| txID | string | yes | The CB58-encoded transaction ID |
| encoding | string | no | Encoding format for the transaction (default: json) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the status of a P-Chain transaction
| Parameter | Type | Required | Notes |
|---|---|---|---|
| txID | string | yes | The CB58-encoded transaction ID |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the current total supply of AVAX on a Subnet/L1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subnetID | string | no | The Subnet ID to query current supply for (default: Primary Network) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the validators and their weights of a Subnet/L1 at a given P-Chain height
| Parameter | Type | Required | Notes |
|---|---|---|---|
| height | yes | The P-Chain height to query validators at, or "proposed" | |
| subnetID | string | no | The Subnet ID to query validators for (default: Primary Network) |
| network | string | no | Avalanche network to query (default: mainnet) |
Get the version of the node, including the database version, git commit, and API compatibility info.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | The Avalanche network to query (default: mainnet) |
Get the numeric ID of the Avalanche network this node is participating in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | The Avalanche network to query (default: mainnet) |
Get the human-readable name of the Avalanche network this node is participating in.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | The Avalanche network to query (default: mainnet) |
Get the CB58-encoded blockchain ID for a given blockchain alias (e.g., "X", "P", "C").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| alias | string | yes | The blockchain alias (e.g., "X", "P", "C", or a full blockchain name) |
| network | string | no | The Avalanche network to query (default: mainnet) |
Check whether a given chain has finished bootstrapping on the node.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | yes | The chain ID or alias to check (e.g., "X", "P", "C") |
| network | string | no | The Avalanche network to query (default: mainnet) |
Get the current transaction fees for the network, returned in both nAVAX and AVAX.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | The Avalanche network to query (default: mainnet) |
Get a list of peers this node is connected to. Optionally filter by specific NodeIDs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| nodeIDs | array | no | Optional list of NodeIDs to filter peers by (e.g., ["NodeID-AbC..."]). If omitted, all peers are returned. |
| network | string | no | The Avalanche network to query (default: mainnet) |
Get information about Avalanche Community Proposals (ACPs), including their status and vote counts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| network | string | no | The Avalanche network to query (default: mainnet) |
Compatibility alias for onchain_lookup address balances. Prefer onchain_lookup for new clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM address (0x...) |
| chainId | string | no | 43114 for C-Chain mainnet, 43113 for Fuji |
Compatibility alias for onchain_lookup contract metadata. Prefer onchain_lookup for new clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Contract address (0x...) |
| chainId | string | no | 43114 for C-Chain mainnet, 43113 for Fuji |
Compatibility alias for onchain_lookup address details. Prefer onchain_lookup for new clients.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM address (0x...) |
| chainId | string | no | 43114 for C-Chain mainnet, 43113 for Fuji |
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 th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | The identifier: 0x address / 0x tx hash / NodeID-… / subnetId / chain name or id |
| kind | string | no | Entity kind (default: auto-detect from value) |
| network | string | no | Network (default: mainnet) |
| chainId | string | no | EVM chain ID for EVM kinds (default: C-Chain for the network) |
| tokenId | string | no | NFT token ID (kind=nft) |
| include | array | no | Extra data for an address (e.g. ["nfts"]) |
Time-windowed on-chain activity. scope=chain/address returns the transaction COUNT over the last hours (max 720h = 30 days; for longer windows use chain_stats series or onchain_query day-based ops) plus a recent sample. 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 work
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope | string | yes | address | chain | token | contract | primary |
| value | string | no | Address/contract/token (omit for scope=chain) |
| feed | string | no | transactions (default) | transfers | erc20Transfers | nftTransfers |
| network | string | no | Network (default: mainnet) |
| chainId | string | no | EVM chain ID (default: C-Chain for the network) |
| blockchainId | string | no | Blockchain ID for scope=primary (default: P-Chain) |
| hours | number | no | Look-back window in hours for EVM transaction feeds (default: 2 for chain, max 720) |
| fromTimestamp | number | no | Unix start time (scope=primary) |
| toTimestamp | number | no | Unix end time (scope=primary) |
| pageSize | number | no | Max rows (default: 25) |
On-chain statistics via the query gateway, which picks the most accurate live source PER FIELD and stamps it (sources/warnings in the response). target=chain: tx count/gas/fees/active senders/avg gas price over a recent window (window=recent, hours, max 720h = 30 days) OR a time-series (window=series, days, max 365). target=contract: per-contract tx/sender/gas totals (days, max 365 — use thi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | no | chain (default) | contract | network |
| window | string | no | chain: recent aggregate (default) or series |
| chainId | string | no | EVM chain ID (default: C-Chain for the network) |
| value | string | no | Contract address (target=contract) |
| timeInterval | string | no | Bucket size for window=series (default: day) |
| hours | number | no | Look-back hours for window=recent (default: 24, max 720) |
| days | number | no | Look-back days for series / contract (default: 30, max 365) |
| network | string | no | Network (default: mainnet) |
PRIMARY tool for indexed on-chain stats/activity/totals — prefer this over raw RPC for chain data. Each op is a backend-agnostic intent: the query gateway selects the most accurate live source per field (indexed DB / pre-aggregated metrics / Data API), stamps every field (sources), and flags any caveat (warnings) — relay warnings to the user, never present a flagged value as exact. Pick an `
| Parameter | Type | Required | Notes |
|---|---|---|---|
| op | string | yes | The query operation |
| params | object | yes | Op-specific parameters (see description); validated server-side. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | Which runbook to generate |
| network | string | no | Target network (default: fuji) |
| name | string | no | create-l1: L1 name (default: myL1) |
| vm | string | no | create-l1: VM type (default: subnet-evm) |
| validatorManager | string | no | create-l1 / validator-manager: model (default: poa) |
| chainId | string | no | create-l1: EVM chain ID |
| tokenSymbol | string | no | create-l1: native token symbol |
| type | string | no | validator-manager: manager type (alias of validatorManager) |
| token | string | no | ictt: token contract address (or "native") |
| tokenType | string | no | ictt: token type (default: erc20) |
| homeChain | string | no | ictt: home chain (where the token originates) |
| remoteChain | string | no | ictt: destination chain (required for operation=ictt) |
| stake | string | no | staking: stake amount |
| duration | string | no | staking: staking period (e.g. 336h) |
| nodeId | string | no | staking: NodeID-… |
| transferKind | string | no | transfer: kind (default: send) |
| amount | string | no | transfer: amount |
| to | string | no | transfer: destination address (transferKind=send) |
| example | string | no | interchain-kit: which example to run |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow | string | yes | The console flow to link to |
| network | string | no | Network (only affects faucet; default: fuji) |
| validatorManager | string | no | Validator-manager variant (default: poa) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flow | string | no | Flow key to explain. Omit to list all flows. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Avalanche AVAX or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Avalanche AVAX can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.