← Index

Keyban Agent Wallet

io.keyban.prod.mcp/agent-walletv0.2.1Finance & Payments

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

The current version, v0.2.1, was published to the official MCP registry on 2026-09-09. It is distributed as @keyban/agent-wallet-mcp on npm, filed under Finance & Payments by this index, and declares 9 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Keyban Agent Wallet in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-09).

Contracts can change after screening, with no version bump. The gate pins Keyban Agent Wallet’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
KEYBAN_API_KEY
requiredsecret

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
requiredsecret

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
secret

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.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
15
installability
25
documentation
10
stability
5
Alternatives in Finance & Payments