About Keyban Agent Wallet
Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @keyban/cliKEYBAN_API_KEYSecretKeyban API key of the application the wallet belongs to. Never exposed to the model.KEYBAN_APP_IDSecretIdentifier of the Keyban application.KEYBAN_INVITE_KEYSecretWallet mode only. One-shot ECDSA private key (0x + 64 hex) authorizing the first-boot registration of this client as a FROST signer of the wallet.KEYBAN_WALLET_ADDRESSSecretWallet mode only. Address of the deployed SchnorrAccount this server drives (0x + 40 hex).KEYBAN_FUNDINGSecretWho pays for the payments: wallet (the agent's own wallet) or prepaid (the organization's prepaid credit, with no wallet address or invite key).KEYBAN_NETWORKSecretBlockchain network the wallet operates on, for example base or xdc.KEYBAN_BASE_URLSecretBase URL of the Keyban backend. Accepts a full URL, or one of the environment aliases dev, testing, staging, prod and sandbox.KEYBAN_DKG_BLOBSecretOptional pre-generated FROST client share, base64-encoded JSON. Used by hosted runtimes with no OS keyring; it does not replace the invite key.MCP_LOG_FILEPath the server writes its log to.MCP_LOG_LEVELLog verbosity.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
2Saved tool list · updated 1d ago
This tool takes no parameters.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.