Zerodust MCP Server

Zerodust is an MCP integration. Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.

Hosted connection

The registry lists a streamable-http connection at https://api.zerodust.xyz/mcp.

Packages and local setup

The published npm package is @zerodust/mcp-server, version 0.5.1. Its declared MCP transport is stdio.

The package declares 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.5.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.