zerodust

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
80%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,021Tokens (definiciones de herramientas)
~583 BTamaño de respuesta típico
Impacto moderado en la atención (0.80% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "zerodust": {
      "command": "npx",
      "args": [
        "@zerodust/mcp-server"
      ]
    }
  }
}

Paquetes ejecutables

npm@zerodust/mcp-server0.4.0stdio

Puntos de conexión remotos

https://api.zerodust.xyz/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (7)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢zerodust_get_balances(address)

Find leftover native gas token (ETH, BNB, POL, ...) stranded across every supported EVM chain for one address, and report which of it can be recovered. Normally these balances are unrecoverable: you cannot transfer 100% of a gas token, because paying for the transfer consumes the thing you are transferring, so a remainder is always left behind. This reports what is stuck and what could be moved out. Useful when a wallet has small amounts scattered over many chains, when someone cannot send their full balance, or before closing out, winding down or decommissioning a wallet.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Ethereum address (0x...)"
    }
  },
  "required": [
    "address"
  ]
}
🟢zerodust_get_quote(fromChainId, toChainId, userAddress, destination)

Price out emptying a chain's native gas balance to exactly zero: how much actually arrives, the full fee breakdown, and whether the balance is even large enough to be worth recovering. Returns a quote ID; quotes expire after about 60 seconds. Executing the sweep needs the wallet's signing key, which this hosted server does not hold - use the @zerodust/mcp-server package or the SDK for that.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "fromChainId": {
      "type": "number",
      "description": "Source chain ID to sweep from"
    },
    "toChainId": {
      "type": "number",
      "description": "Destination chain ID to receive funds"
    },
    "userAddress": {
      "type": "string",
      "description": "User's wallet address to sweep from"
    },
    "destination": {
      "type": "string",
      "description": "Destination address to receive swept funds"
    }
  },
  "required": [
    "fromChainId",
    "toChainId",
    "userAddress",
    "destination"
  ]
}
🟢zerodust_get_chains

List the EVM chains a native gas balance can be emptied to exactly zero on. Returns chain IDs, names, and native tokens. Call this to check whether a specific chain is supported before quoting.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "required": []
}
🟢zerodust_get_sweep_status(sweepId)

Check how a previously submitted sweep is progressing. Returns the current status (pending, simulating, executing, bridging, completed, failed), the transaction hash once there is one, and the error message if it failed.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "sweepId": {
      "type": "string",
      "description": "The sweep ID returned from submitting a sweep"
    }
  },
  "required": [
    "sweepId"
  ]
}
🟢zerodust_list_sweeps(address, limit)

List past sweeps for a wallet address, with status and amounts. Useful for confirming a chain was already emptied before trying again.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "address": {
      "type": "string",
      "description": "Wallet address to list sweeps for"
    },
    "limit": {
      "type": "number",
      "description": "Maximum number of results (default: 10)"
    }
  },
  "required": [
    "address"
  ]
}
⚪zerodust_register_api_key(name, agentId, contactEmail)

Issue this agent its own ZeroDust API key for higher rate limits, with no human signup step. The other tools work without a key, so only call this when rate limits are being hit, or when setting up an unattended agent that will run repeatedly. The key is returned once and cannot be retrieved later - report it to the operator.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "Human-readable name for this agent, e.g. 'arbitrage-bot-prod'"
    },
    "agentId": {
      "type": "string",
      "description": "Stable unique identifier for this agent, if it has one"
    },
    "contactEmail": {
      "type": "string",
      "description": "Contact email for support and abuse notices"
    }
  },
  "required": [
    "name"
  ]
}
🟢zerodust_info

Explain how a native gas balance can be emptied to exactly zero, what it costs, and how to integrate. Call this when asked how ZeroDust works, why a full balance normally cannot be sent, or what sweeping will cost.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "required": []
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada7 herramientas
verificadoversión no registrada7 herramientas
verificadoversión no registrada7 herramientas