io.github.andresdefi/zerodust
Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.
The current version, v0.3.1, was published to the official MCP registry on 2026-07-25. It is distributed as @zerodust/mcp-server on npm and as a hosted remote over streamable-http, filed under Other by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using io.github.andresdefi/zerodust in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions found”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-09-05).
Contracts can change after screening, with no version bump. The gate pins io.github.andresdefi/zerodust’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for io.github.andresdefi/zerodust](https://mcpindex.ai/server/io-github-andresdefi-zerodust) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-andresdefi-zerodust">Independent trust record for io.github.andresdefi/zerodust</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-andresdefi-zerodust)<a href="https://mcpindex.ai/server/io-github-andresdefi-zerodust"><img src="https://mcpindex.ai/api/v1/badge/io-github-andresdefi-zerodust" alt="mcpindex verdict" height="20" /></a>ZERODUST_API_URLCustom API URL (defaults to https://api.zerodust.xyz)
ZERODUST_API_KEYAPI 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_EXECUTESet 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_MODULEPath 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_FILEPath 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_FILEPath to a file containing the keystore password, so the password never enters the MCP config.
ZERODUST_KEYSTORE_PASSWORDKeystore password inline. Prefer ZERODUST_KEYSTORE_PASSWORD_FILE.
ZERODUST_PRIVATE_KEY_FILEPath to a file containing a hex private key, so the key stays out of the MCP config.
ZERODUST_PRIVATE_KEYPrivate 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_DESTINATIONSComma-separated allowlist of sweep destinations. When unset, funds can only be swept to the agent's own address.
Buy travel eSIMs, gift cards and mobile top-ups with crypto — user confirms before any order.
Give your AI agent a spending limit: approval controls and single-use virtual cards.
Complete 49 CFR 172.101 hazmat table lookup with special-provision decoding, cited to eCFR.