Keyban Agent Wallet MCP Server

Keyban Agent Wallet is an MCP integration. Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.

Packages and local setup

The published npm package is @keyban/agent-wallet-mcp, version 0.4.6. Its declared MCP transport is stdio.

The package declares KEYBAN_API_KEY (required): Keyban API key of the application the wallet belongs to. Never exposed to the model.; KEYBAN_APP_ID (required): Identifier of the Keyban application.; KEYBAN_INVITE_KEY (required): 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_ADDRESS (required): Address of the deployed SchnorrAccount this server drives (0x + 40 hex).; KEYBAN_NETWORK (required): Blockchain network the wallet operates on, for example base or xdc.; KEYBAN_BASE_URL: Base URL of the Keyban backend. Accepts a full URL, or one of the environment aliases dev, testing, staging, prod and sandbox.; KEYBAN_DKG_BLOB: Optional 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_FILE: Path the server writes its log to.; MCP_LOG_LEVEL: Log verbosity..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project website. This profile uses version 0.4.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.