Zerodust vs Arctic
A side-by-side look at the Zerodust and Arctic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
ArcticFinance & FintechRead Robinhood Chain live: scan a token, trace its deployer, list new launches.52GoodAuth: api key requiredVerdict: choose Zerodust for finance & fintech work as a local process; choose Arctic for finance & fintech. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Zerodust when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
ZERODUST_API_KEY, ZERODUST_ALLOW_EXECUTE, ZERODUST_SIGNER_MODULE, ZERODUST_KEYSTORE_FILE, ZERODUST_PRIVATE_KEY_FILE, ZERODUST_PRIVATE_KEY, ZERODUST_ALLOWED_DESTINATIONS. - You want tools like
zerodust_get_chains, zerodust_get_balances, zerodust_get_quote.
AChoose Arctic when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: API key required.
- You want tools like
scan_token, trace_wallet, robinhood_radar.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Arctic | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 65/100 · Great | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | API key required |
| Pricing | Free | Not declared |
| Required env vars | ZERODUST_API_KEYZERODUST_ALLOW_EXECUTEZERODUST_SIGNER_MODULE |
Tools & capabilities
Zerodust tools 10
zerodust_get_chainsList 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 or sweeping.zerodust_get_balancesFind 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.zerodust_get_quotePrice 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. Call this before sweeping so the user sees the numbers first. Returns a quote ID; quotes expire after about 60 seconds.zerodust_get_sweep_statusCheck 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.zerodust_list_sweepsList past sweeps for a wallet address, with status and amounts. Useful for confirming a chain was already emptied before trying again.zerodust_register_api_keyIssue this agent its own ZeroDust API key for higher rate limits, with no human signup step. The read-only tools work without a key, so only call this when rate limits are actually being hit, or when setting up an unattended agent that will run repeatedly. The key is returned once and is not stored by this server - report it to the operator so they can set ZERODUST_API_KEY.zerodust_infoExplain how a native gas balance can be emptied to exactly zero, what it costs, and how to set this server up to do it. Call this when asked how ZeroDust works, why a full balance normally cannot be sent, or what sweeping will cost.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Zerodust
{
"mcpServers": {
"andresdefi-zerodust": {
"command": "npx",
"args": [
"@zerodust/mcp-server"
],
"env": {
"ZERODUST_API_KEY": "YOUR_ZERODUST_API_KEY_HERE",
"ZERODUST_ALLOW_EXECUTE": "YOUR_ZERODUST_ALLOW_EXECUTE_HERE",
"ZERODUST_SIGNER_MODULE": "YOUR_ZERODUST_SIGNER_MODULE_HERE",
"ZERODUST_KEYSTORE_FILE": "YOUR_ZERODUST_KEYSTORE_FILE_HERE",
"ZERODUST_PRIVATE_KEY_FILE": "YOUR_ZERODUST_PRIVATE_KEY_FILE_HERE",
"ZERODUST_PRIVATE_KEY": "YOUR_ZERODUST_PRIVATE_KEY_HERE",
"ZERODUST_ALLOWED_DESTINATIONS": "YOUR_ZERODUST_ALLOWED_DESTINATIONS_HERE"
}
}
}
}
Arctic
No confirmed install command for Arctic yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Zerodust is categorized under Finance & Fintech and uses a local stdio subprocess. Arctic belongs to Finance & Fintech and uses an install path we have not confirmed yet. Pick Zerodust for finance & fintech work and Arctic for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Arctic has no confirmed install command yet — follow its own setup instructions.
Zerodust is listed as free. Auth: no auth required. Arctic has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add andresdefi-zerodust and arctic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Zerodust has a quality signal of 65/100 (Great) with 7 views, 0 installs and 2 GitHub stars. Arctic has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.