@keyban/agent-wallet-mcp

MCPcommunity
v0.2.2io.keyban.prod.mcpApache-2.0Updated 9d agonpm

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
411Downloads/wk
9d agoLast update
Needs 2 credentials before it runs
  • KEYBAN_API_KEYAPI keyrequired

    Keyban API key of the application the wallet belongs to. Never exposed to the model.

  • KEYBAN_INVITE_KEYAPI keyrequired

    One-shot ECDSA private key (0x + 64 hex) authorizing the first-boot registration of this client as a FROST signer of the wallet.

  • KEYBAN_DKG_BLOBAPI keyoptional

    Optional pre-generated FROST client share, base64-encoded JSON. Used by hosted runtimes with no OS keyring; it does not replace the invite key.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.keyban.prod.mcp
LicenseApache-2.0
Version0.2.2
Sourcenpm+mcp-registry
npm@keyban/agent-wallet-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 2 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.2.1 · 10d agoHow well does this scan work?
EvalsNone
IndexedSep 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source10d ago

Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-13 — observed resolution, not a publisher declaration.

2 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in crypto & web3