Finance · Local MCP server
Keyban Agent Wallet
Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.keyban.prod.mcp/agent-wallet- Version
- 0.2.2
- Status
- Active
- Category
- finance
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- io.keyban.prod.mcp
- Namespace
- Namespace verified by the MCP Registry via the domain mcp.prod.keyban.io or a parent domain of it · how
- Website
- keyban.io
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @keyban/agent-wallet-mcp | 0.2.2 | stdio |
How to connect Keyban Agent Wallet
Keyban Agent Wallet runs locally from a Node.js package published to the npm registry: @keyban/agent-wallet-mcp version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @keyban/agent-wallet-mcp@0.2.2. It reads these environment variables: KEYBAN_API_KEY (required, secret), KEYBAN_APP_ID (required), KEYBAN_INVITE_KEY (required, secret), KEYBAN_WALLET_ADDRESS (required), KEYBAN_NETWORK (required), KEYBAN_BASE_URL, KEYBAN_DKG_BLOB (secret), MCP_LOG_FILE and MCP_LOG_LEVEL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agent-wallet": {
"command": "npx",
"args": [
"-y",
"@keyban/agent-wallet-mcp@0.2.2"
],
"env": {
"KEYBAN_API_KEY": "<secret>",
"KEYBAN_APP_ID": "<value>",
"KEYBAN_INVITE_KEY": "<secret>",
"KEYBAN_WALLET_ADDRESS": "<value>",
"KEYBAN_NETWORK": "<value>",
"KEYBAN_BASE_URL": "<value>",
"KEYBAN_DKG_BLOB": "<secret>",
"MCP_LOG_FILE": "<value>",
"MCP_LOG_LEVEL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| Kema InvoiceCompliant invoicing for freelancers: create, issue and track invoices from your AI agent. | Remote · HTTPLive check: sign-in required |
| Kerdos X402 MCPCrypto market intelligence MCP - pay-per-tool-call in USDC on Base via the x402 protocol. | Local · stdio |
| Kerne Honesty IndexAdvertised versus realized yield for stablecoin vaults, signed hourly, reproducible from chain. | Remote · HTTPLive check: ✓ handshake |
| KEVAREMESH AI Procurement GatewayAI procurement gateway: finds and auto-selects live x402 APIs; provider payments stay buyer-direct. | Remote · HTTPLive check: ✓ handshake |
| Khalid Ibne Hasan · PortfolioQuery Khalid Ibne Hasan's portfolio: profile, availability, case studies, writing, and resume. | Remote · HTTPLive check: ✓ handshake |
| KI AlternativenAlternativen zu bekannten KI-Tools, mit über Stripe geprüften Umsätzen statt Schätzungen. | Remote · HTTPLive check: ✓ handshake |
| KI Tools HeuteTägliche Rangliste neuer KI-Tools mit echten Startdaten und über Stripe geprüften Umsätzen. | Remote · HTTPLive check: ✓ handshake |
| Kifly - Agentic Commerce & PaymentsMulti-seller shopping for AI agents. Settle via Stripe MPP or x402 USDC on Base. Hosted. | Remote · HTTPLive check: ✓ handshake |