io.github.zerodustxyz/zerodust
NPM · @ZERODUST/MCP-SERVER · SCANNED SEP 20
Sweep native gas tokens to exactly zero across 25+ EVM chains via AI agents.
Available components
Deprecated
This server is marked deprecated in the MCP registry.
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 377 tokens (~62/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 Management93
- Stability observed for 28 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
How do I install the io.github.zerodustxyz/zerodust MCP server?
io.github.zerodustxyz/zerodust runs locally as an npm package, launched with npx -y @zerodust/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 · @zerodust/mcp-server
claude mcp add zerodustxyz-zerodust -- npx -y @zerodust/mcp-server
{
"mcpServers": {
"zerodustxyz-zerodust": {
"command": "npx",
"args": [
"-y",
"@zerodust/mcp-server"
]
}
}
} {
"servers": {
"zerodustxyz-zerodust": {
"command": "npx",
"args": [
"-y",
"@zerodust/mcp-server"
]
}
}
} codex mcp add zerodustxyz-zerodust -- npx -y @zerodust/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zerodustxyz-zerodust": {
"type": "local",
"command": [
"npx",
"-y",
"@zerodust/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add zerodustxyz-zerodust --command npx --arg -y --arg @zerodust/mcp-server
mcp_servers:
zerodustxyz-zerodust:
command: "npx"
args: ["-y", "@zerodust/mcp-server"] {
"McpServers": {
"zerodustxyz-zerodust": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@zerodust/mcp-server"
]
}
}
} assistant mcp add zerodustxyz-zerodust -t stdio -c npx -a -y @zerodust/mcp-server
{
"mcpServers": {
"zerodustxyz-zerodust": {
"command": "npx",
"args": [
"-y",
"@zerodust/mcp-server"
]
}
}
} 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.
- 18 Sept 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.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 11 Sept 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.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
- 7 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.
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 20 Sept 2026 · Analysed npm/@zerodust/mcp-server@0.1.1
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
zerodust_get_balances ~51
Check native gas token balances across all supported chains for a wallet address. Shows which chains have sweepable balances and their USD values.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum wallet address (0x...) |
No output schema declared.
No examples provided.
zerodust_get_chains ~42
Get a list of all blockchain chains supported by ZeroDust for sweeping native gas tokens. Returns chain IDs, names, native tokens, and contract addresses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zerodust_get_quote ~109
Get a quote for sweeping native gas tokens from one chain. Returns the estimated amount the user will receive, fee breakdown, and a quote ID for executing the sweep. Quotes expire in 60 seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination address to receive swept funds |
| fromChainId | integer | yes | Source chain ID to sweep from |
| toChainId | integer | yes | Destination chain ID to receive funds |
| userAddress | string | yes | User's wallet address to sweep from |
No output schema declared.
No examples provided.
zerodust_get_sweep_status ~67
Check the status of a previously submitted sweep. Returns the current status (pending, simulating, executing, bridging, completed, failed), transaction hash if available, and error messages if failed.
| Name | Type | Req | Description |
|---|---|---|---|
| sweepId | string | yes | The sweep ID returned from submitting a sweep |
No output schema declared.
No examples provided.
zerodust_info ~48
Get information about ZeroDust service, including what it does, fee structure, and how to use it. Use this tool when the user asks about ZeroDust or needs to understand the service.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zerodust_list_sweeps ~60
List past sweeps for a wallet address. Shows sweep history with status and amounts.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to list sweeps for |
| limit | integer | – | Maximum number of results (default: 10) |
No output schema declared.
No examples provided.
What is the io.github.zerodustxyz/zerodust MCP server?
io.github.zerodustxyz/zerodust is an MCP server listed in the public MCP registry as io.github.zerodustxyz/zerodust. Sweep native gas tokens to exactly zero across 25+ EVM chains via AI agents. This page covers its npm package (@zerodust/mcp-server).
Is the io.github.zerodustxyz/zerodust MCP server safe to use?
io.github.zerodustxyz/zerodust scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 io.github.zerodustxyz/zerodust MCP server expose?
io.github.zerodustxyz/zerodust exposes 6 tools: zerodust_get_chains, zerodust_get_balances, zerodust_get_quote, zerodust_get_sweep_status, zerodust_list_sweeps, zerodust_info. Their descriptions and schemas cost roughly 377 tokens of context every time the server is loaded.
Is the io.github.zerodustxyz/zerodust MCP server still maintained?
io.github.zerodustxyz/zerodust is marked deprecated in the MCP registry. We last reached this channel on 20 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 io.github.zerodustxyz/zerodust MCP server under?
io.github.zerodustxyz/zerodust declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.