BVCC Agent Wallet MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to BVCC wallet simulation and DeFi operations: Do execution limits and simulation remain separate from unsigned plans when supported liquidity protocols change?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Non-custodial on-chain wallet execution for agents with on-chain limits and optional read-only/module controls.

What we know

MCP server generated from the BVCC Agent SDK capability catalog. It can inspect balances/limits, simulate transactions, transfer assets, approve tokens, swap via Uniswap and, in newer modules, manage liquidity and Aave positions. Agent EOA key signs locally; wallet limits are enforced on-chain.

Maintenance / activity evidence

@bvcc/agent-mcp 0.2.2 published 2026-07-30T11:36:46.430Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Real on-chain wallet execution bounded by on-chain capabilities/budgets. Writes: Send native/token transfers; Approve tokens; Swap; Provide/remove liquidity; Supply/borrow/repay/withdraw Aave positions where module enabled.
Agent private key.
Sensitive access: Private key, Wallet balances, Trading/lending positions

Direct asset movement. Use read-only mode when possible, dedicated key file chmod 600, explicit limits and simulation.
On-chain writes are irreversible and financially consequential.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do execution limits and simulation remain separate from unsigned plans when supported liquidity protocols change?

The bounded review of the publisher's documented BVCC wallet simulation and DeFi operations and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Direct asset movement. Use read-only mode when possible, dedicated key file chmod 600, explicit limits and simulation.
Real on-chain wallet execution bounded by on-chain capabilities/budgets.
Agent private key.
Key is used locally; signed transactions go to configured blockchain RPC/router infrastructure.
Reviewed write actions: Send native/token transfers; Approve tokens; Swap; Provide/remove liquidity; Supply/borrow/repay/withdraw Aave positions where module enabled
Sensitive access: Private key, Wallet balances, Trading/lending positions
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Requires agent private key and funded gas.
On-chain writes are irreversible and financially consequential.
Module/tool surface can expand as SDK catalog changes.
Read-only mode must be explicitly enabled when desired.

Original activity observations

@bvcc/agent-mcp 0.2.2 published 2026-07-30T11:36:46.430Z

Technical identity

npm/@bvcc/agent-mcp

Exact implementation source: https://www.npmjs.com/package/@bvcc/agent-mcp ↗
Reviewed resource type: Gateway
Repository identity: blockventurechaincapital-crypto/bvcc-agent-mcp
Package identity: npm:@bvcc/agent-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@bvcc/agent-mcp
Recorded package identity, distribution or download evidence.
GitHub repository ↗
blockventurechaincapital-crypto/bvcc-agent-sdk
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
GitHub repository ↗
blockventurechaincapital-crypto/bvcc-agent-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

On-chain agent wallet MCP. Configure AGENT_PRIVATE_KEY in a separate securely held environment; authorize agent on-chain with scoped permissions and gas funding before writes.
HIGH RISK: real transfers/swaps and DeFi actions. Suggest status/read, then dry-run/simulation only; never test a real transaction. Private keys cannot simply be revoked; revoke on-chain authorization and migrate assets if key compromised.
Earlier review note retained for provenance; the V3 verified fields take precedence: Targeted 2026-10-13 re-research: Publisher provides Claude registration with BVCC_ENV_FILE; wallet/chain writes require explicit user consent.
Publisher provides Claude registration with BVCC_ENV_FILE; wallet/chain writes require explicit user consent.
Prior reviewed safety note: Do not place orders, spend tokens, modify infrastructure or upload confidential files as a test.
Prior reviewed safety note: Never paste a funded wallet private key into shared configuration.
Earlier review note retained for provenance; the V3 verified fields take precedence: Second-pass 2026-10-14 could not retrieve full current publisher npm README; preserve baseline, do not promote source-specific claims or run commands until documentation is rechecked.
Direct npm README reviewed 2026-10-14; client registration still required.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
On-chain agent wallet MCP. Configure AGENT_PRIVATE_KEY in a separate securely held environment; authorize agent on-chain with scoped permissions and gas funding before writes.
publisher documented mcp stdio launch · Publisher instructions
npx -y @bvcc/agent-mcp
Configure / authenticate
MCP100 setup guide
Publisher: `claude mcp add bvcc-agent-wallet -- npx -y @bvcc/agent-mcp` (with the required wallet config/environment from its README).
Check connection
Suggested check
Use read-only `getAgentStatus` and `getCapabilities`, never `sendNative` or approvals for verification.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `bvcc-agent-mcp`, run `claude mcp remove bvcc-agent-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove bvcc-agent-mcp

Official Documentation & Sources

What it does

MCP server generated from the BVCC Agent SDK capability catalog. It can inspect balances/limits, simulate transactions, transfer assets, approve tokens, swap via Uniswap and, in newer modules, manage liquidity and Aave positions. Agent EOA key signs locally; wallet limits are enforced on-chain.

Capability: Finance & Payments
Resource type: Gateway
Industry: Financial Services & Investing
Best fit: Non-custodial on-chain wallet execution for agents with on-chain limits and optional read-only/module controls.

Representative uses

Check balances/capabilities/budgets
Simulate swaps
Send native/ERC-20 tokens
Approve token spend
Swap Uniswap v3/v4
Use optional Aave/liquidity modules

Limitations

Requires agent private key and funded gas.
On-chain writes are irreversible and financially consequential.
Module/tool surface can expand as SDK catalog changes.
Read-only mode must be explicitly enabled when desired.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Agent private key.
Permissions: Real on-chain wallet execution bounded by on-chain capabilities/budgets.
Data handling: Key is used locally; signed transactions go to configured blockchain RPC/router infrastructure.
Cost: transactional
Risk and cautions: Direct asset movement. Use read-only mode when possible, dedicated key file chmod 600, explicit limits and simulation.

Access scope and cautions

Write actions: Send native/token transfers Approve tokens Swap Provide/remove liquidity Supply/borrow/repay/withdraw Aave positions where module enabled
Sensitive access: Private key Wallet balances Trading/lending positions
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Check balances/capabilities/budgets; Simulate swaps; Send native/ERC-20 tokens; Approve token spend; Swap Uniswap v3/v4; Use optional Aave/liquidity modules.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @bvcc/agent-mcp. Recorded transport: stdio. Recorded environment-variable notes: BVCC_ENV_FILE (recommended); AGENT_PRIVATE_KEY; WALLET_ADDRESS; CHAIN_ID (optional/default depends config); BVCC_MCP_READONLY (optional); BVCC_MCP_MODULES (optional). No configuration values are supplied here. Prerequisites: Authorized BVCC Agent Wallet; gas funds. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local agent EOA private key; no custodial server key.

Can it modify data or perform write operations?

Documented write actions include: Send native/token transfers; Approve tokens; Swap; Provide/remove liquidity; Supply/borrow/repay/withdraw Aave positions where module enabled. Recorded permission boundary: Real on-chain wallet execution bounded by on-chain capabilities/budgets.

What data-handling boundary should I consider?

Key is used locally; signed transactions go to configured blockchain RPC/router infrastructure. Recorded sensitive-access context: Private key; Wallet balances; Trading/lending positions.

What limitations and risks should I check before use?

Direct asset movement. Use read-only mode when possible, dedicated key file chmod 600, explicit limits and simulation. Requires agent private key and funded gas. On-chain writes are irreversible and financially consequential. Module/tool surface can expand as SDK catalog changes. Read-only mode must be explicitly enabled when desired. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is transactional. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.