
Zerodust
io.github.zerodustxyzPublished by GitHub account zerodustxyzv0.1.1Updated Oct 27, 2026
Sweep native gas tokens to exactly zero across 25+ EVM chains via AI agents.
Overview
Local MCP server for ZeroDust that lets an AI assistant sweep a wallet's native gas balance to exactly zero on EVM chains.
- What you can do
- Sweep native gas tokens from a wallet to exactly zero wei on supported EVM chains
- Send the swept balance to another address on the same chain or bridge it to another chain
- Quote sweeps across sponsored, MetaMask-permission and direct chains, with fees and destination options
- Run locally over stdio against the ZeroDust public API using your own API key
- When to use it
- Useful when you want an assistant to help empty a wallet's remaining native gas on an EVM chain, either to a same-chain address or bridged elsewhere, and you are comfortable signing sweep intents. The vendor notes the agent packages are paused and deprecated on npm, so check current availability before relying on it.
- Requirements
- Runs as a local process over stdio, installed from the npm package @zerodust/mcp-server, so a Node.js runtime is needed. Requires a ZeroDust API key supplied as the ZERODUST_API_KEY environment variable; ZERODUST_API_URL can override the default API endpoint. Network access to the ZeroDust API and the relevant chains is required.
Installation
In SourceWeft
- Open Zerodust in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
ZeroDust
Empty a wallet's native gas balance on an EVM chain to exactly 0.
A normal transfer cannot send a whole native balance, because paying for the transfer uses the token
being sent. ZeroDust sends all of it, to any address on the same chain or bridged to another chain,
and the wallet ends at exactly 0 wei. Live at zerodust.xyz, with an API at
https://api.zerodust.xyz and developer docs at zerodust.xyz/docs.
This repository holds the contracts, the TypeScript SDK and the agent packages.
How it works
- Sponsored chains (EIP-7702): the wallet signs a
SweepIntentand two EIP-7702 authorizations (one delegating to the ZeroDust contract, one removing it afterwards). A ZeroDust sponsor executes the sweep and pays the gas, reimbursed from the swept balance. The contract runs as the wallet and reverts unless the balance ends at exactly 0. - MetaMask without a key: MetaMask's Advanced Permissions (ERC-7715) grant
ZeroDustPermissionRoutera one-time allowance per chain; one EIP-712 signature covers every chain. The router redeems it, requires exactly 0, and settles like the contract. 16 chains. - Direct chains (no EIP-7702): the wallet sends its own legacy transactions, sized to the wei by
the API's planner (22 chains). On OP-stack chains with an L1 data fee it goes through
ZeroDustGuard; on ZK-stack chains a ZeroDust paymaster pays the gas. - What arrives: the destination's native gas, carried by Relay, Across (ETH to ETH), Stargate or Gas.zip, whichever delivers the most. A few chains whose coin no gas bridge carries deliver it as a token instead (Mitosis, Endurance, Intuition, Telos, 0G), said plainly in the quote. On request a sweep can also go into the chain's own bridge to Ethereum (to BNB Chain for opBNB), which the recipient proves and claims there later; Gravity's G and Fraxtal's FRAX arrive on Ethereum as the G and FXS tokens.
For AI agents (paused)
The agent packages (@zerodust/mcp-server, @zerodust/ai-sdk, @zerodust/langchain) are paused
and deprecated on npm, and the hosted MCP endpoint and agent key signup are switched off. The local
MCP server and the SDK still sweep through the public API with your own key; keys issued before keep
their rate limits. To sweep, use zerodust.xyz.
Contracts
All are immutable: no admin functions, no upgrades, no pause (the paymaster's owner can only change its approver and withdraw its float). The sweep contract's sponsor address is fixed in its bytecode.
Supported chains
55 sponsored chains, generated from the live API (GET https://api.zerodust.xyz/chains):
Regenerate or check this table with node scripts/generate-chain-docs.mjs (--check runs in CI); do
not hand-edit it. The 20 direct chains are listed by GET https://api.zerodust.xyz/direct/chains:
Flare, Cronos, Rootstock, Telos, XDC, Fuse, Monad, opBNB, Lens, Boba, zkSync Era, Flow EVM, HyperEVM,
Metis, Vana, Abstract, Immutable zkEVM, Etherlink, Avalanche and Ethereal. Destinations are
any EVM chain a bridge delivers native gas to (GET /destinations?fromChainId=), over 100 from Base.
Fees
1% of the swept value, at least $0.05 and at most $0.50; balances under $1 pay 5%, with no minimum.
On top: the sweep's gas (and the L1 data fee on rollups) and, cross-chain, the bridge's fee. The
signed maxTotalFeeWei caps what can be taken, so a gas spike cannot exceed what you agreed to.
Security
- No custody: every sweep is one atomic transaction from the wallet itself.
- The signed intent caps the fee and names the destination; for a bridge route
routeHash(keccak256(callData)) binds the signature to that exact call. - Every sponsored transaction is simulated before it is sent.
- ERC-7201 namespaced storage, so the contract's nonce never collides with another EIP-7702 app.
- Internal security review, 7 rounds, 16 issues found and fixed; contract tests drive a real EIP-7702 delegation and are mutation-verified. Not externally audited, and no audit is currently funded. Details: contracts/SECURITY.md, contracts/SECURITY_REPORT.md.
Layout
License
MIT, see LICENSE.
Source: README.md at commit 1736e8a
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts