Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.avakit/avalanche

NPM · @AVAKIT/MCP · SCANNED SEP 21

Act on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain state.

Available components

npm · @avakit/mcp 87
−1 this week 87 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security90
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects ws 8.20.1, reached via viem > ws. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 48 of 157 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to mericcintosun/AvaKit). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 60 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 495 tokens (~82/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy_contract" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the dev.avakit/avalanche MCP server?

dev.avakit/avalanche runs locally as an npm package, launched with npx -y @avakit/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @avakit/mcp

# add to Claude Code
claude mcp add dev-avakit-avalanche -- npx -y @avakit/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-avakit-avalanche": {
      "command": "npx",
      "args": [
        "-y",
        "@avakit/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-avakit-avalanche": {
      "command": "npx",
      "args": [
        "-y",
        "@avakit/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dev-avakit-avalanche -- npx -y @avakit/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-avakit-avalanche": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@avakit/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-avakit-avalanche --command npx --arg -y --arg @avakit/mcp
# ~/.hermes/config.yaml
mcp_servers:
  dev-avakit-avalanche:
    command: "npx"
    args: ["-y", "@avakit/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-avakit-avalanche": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@avakit/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-avakit-avalanche -t stdio -c npx -a -y @avakit/mcp
// mcp.json
{
  "mcpServers": {
    "dev-avakit-avalanche": {
      "command": "npx",
      "args": [
        "-y",
        "@avakit/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/@avakit/mcp@0.1.25

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo mericcintosun/AvaKit
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mericcintosun/AvaKit/.github/workflows/release.yml@refs/heads/main
Rekor log index 2171733280
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:bc085f6d60927044bdf19d7c9d9df3e76e45e8ef2cc4ac41f782e71aa41527013b6325967921b2b7f829f85ab60e899f03abdccbdf7551dc8c2468eaa

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-96hv-2xvq-fx4p CVE-2026-48779 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 157 packages
Packages resolved 157
Stale 48
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~495 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
deploy_contract ~97

Deploy compiled bytecode to Avalanche using a deployer key from the AVAKIT_DEPLOYER_KEY env var. Fuji testnet by default; mainnet (c-chain) requires confirm:true.

NameTypeReqDescription
abiarrayyes–
argsarray––
bytecodestringyesCreation bytecode (0x-prefixed)
chainstring––
confirmboolean–Required to deploy to mainnet

No output schema declared.

No examples provided.

estimate_gas ~104

Estimate the gas a transaction (to / data / value) would use and report the current gas price and rough AVAX cost, over RPC. No key needed.

NameTypeReqDescription
chainstring––
datastring–Calldata (0x…)
fromstring–Sender address (0x…)
tostringyesRecipient / contract address (0x…)
valuestring–Native value in wei (decimal string)

No output schema declared.

No examples provided.

get_context ~37

Return AvaKit + Avalanche context for coding: the API surface, conventions, and doc links.

NameTypeReqDescription
topicstring–Optional focus topic

No output schema declared.

No examples provided.

list_templates ~19

List the Avalanche dapp templates available to scaffold_app.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_chain ~100

Read a native AVAX balance, a transaction receipt, or a contract view/pure function over RPC.

NameTypeReqDescription
abiarray–Contract ABI for contractRead
actionstringyes–
addressstring–Address for balance / contractRead
argsarray––
chainstring––
functionNamestring–View function for contractRead
hashstring–Tx hash for txReceipt

No output schema declared.

No examples provided.

scaffold_app ~138

Create a new Avalanche dapp from a template (minimal, nft-mint, token-gated-app, erc20-token, icm-messenger, eerc-token, l1-launch, token-bridge). Wraps create-avalanche-app. Returns the created files and next steps.

NameTypeReqDescription
chainstring––
directorystring–Parent directory (default: cwd)
localboolean–Link @avakit/* via workspace (repo dev only)
namestringyesProject directory name, e.g. my-avax-app
templatestring––
walletstring––

No output schema declared.

No examples provided.

Common questions

What is the dev.avakit/avalanche MCP server?

dev.avakit/avalanche is an MCP server listed in the public MCP registry as dev.avakit/avalanche. Act on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain state. This page covers its npm package (@avakit/mcp).

Is the dev.avakit/avalanche MCP server safe to use?

dev.avakit/avalanche scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the dev.avakit/avalanche MCP server expose?

dev.avakit/avalanche exposes 6 tools: list_templates, scaffold_app, read_chain, estimate_gas, deploy_contract, get_context. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.

Is the dev.avakit/avalanche MCP server still maintained?

dev.avakit/avalanche is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the dev.avakit/avalanche MCP server under?

dev.avakit/avalanche declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.