Bvcc Agent Wallet

What is Bvcc Agent Wallet?

An MCP server that lets AI agents operate a non‑custodial BVCC Agent Wallet on‑chain. It integrates the @bvcc/agent-sdk capability catalog and enforces all limits (spend caps, allowed tokens/recipients, expiry) on‑chain via the wallet contract.

How to use Bvcc Agent Wallet?

1. Create a BVCC Agent Wallet and authorize your agent at the BVCC website.
2. Configure AGENT_PRIVATE_KEY, WALLET_ADDRESS, and CHAIN_ID as environment variables.
3. Run npx -y @bvcc/agent-mcp to start the server. The agent private key signs locally and is never transmitted.

Key features of Bvcc Agent Wallet

• Balances for native and ERC‑20 tokens
• Send native tokens and ERC‑20 tokens
• Approve and swap on Uniswap v3/v4
• On‑chain simulation (dry‑runs) before any write
• Opt‑in read‑only mode (BVCC_MCP_READONLY=true)
• Multi‑network support: Ethereum, BNB Chain, Arbitrum, Base, Polygon

Use cases of Bvcc Agent Wallet

• An AI agent manages DeFi positions with pre‑approved spending limits
• Automated cross‑chain payments with per‑call network selection
• AI‑driven token swaps via Uniswap with on‑chain enforcements
• Dry‑run any transaction to verify behaviour before sending

FAQ from Bvcc Agent Wallet

How does the wallet enforce limits?

All spend caps, allowed tokens/recipients, and expiry are enforced directly on‑chain — a blocked action reverts.

What networks are supported?

Ethereum, BNB Chain, Arbitrum, Base, and Polygon. The network can be passed as an optional parameter per call.

Is the private key ever sent to BVCC?

No. The agent private key signs locally on your machine and is never transmitted. BVCC does not custody keys or funds.

How do I run the server in read‑only mode?

Set the environment variable BVCC_MCP_READONLY=true before starting the server. This hard‑locks all write operations.

What configuration is required?

You must set AGENT_PRIVATE_KEY, WALLET_ADDRESS, and CHAIN_ID. A wallet must first be created and the agent authorized at the BVCC website.