dev.avakit/avalanche
NPM · @AVAKIT/MCP
Act on Avalanche from your agent: scaffold a dapp, deploy a contract, mint, and read chain state.
Available components
Last scanned (9 hours ago)
Scores higher than 83% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 48 of 162 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 107 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +6
- Source repository: unverified → pass ▲ security
- 5 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 4 Nov 26 −3
- Stability: pass → 0.77 functional
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
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 7 Nov 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 | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bc085f6d60927044bdf19d7c9d9df3e76e45e8ef2cc4ac41f782e71aa41527013b6325967921b2b7f829f85ab60e899f03abdccbdf7551dc8c2468eaa |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 10 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-gcqx-w48m-w2h4 | CVE-2026-93753 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | no |
| 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 |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | 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 162 packages
| Packages resolved | 162 |
|---|---|
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
deploy_contract Deploy a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | array | yes | – |
| args | array | – | – |
| bytecode | string | yes | Creation bytecode (0x-prefixed) |
| chain | string | – | – |
| confirm | boolean | – | Required to deploy to mainnet |
No output schema declared.
No examples provided.
estimate_gas 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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| data | string | – | Calldata (0x…) |
| from | string | – | Sender address (0x…) |
| to | string | yes | Recipient / contract address (0x…) |
| value | string | – | Native value in wei (decimal string) |
No output schema declared.
No examples provided.
get_context Get AvaKit context ~37
Return AvaKit + Avalanche context for coding: the API surface, conventions, and doc links.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional focus topic |
No output schema declared.
No examples provided.
list_templates 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 Read Avalanche chain data ~100
Read a native AVAX balance, a transaction receipt, or a contract view/pure function over RPC.
| Name | Type | Req | Description |
|---|---|---|---|
| abi | array | – | Contract ABI for contractRead |
| action | string | yes | – |
| address | string | – | Address for balance / contractRead |
| args | array | – | – |
| chain | string | – | – |
| functionName | string | – | View function for contractRead |
| hash | string | – | Tx hash for txReceipt |
No output schema declared.
No examples provided.
scaffold_app Scaffold an Avalanche dapp ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| directory | string | – | Parent directory (default: cwd) |
| local | boolean | – | Link @avakit/* via workspace (repo dev only) |
| name | string | yes | Project directory name, e.g. my-avax-app |
| template | string | – | – |
| wallet | string | – | – |
No output schema declared.
No examples provided.
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
claude mcp add dev-avakit-avalanche -- npx -y @avakit/mcp
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 85 out of 100 on VerifyMCP. We recorded 10 known advisories against it as of 7 November 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 7 November 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.
What did VerifyMCP test on the dev.avakit/avalanche MCP server?
VerifyMCP ran 16 checks on dev.avakit/avalanche, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.