Skip to content
mcp/skillhub

Keyban Agent Wallet MCP Server

io.keyban.prod.mcp/agent-walletv0.4.6

Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.

Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active2d ago

Install Keyban Agent Wallet MCP server

Install in Claude Code

claude mcp add io-keyban-prod-mcp-agent-wallet -e KEYBAN_API_KEY='<keyban-api-key>' -e KEYBAN_APP_ID='<keyban-app-id>' -e KEYBAN_INVITE_KEY='<keyban-invite-key>' -e KEYBAN_WALLET_ADDRESS='<keyban-wallet-address>' -e KEYBAN_NETWORK='<keyban-network>' -e KEYBAN_DKG_BLOB='<keyban-dkg-blob>' -- npx -y @keyban/agent-wallet-mcp

Configuration

VariableRequiredSecretDescription
KEYBAN_API_KEYyesyesKeyban API key of the application the wallet belongs to. Never exposed to the model.
KEYBAN_APP_IDyes—Identifier of the Keyban application.
KEYBAN_INVITE_KEYyesyesOne-shot ECDSA private key (0x + 64 hex) authorizing the first-boot registration of this client as a FROST signer of the wallet.
KEYBAN_WALLET_ADDRESSyes—Address of the deployed SchnorrAccount this server drives (0x + 40 hex).
KEYBAN_NETWORKyes—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—yesOptional 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.

Freshness

Active — last maintenance signal 2d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    no data · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-08 · 2d ago · official registry · v0.4.6

FAQ

›How do I install the Keyban Agent Wallet MCP server in Claude Code?

Run: claude mcp add io-keyban-prod-mcp-agent-wallet -e KEYBAN_API_KEY='<keyban-api-key>' -e KEYBAN_APP_ID='<keyban-app-id>' -e KEYBAN_INVITE_KEY='<keyban-invite-key>' -e KEYBAN_WALLET_ADDRESS='<keyban-wallet-address>' -e KEYBAN_NETWORK='<keyban-network>' -e KEYBAN_DKG_BLOB='<keyban-dkg-blob>' -- npx -y @keyban/agent-wallet-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Keyban Agent Wallet require an API key?

Yes. It expects KEYBAN_API_KEY, KEYBAN_APP_ID, KEYBAN_INVITE_KEY, KEYBAN_WALLET_ADDRESS, KEYBAN_NETWORK, KEYBAN_DKG_BLOB, of which 3 are secrets.

›Can I use Keyban Agent Wallet as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Keyban Agent Wallet in the official MCP registry?

Yes, as io.keyban.prod.mcp/agent-wallet.

Alternatives to Keyban Agent Wallet

Other finance & fintech MCP servers.

View all