Non-custodial BVCC Agent Wallet on-chain for AI agents: balances, transfers, approvals, swaps.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"bvcc-agent-wallet": {
"env": {
"BVCC_ENV_FILE": "/secure/agent.env"
},
"args": [
"-y",
"@bvcc/agent-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Model Context Protocol server for a BVCC Agent Wallet. It lets MCP-speaking AI runtimes — Claude Code, Cursor, the Claude desktop app — operate a BVCC Agent Wallet on-chain: check balances and limits, plan and simulate swaps, send tokens,
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@bvcc/agent-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @bvcc/agent-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance / ai-ml
Dynamic problem-solving through sequential thought chains
An open-source AI agent that brings the power of Gemini directly into your terminal.
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Use any LLMs (Large Language Models) for Deep Research. Support SSE API and MCP server.
MCP Security Weekly
Get CVE alerts and security updates for com.blockventurechaincapital/bvcc-agent-wallet and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Model Context Protocol server for a BVCC Agent Wallet. It lets MCP-speaking AI runtimes — Claude Code, Cursor, the Claude desktop app — operate a BVCC Agent Wallet on-chain: check balances and limits, plan and simulate swaps, send tokens, and swap on Uniswap v3/v4.
Every tool is generated from the @bvcc/agent-sdk capability
catalog. There is no per-tool code here: add a capability to the SDK catalog and
it appears here automatically.
New here? Start with QUICKSTART.md — the full end-to-end setup (create wallet → authorize the agent on-chain → fund it with gas → configure → verify). It covers the two steps people miss without which the agent does nothing.
This server adds no powers. All limits — spend caps (native + per-token, daily + total), allowed tokens, allowed protocols, recipient whitelist, and a global pause — are enforced on-chain by the Agent Wallet contract. The worst any tool can do is bounded by what you authorized for the agent in the BVCC dashboard.
BVCC_MCP_READONLY=true to expose only read/simulate tools (no writes).Generated from the catalog and tagged by class:
| Class | Tools |
|---|---|
| 🟢 read | getAgentStatus, getCapabilities, getNativeBalance, getTokenBalances, getRemaining, needsApproval |
| 🟡 simulate | buildSwapPlan, dryRunSendNative, dryRunSendToken, dryRunSwapV3, dryRunSwapV4 |
| 🔴 write | sendNative, sendToken, approve, swapV3, swapV4 |
Writes carry the MCP destructiveHint annotation so clients can require
confirmation. See GUIDE.md for the recommended operating workflow.
Recommended: keep the values — above all AGENT_PRIVATE_KEY — in a dedicated
env file and point the server at it with BVCC_ENV_FILE, instead of inlining the
key in your MCP host's config (which gets shared, synced and screenshotted).
chmod 600 that file and keep it outside any cloud-synced folder. You can still
inline the variables in the host's env block if you prefer; host env wins over
the file. See .env.example.
Example agent.env (path passed via BVCC_ENV_FILE):
AGENT_PRIVATE_KEY=0xYOUR_AGENT_KEY
WALLET_ADDRESS=0xYOUR_WALLET
CHAIN_ID=42161
| Variable | Required | Description |
|---|---|---|
AGENT_PRIVATE_KEY | yes | Agent EOA private key (0x + 64 hex). Used locally only. |
WALLET_ADDRESS | yes | The BVCC Agent Wallet this agent operates. |
CHAIN_ID | yes | Default chain: 42161 Arbitrum One · 56 BNB · 1 Ethereum · 8453 Base · 421614 Arbitrum Sepolia. |
RPC_URL | no | Custom RPC for the default chain (otherwise a public default). |
RPC_URL_<chainId> | no | Per-chain RPC override, e.g. RPC_URL_56. |
BVCC_ENV_FILE | no | Path to a dedicated env file to load (keeps the key out of the host config). Host env wins over it. |
BVCC_MCP_READONLY | no | true exposes only read/simulate tools. |
**Multi-n