voidly-agent-wallet-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VOIDLY_AGENT_KEY | No | Agent key used with the recovery secret for wallet_restore_relay. | |
| VOIDLY_WALLET_NETWORK | No | Network to use. Defaults to base-sepolia. Set to base for Base mainnet. | |
| VOIDLY_WALLET_STATE_DIR | No | Private, durable directory for the encrypted backup, spend ledger, and Marketplace recovery records. Keep the same directory across restarts. | |
| VOIDLY_WALLET_DAILY_USDC | No | UTC-day USDC cap. Defaults to 5. | |
| VOIDLY_WALLET_MEMORY_ONLY | No | Set to 1 to support encrypted Relay backup and restore but refuse payment. | |
| VOIDLY_WALLET_PER_CALL_USDC | No | Per-call USDC cap. Defaults to 1. | |
| VOIDLY_WALLET_ALLOWED_ORIGINS | No | Comma-separated list of allowed payment origins. Required with VOIDLY_WALLET_NETWORK=base for Base mainnet. To restrict a staging run, set to https://x402-staging.voidly.ai. | |
| VOIDLY_WALLET_RECOVERY_SECRET | No | Saved recovery secret for restoring the local encrypted backup or making another backup. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| wallet_generate_recovery_secretA | Generate a one-time 32-byte recovery secret. Store it in the agent secret manager before creating a wallet; it is never sent to Voidly. |
| wallet_createB | Generate a Base wallet key locally and encrypt it under the agent-held recovery secret before returning. |
| wallet_addressB | Get the locally held wallet address. |
| wallet_receive_infoA | Get the USDC receiving address and Base network information. |
| wallet_funding_requestA | Locally generate a Base USDC EIP-681 funding URI and SVG QR for this wallet. This does not sign or submit a transfer. |
| wallet_prepare_voidly_seller_registrationA | Fetch and sign only Voidly's exact seller-registration SIWE challenge; return the fixed submit URL and body without submitting. |
| wallet_balanceA | Read the wallet USDC balance from the configured Base RPC. |
| wallet_pay_x402A | Pay a public HTTPS x402 resource with local USDC authorization, within configured per-call and daily limits. |
| wallet_marketplace_attemptsA | List locally retained Marketplace quote and payment keys for payer-authenticated recovery; never retries or pays. |
| wallet_recover_marketplaceB | Sign a fresh payer recovery request for a locally retained Marketplace attempt; never sends a payment retry. |
| wallet_backup_relayB | Encrypt the local key with the agent-held recovery secret, then store only ciphertext in Relay memory. |
| wallet_restore_localB | Restore the local encrypted vault with the agent-held recovery secret. |
| wallet_restore_relayB | Restore the wallet locally from client-encrypted Relay memory using the agent-held recovery secret. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools target clearly distinct actions (create, balance, pay, back up, restore). Minor overlap exists between wallet_address and wallet_receive_info, and the three backup/restore variants (wallet_backup_relay, wallet_restore_local, wallet_restore_relay) are close in purpose though descriptions differentiate their sources.
Every tool follows a consistent wallet_ snake_case verb_noun pattern, including longer names like wallet_prepare_voidly_seller_registration. No mixing of conventions.
13 tools sit comfortably within the well-scoped 3-15 range for a self-custody agent wallet. Each tool maps to a distinct lifecycle step with no redundant filler.
Coverage is strong: secret generation, creation, address, funding, balance, x402 payment, backup, and both local and relay restoration are present. A generic outbound transfer tool beyond x402 pay is absent, but the constrained design is intentional and workable.