🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

@bvcc/agent-mcp

Package Overview
Dependencies
Maintainers
1
Versions
10
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@bvcc/agent-mcp - npm Package Compare versions

Comparing version
0.2.1
to
0.2.2
+19
-0
CHANGELOG.md

@@ -11,2 +11,21 @@ # Changelog

## [0.2.2] — 2026-07-30
### Fixed
- **The server reported the wrong version.** `serverInfo.version` in the MCP handshake —
what your client shows and what the startup banner prints — was a literal in
`server.ts` last updated for 0.1.6, so 0.2.0 and 0.2.1 both announced themselves as
`0.1.6`. Nothing behaved differently, but anyone checking their version saw a stale one
and had reason to think `npx` was serving an old build. The version is now injected at
build time from `package.json` and cannot drift again.
- **The MCP registry entry pinned 0.2.0.** `server.json` named 0.2.0 as the npm version to
install, so anyone arriving through the registry got a build with no wallet V4 support —
no `walletVersion: "v4"` from `getCapabilities`, no V4 call-policy checks, and raw
selectors instead of an actionable `AgentMustBeEOA`. Installing with
`npx -y @bvcc/agent-mcp` was never affected; it resolves to `latest`.
No tool signatures changed and no behaviour changed. Bundles `@bvcc/agent-sdk` 0.2.2,
which is itself a maintenance release identical in behaviour to 0.2.1 — the version
numbers are aligned so that the SDK inside a given MCP build is obvious.
## [0.2.1] — 2026-07-28

@@ -13,0 +32,0 @@

+1
-1
{
"name": "@bvcc/agent-mcp",
"version": "0.2.1",
"version": "0.2.2",
"mcpName": "com.blockventurechaincapital/bvcc-agent-wallet",

@@ -5,0 +5,0 @@ "description": "Model Context Protocol server exposing a BVCC Agent Wallet to AI runtimes (Claude Code, Cursor, Claude app). Tools are generated from the @bvcc/agent-sdk capability catalog.",

Sorry, the diff of this file is too big to display