@zerodust/mcp-server

Name: @zerodust/mcp-server
Author: io.github.andresdefi

MCPcommunitylive

v0.4.0io.github.andresdefiMITUpdated 5d agonpm GitHub

MCP server that lets an AI agent sweep its own wallet to exactly zero on 25+ EVM chains, with no gas left stranded.

Endpoint healthlive

checked 3 days ago · 610ms

100% of the last 5 checks reached this endpoint

Works in

ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

278Downloads/wk

2GitHub stars

5d agoLast update

Reads these credentials

ZERODUST_API_KEYAPI keyoptional
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_KEYSTORE_PASSWORDAPI keyoptional
Keystore password inline. Prefer ZERODUST_KEYSTORE_PASSWORD_FILE.
ZERODUST_PRIVATE_KEYAPI keyoptional
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,…

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorio.github.andresdefi

LicenseMIT

Version0.4.0

Sourcenpm+mcp-registry

npm@zerodust/mcp-server

GitHubandresdefi/zerodust

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface10 tools · none privileged

Security scan✓ Cleanv0.3.1 · 1mo agoHow well does this scan work?

EvalsNone

IndexedJul 22, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged

Statically extracted from the published packagev0.3.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

zerodust_get_agent_addressNo description published