Zerodust

What andresdefi/zerodust MCP server does

The andresdefi/zerodust MCP server helps an agent identify and recover native gas token balances that are normally too small to transfer completely. It supports 25 live EVM mainnets through the API, including Ethereum, Base, Arbitrum, Optimism, BNB Chain, Polygon, and others. The authoritative supported-chain list comes from the service API, so agents should query it before presenting a quote or attempting a sweep.

A sweep can empty one source chain or consolidate balances from multiple chains onto one destination. Supported flows include same-chain transfers to another address, cross-chain transfers to the same address, and cross-chain transfers to a different address. The source balance is intended to end at exactly zero wei.

How it works

Ordinary native-token transfers cannot send the entire balance because the transaction itself requires native gas. ZeroDust uses EIP-7702 sponsored execution: the wallet authorizes the operation, a relayer submits and pays for execution, and the cost is accounted for in the amount delivered. Cross-chain operations can also invoke a bridge target as part of the execution.

The normal agent flow is to inspect balances, request a quote, confirm the signing address and permitted destinations, and then submit a sweep. Quotes include the expected received amount and fee breakdown, and expire after about 60 seconds. Status can be checked later using the returned sweep information.

Setup and configuration

The hosted MCP endpoint is available at https://api.zerodust.xyz/mcp. It provides read-only discovery and quoting without installing the package or supplying a key. For local execution, configure the @zerodust/mcp-server package through an MCP client and set ZERODUST_ALLOW_EXECUTE=true together with one signing-key source.

Supported key sources include a signer module, an encrypted V3 keystore plus a separate password file, a private-key file, or a directly configured private key. A signer module can return a viem LocalAccount, which allows custody-provider adapters to supply the account. ZERODUST_ALLOWED_DESTINATIONS can further restrict where funds may be sent; otherwise funds can go only to the agent's own address.

The server can issue an API key for higher rate limits through zerodust_register_api_key. The key is returned once and must be reported to the operator for configuration as ZERODUST_API_KEY.

Tools and capabilities

The andresdefi/zerodust MCP server exposes tools for:

• Listing supported chains and their native tokens.
• Finding recoverable native balances across chains for an address.
• Producing short-lived quotes with delivery and fee details.
• Checking sweep status and listing previous sweeps.
• Showing the configured signing address and allowed destinations.
• Sweeping one chain or all funded chains.
• Explaining the execution model and setup requirements.
• Registering an API key when rate limits require one.

Execution tools support dryRun. A dry run obtains a real quote and creates the signatures needed for the flow but stops before broadcasting, so funds are not moved.

Limitations and notes

The andresdefi/zerodust MCP server serves mainnet chains only; there is no testnet API environment. Use dryRun instead of a testnet flag for rehearsal. Actual sweeps require both the explicit execution opt-in and a signing key; without them, the execution tools return an error and move no funds.

The browser interface depends on a non-standard wallet_signAuthorization RPC that shipping wallets do not yet expose, but agents signing locally are described as unaffected. Destination restrictions should be reviewed before enabling unattended execution, and agents should call the address and balance inspection tools before moving funds.