three.ws Agent Payments vs VaultPilot MCP
three.ws Agent Payments is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). VaultPilot MCP is an MCP server published by szhygulin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  three.ws Agent Payments |  VaultPilot MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.5 Downloads/month (npm): 207 Downloads/week (npm): 47 Forks (GitHub): 68 Stars (GitHub): 249 Not marked · First seen |
Listed Version: 0.14.4 Downloads/month (npm): 1 160 Downloads/week (npm): 100 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | three.ws Agent Payments | VaultPilot MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 249 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 68 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@three-ws/agentcore-payments-mcp) | On your machine (vaultpilot-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 10, secrets among them: 4 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/nirholas/three.ws | github.com/szhygulin/vaultpilot-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
three.ws Agent Payments
Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.
VaultPilot MCP
Self-custodial crypto + DeFi MCP for AI agents. Ledger-signed. EVM, TRON, Solana, BTC, LTC.
How to run each
three.ws Agent Payments As a local MCP server: npm package
claude mcp add --env "PAYMENT_SESSION_TOKEN=<YOUR_PAYMENT_SESSION_TOKEN>" --env "THREE_WS_SESSION=<YOUR_THREE_WS_SESSION>" --transport stdio agentcore-payments-mcp -- npx -y @three-ws/agentcore-payments-mcpRequires: PAYMENT_SESSION_TOKEN (secret), THREE_WS_SESSION (secret)
VaultPilot MCP As a local MCP server: npm package
claude mcp add --env "ETHERSCAN_API_KEY=<YOUR_ETHERSCAN_API_KEY>" --env "ONEINCH_API_KEY=<YOUR_ONEINCH_API_KEY>" --env "RPC_API_KEY=<YOUR_RPC_API_KEY>" --env "WALLETCONNECT_PROJECT_ID=<YOUR_WALLETCONNECT_PROJECT_ID>" --transport stdio vaultpilot-mcp -- npx -y vaultpilot-mcpRequires: ETHERSCAN_API_KEY (secret), ONEINCH_API_KEY (secret), RPC_API_KEY (secret), WALLETCONNECT_PROJECT_ID (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only three.ws Agent Payments asks for
PAYMENT_SESSION_TOKEN (secret)THREE_WS_BASETHREE_WS_SESSION (secret)THREE_WS_TIMEOUT_MS
Only VaultPilot MCP asks for
ARBITRUM_RPC_URLBASE_RPC_URLETHEREUM_RPC_URLETHERSCAN_API_KEY (secret)ONEINCH_API_KEY (secret)POLYGON_RPC_URLRPC_API_KEY (secret)RPC_PROVIDERVAULTPILOT_DEMOWALLETCONNECT_PROJECT_ID (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: three.ws Agent Payments · What it can do: VaultPilot MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.