Ashfields MCP Server
NPM · ASHFIELDS-MCP-SERVER
Burn $ASH to mint on-chain NFTs on Ethereum. No browser. Two agent tool calls.
Available components
Last scanned (3 hours ago)
Scores higher than 72% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 219 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 356 tokens (~71/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −5
- Stability: pass → 0.67 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
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 5 Nov 2026 · Analysed npm/ashfields-mcp-server@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 108 packages
| Packages resolved | 108 |
|---|---|
| Stale | 30 |
| 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 →
approve_ash ~77
Approves the Ashfields contract to spend $ASH tokens from the configured wallet. Submits the approval transaction and waits for on-chain confirmation. Required before minting if the current allowance is insufficient.
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | number | yes | Number of tokens to approve spend for (1–5). Approves quantity × 100,000 ASH. |
No output schema declared.
No examples provided.
check_wallet ~51
Returns the configured wallet address, its $ASH token balance, its current $ASH allowance for the Ashfields contract, and its ETH balance for gas. Also reports the maximum number of tokens it can mint right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mint_info ~54
Returns current Ashfields mint status: price per token, total minted so far, remaining supply, whether minting is currently active, and contract addresses. Call this first to confirm minting is open before attempting a mint.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mint_ashfield ~91
Mints one or more Ashfields NFTs. Automatically approves $ASH if the current allowance is insufficient, then submits the mint transaction and waits for confirmation. Returns the minted token IDs and OpenSea links. Burns 100,000 $ASH per token permanently (sent to 0xdead).
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | number | yes | Number of tokens to mint. Must be between 1 and 5 per transaction. |
No output schema declared.
No examples provided.
trigger_distribute ~83
Calls distribute() on the RoyaltyDistributor contract. Permissionless — any wallet can trigger this at any time. Splits accumulated royalty ETH: 1% to creator, 1% to $ASH team, 8% buys $ASH on Uniswap and burns it to 0xdead. Requires at least 0.005 ETH in the distributor to execute.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Ashfields MCP Server server?
Ashfields MCP Server runs locally as an npm package, launched with npx -y ashfields-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · ashfields-mcp-server
claude mcp add smoke711711-ashfields-mcp-server -- npx -y ashfields-mcp-server
What is the Ashfields MCP Server server?
Ashfields MCP Server is listed in the public MCP registry as io.github.smoke711711/ashfields-mcp-server. Burn $ASH to mint on-chain NFTs on Ethereum. No browser. Two agent tool calls. This page covers its npm package (ashfields-mcp-server).
Is the Ashfields MCP Server server safe to use?
Ashfields MCP Server scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Ashfields MCP Server server expose?
Ashfields MCP Server exposes 5 tools: get_mint_info, check_wallet, approve_ash, mint_ashfield, trigger_distribute. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the Ashfields MCP Server server still maintained?
Ashfields MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 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 Ashfields MCP Server server under?
Ashfields MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.