Keyban Agent Wallet

io.keyban.mcpPublished by mcp.keyban.iov0.2.2Updated Nov 7, 2026

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

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Keyban agent wallet server that lets an AI agent hold a blockchain wallet, check balances, send USDC and pay x402 APIs under policy.

What you can do
  • Guide the assistant through wallet setup and configuration steps
  • Explain funding the wallet, paying x402 APIs and transferring USDC
  • Describe how to wait for human approval and read a policy refusal
  • Drive a Keyban-provisioned wallet on a chosen blockchain network
When to use it
Worth adding when you want an AI agent to make blockchain payments, such as paying x402 APIs or sending USDC, with policy controls and human approval. Not useful until a Keyban agent wallet has been created and configured.
Requirements
Runs locally via npx as a stdio process on desktop. Needs a Keyban application and agent wallet, with KEYBAN_API_KEY, KEYBAN_APP_ID and KEYBAN_NETWORK required; wallet mode also needs KEYBAN_WALLET_ADDRESS and KEYBAN_INVITE_KEY. Optional KEYBAN_BASE_URL, KEYBAN_FUNDING, KEYBAN_DKG_BLOB and log settings.
Before you install
Handles real funds: the agent can transfer USDC and make payments, so set funding and policy limits carefully. KEYBAN_INVITE_KEY is a one-shot private key authorizing registration as a wallet signer, and KEYBAN_DKG_BLOB holds a FROST client share; keep both secret. KEYBAN_FUNDING decides whether the agent's wallet or organization prepaid credit pays.

Installation

In SourceWeft

  1. Open Keyban Agent Wallet in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

2

setup_instructions

How to finish setting up this wallet

This Keyban agent wallet has no wallet to drive yet, so none of its usual tools are available. Incomplete configuration: KEYBAN_WALLET_ADDRESS, KEYBAN_INVITE_KEY, KEYBAN_NETWORK. Call this tool for the steps to obtain those values from keyban.io.

Takes no parameters.

get_instructions

Read the agent wallet guide

Return the guide to follow with this server (the keyban-agent-wallet skill): funding the wallet, paying x402 APIs, transferring USDC, waiting for a human approval, reading a policy refusal. Call it before the first payment, or whenever a wallet operation is unclear. Creating and configuring the wallet is the Keyban admin MCP guide instead.

Takes no parameters.

Version history

6
  1. v0.2.2LatestNov 7, 2026
  2. v0.2.1Oct 30, 2026
  3. v0.2.0Oct 29, 2026
  4. v0.1.3Oct 20, 2026
  5. v0.1.1Oct 19, 2026
  6. v0.1.0Oct 15, 2026

Score

55% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.