Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/Zerodust

Zerodust

by io.github.andresdefi

Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL
https://api.zerodust.xyz/mcp
Credentials from the publisher
  • ZERODUST_API_URL — Custom API URL (defaults to https://api.zerodust.xyz)
  • ZERODUST_API_KEY — API key for higher rate limits. An agent can issue itself one with the zerodust_register_api_key tool, with no human signup step.
  • ZERODUST_ALLOW_EXECUTE — Set to "true" to enable the sweep tools. Sweeping moves real funds, so it is off by default and also requires one of the four signing-key variables below.
  • ZERODUST_SIGNER_MODULE — Path or specifier of a module whose default export returns a viem LocalAccount. This is how Turnkey, Privy, AWS KMS or any other custody service is used, without a raw key ever reaching this server. Preferred over ZERODUST_PRIVATE_KEY.
  • ZERODUST_KEYSTORE_FILE — Path to an encrypted V3 keystore (as produced by `cast wallet import` or geth). Requires ZERODUST_KEYSTORE_PASSWORD_FILE or ZERODUST_KEYSTORE_PASSWORD.
  • ZERODUST_KEYSTORE_PASSWORD_FILE — Path to a file containing the keystore password, so the password never enters the MCP config.
  • ZERODUST_KEYSTORE_PASSWORD — Keystore password inline. Prefer ZERODUST_KEYSTORE_PASSWORD_FILE.
  • ZERODUST_PRIVATE_KEY_FILE — Path to a file containing a hex private key, so the key stays out of the MCP config.
  • ZERODUST_PRIVATE_KEY — Private key for the agent's own wallet, inline. Used locally to sign the EIP-7702 authorization and EIP-712 sweep intent; never transmitted, only the resulting signatures are sent. The signer-module, keystore and key-file options above keep it out of your config entirely.
  • ZERODUST_ALLOWED_DESTINATIONS — Comma-separated allowlist of sweep destinations. When unset, funds can only be swept to the agent's own address.
Provider
Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code
claude mcp add --transport http io.github.andresdefi-zerodust https://api.zerodust.xyz/mcp

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.andresdefi-zerodust": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.zerodust.xyz/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Questions

How do I install Zerodust?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Zerodust need an API key?
The publisher lists these environment variables: ZERODUST_API_URL, ZERODUST_API_KEY, ZERODUST_ALLOW_EXECUTE, ZERODUST_SIGNER_MODULE, ZERODUST_KEYSTORE_FILE, ZERODUST_KEYSTORE_PASSWORD_FILE, ZERODUST_KEYSTORE_PASSWORD, ZERODUST_PRIVATE_KEY_FILE, ZERODUST_PRIVATE_KEY, ZERODUST_ALLOWED_DESTINATIONS.
What transport does Zerodust use?
Zerodust is reached over HTTP.
When was Zerodust last checked?
Last checked 2026-10-16. Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.

Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.

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 SweepIntent and 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 ZeroDustPermissionRouter a 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.

PackageUse
@zerodust/sdkTypeScript client and agent (createAgentFromPrivateKey); the website uses it
@zerodust/mcp-serverMCP server, run locally (paused)
@zerodust/langchainLangChain tools (paused)
@zerodust/ai-sdkVercel AI SDK tools (paused)

Contracts

ContractAddress (same on every chain, CREATE2)Where
ZeroDustSweep (contracts/src/ZeroDustSweepMainnet.sol)0x3732398281d0606aCB7EC1D490dFB0591BE4c4f2the 56 sponsored chains below
ZeroDustPermissionRouter v2 (contracts/src/ZeroDustPermissionRouter.sol)0x369A97dd256F7eb37fF7116C4EcBd50318eBb28616 chains with MetaMask Advanced Permissions
ZeroDustGuard (contracts/src/ZeroDustGuard.yul)0x2f95e6ED90a7dD67fc3Fae5c5628647E6A83e48eBlast, Boba
ZeroDustPaymaster (contracts-zk/)0x986e4Bb55AEEE6a8c80c28Ca787b13E216fD25B8zkSync Era, Abstract, Lens

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

56 sponsored chains, generated from the live API (GET https://api.zerodust.xyz/chains):

ChainIDTokenChainIDToken
Ethereum1ETHSomnia5031SOMI
Optimism10ETHArc5042USDC
BNB Chain56BNBKaia8217KAIA
Gnosis100xDAIBase8453ETH
Unichain130ETHPlasma9745XPL
Polygon137POL0G166610G
Sonic146SApechain33139APE
Manta Pacific169ETHMode34443ETH
X Layer196OKBMythos42018ETH
Fraxtal252FRAXArbitrum42161ETH
Shape360ETHArbitrum Nova42170ETH
World Chain480ETHCelo42220CELO
Endurance648ACEHemi43111ETH
Stable988gUSDTZircuit48900ETH
Lisk1135ETHInk57073ETH
Intuition1155TRUSTLinea59144ETH
Sei1329SEIBOB60808ETH
DATA Network1514DATABerachain80094BERA
Pharos1672PROSCodex81224ETH
Reya1729ETHDoma97477ETH
Metal L21750ETHPlume98866PLUME
Soneium1868ETHMitosis124816MITO
Ronin2020RONTaiko167000ETH
Morph2818ETHHPP190415ETH
RISE4153ETHScroll534352ETH
MegaETH4326ETHGensyn685689ETH
Robinhood Chain4663ETHKatana747474ETH
Mantle5000MNTZora7777777ETH

Regenerate or check this table with node scripts/generate-chain-docs.mjs (--check runs in CI); do not hand-edit it. The 22 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, Gravity, Abstract, Immutable zkEVM, Etherlink, Avalanche, Blast 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

contracts/      Foundry: ZeroDustSweepMainnet.sol, ZeroDustPermissionRouter.sol, ZeroDustGuard.yul,
                tests, deploy scripts and broadcasts (README, SPECIFICATION, DEPLOYMENT, SECURITY)
contracts-zk/   ZeroDustPaymaster for ZK-stack chains (Hardhat + zksolc)
sdk/            @zerodust/sdk
packages/       @zerodust/mcp-server, @zerodust/ai-sdk, @zerodust/langchain
skills/         an agent skill for ZeroDust
scripts/        generate-chain-docs.mjs

License

MIT, see LICENSE.

How do I install Zerodust?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Zerodust need an API key?
The publisher lists these environment variables: ZERODUST_API_URL, ZERODUST_API_KEY, ZERODUST_ALLOW_EXECUTE, ZERODUST_SIGNER_MODULE, ZERODUST_KEYSTORE_FILE, ZERODUST_KEYSTORE_PASSWORD_FILE, ZERODUST_KEYSTORE_PASSWORD, ZERODUST_PRIVATE_KEY_FILE, ZERODUST_PRIVATE_KEY, ZERODUST_ALLOWED_DESTINATIONS.
What transport does Zerodust use?
Zerodust is reached over HTTP.
When was Zerodust last checked?
Last checked 2026-10-16. Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Pricing
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • MCP Apps
  • Tools
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • Club
  • Work with us
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA