1a04cfa9-4

ConfirmedInfrastructure569 words3 min decode

WalletConnect Launches MCP Service With Wallet-Level Controls

WalletConnect for Agents lets Claude, Claude Code and Cursor check balances and prepare transfers or swaps through MCP, while each transaction still requires approval and a wallet signature.

WalletConnect Launches MCP Service for AI-Assisted Crypto Transactions
WitnessWalletConnect Launches MCP Service for AI-Assisted Crypto TransactionsPexels / pixabay

Outputs

  1. WalletConnect announced WalletConnect for Agents, an MCP service for Claude, Claude Code and Cursor.

  2. Every transaction requires user approval and a signature in the wallet app.

  3. Prepared transaction plans have a five-minute validity period.

  4. Per-transaction limits, a supported-token list and transaction-specific token approvals constrain activity.

  5. Developers can integrate through an HTTP API as access rolls out through a waitlist.

By Nathan Brooks

WalletConnect announced WalletConnect for Agents, a Model Context Protocol (MCP) service that gives every prepared transaction plan a five-minute validity window and requires user approval and a signature in the wallet app.

The service connects Claude, Claude Code and Cursor to users’ existing wallets through MCP. Those AI clients can check balances and prepare token transfers or swaps for review, but they cannot complete either action without the required wallet approval and signature.

Developers can add those functions to agent workflows through an HTTP API. WalletConnect is rolling out access through a waitlist, so immediate availability is limited rather than open to every developer or wallet user.

What changes for developers and users?

For developers, the HTTP API is the integration point for adding balance checks and transaction preparation to an agent workflow. The supported flow covers three operations: check a balance, construct a transfer or swap, and submit that proposal to the user’s wallet for confirmation.

For users, the practical distinction is between preparing a crypto transaction and authorizing it. An AI client can assemble a transfer or swap, but WalletConnect requires the user to approve and sign each transaction in the wallet app. The final authorization step remains outside the agent’s control.

WalletConnect says: “The service does not hold users’ signing keys.” The statement places WalletConnect for Agents on the preparation side of the transaction boundary rather than giving it authority to move funds directly. Users retain signing through their existing wallet setup, while the agent supplies the transaction plan.

The design creates a two-stage operating model: an AI client prepares the request, and the user authorizes the request through the wallet. That separation limits how much authority an agent receives by default while keeping user confirmation inside the execution path.

Several controls govern the path between those stages:

  • Per-transaction limits apply to each request.
  • A supported-token list restricts activity.
  • Prepared transaction plans remain valid for five minutes.
  • Token approvals cover only the amount needed for the specific transaction, rather than an unlimited allowance.

WalletConnect says: “Token approvals cover only the amount needed for a transaction, rather than an unlimited allowance.” That approach bounds the permission associated with an individual transfer or swap and avoids an open-ended token allowance. It does not remove the wallet confirmation requirement, so the user’s signature remains the final authorization step.

The five-minute validity period sets a short operating window for a prepared plan. WalletConnect does not extend that validity indefinitely, and the announcement does not specify the behavior after expiration, the numerical per-transaction limits or the membership of the supported-token list.

For practitioners building agent workflows, transaction execution still depends on an existing wallet and a user action at the point of signing. The HTTP API can make preparation programmable, but it does not turn an AI model into a custodian or an autonomous signer.

WalletConnect therefore places transaction-specific controls around the handoff rather than granting broad wallet authority to Claude, Claude Code or Cursor. The practical change is programmable preparation within a wallet-confirmed process, not autonomous execution.

The staged rollout also keeps the product outside universal availability, and the announcement provides no broader timetable for removing that gate. As waitlist access expands, the five-minute plan window and required wallet signature will test whether the HTTP API can preserve its preparation-and-signature boundary.

via tokenpost.com (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,651 articles