Keyban Agent Wallet

io.keyban.prod.mcpPublished by mcp.prod.keyban.iov0.4.6Updated Oct 25, 2026

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

VerifiedSTDIODesktop onlyFinance AI & ML

Server details

Identifier: io.keyban.prod.mcp/agent-wallet
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to mcp.prod.keyban.io. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.keyban.prod.mcp%2Fagent-wallet.svg)](https://sourceweft.com/mcp/io.keyban.prod.mcp%2Fagent-wallet?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Gives an AI assistant its own blockchain wallet to check balances, send USDC transfers and make x402 payments under policy.

What you can do: Check the wallet's balances on its configured blockchain network and address. Send USDC transfers from the wallet. Make x402 payments, subject to the wallet's policy. Operates a SchnorrAccount wallet whose signing share is registered on first boot.
When to use it: Useful when an assistant needs to hold and spend funds on-chain on its own, for example paying for x402-enabled services or moving USDC, and you are prepared to give it a funded wallet with spending limits.
Requirements: Runs locally via npx (Node.js). Requires a Keyban application ID, API key, invite key, blockchain network and wallet address, set through environment variables; an optional pre-generated signing share can be supplied for runtimes without an OS keyring. Desktop only.

Before you install

Handles real funds and private key material: the invite key authorizes registering this client as a wallet signer, and the API key and signing share are secrets. Transfers and payments move money and cannot be undone, so set policy limits and fund the wallet sparingly. Logs written to a file may contain operational detail.

Installation

In SourceWeft

Open Keyban Agent Wallet in the dashboard and add it to a workspace.
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

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.4.6LatestOct 8, 2026
v0.4.5Oct 7, 2026
v0.4.4Oct 6, 2026
v0.2.2Sep 16, 2026

Score

15% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
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 listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
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.