io.github.andresdefi/zerodust
REMOTE · API.ZERODUST.XYZ · 2 COMPONENTS · SCANNED AUG 3
Recover stranded native gas: empty a chain's balance to exactly zero on 25 EVM chains.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 684 tokens (~97/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.zerodust.xyz
claude mcp add --transport http andresdefi-zerodust https://api.zerodust.xyz/mcp
[mcp_servers.andresdefi-zerodust] url = "https://api.zerodust.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"andresdefi-zerodust": {
"type": "remote",
"url": "https://api.zerodust.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add andresdefi-zerodust --url https://api.zerodust.xyz/mcp --transport streamable-http
mcp_servers:
andresdefi-zerodust:
url: "https://api.zerodust.xyz/mcp" {
"mcpServers": {
"andresdefi-zerodust": {
"type": "http",
"url": "https://api.zerodust.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.zerodust.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.zerodust.xyz | CN=WE1,O=Google Trust Services,C=US | 11 Jul 2026 | 9 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a3a9ff4ebbcf01e713fb0afec222afe9 |
| SANs: api.zerodust.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.zerodust.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| zerodust.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.zerodust.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://api.zerodust.xyz/mcp | HTTPS enforced | 301 | https://api.zerodust.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
zerodust_get_balances ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address (0x...) |
No output schema declared.
No examples provided.
zerodust_get_chains ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zerodust_get_quote ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination address to receive swept funds |
| fromChainId | number | yes | Source chain ID to sweep from |
| toChainId | number | yes | Destination chain ID to receive funds |
| userAddress | string | yes | User's wallet address to sweep from |
No output schema declared.
No examples provided.
zerodust_get_sweep_status ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sweepId | string | yes | The sweep ID returned from submitting a sweep |
No output schema declared.
No examples provided.
zerodust_info ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zerodust_list_sweeps ~69
List past sweeps for a wallet address, with status and amounts. Useful for confirming a chain was already emptied before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to list sweeps for |
| limit | number | — | Maximum number of results (default: 10) |
No output schema declared.
No examples provided.
zerodust_register_api_key ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | — | Stable unique identifier for this agent, if it has one |
| contactEmail | string | — | Contact email for support and abuse notices |
| name | string | yes | Human-readable name for this agent, e.g. 'arbitrage-bot-prod' |
No output schema declared.
No examples provided.