Walletconnect Mcp

io.github.DELIGHT-LABSPublished by GitHub account DELIGHT-LABSv0.0.4Updated Oct 24, 2026

Non-custodial EVM wallet bridge over WalletConnect: balances, signing, transactions.

VerifiedSTDIODesktop onlyFinance

Server details

Identifier: io.github.DELIGHT-LABS/walletconnect-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account DELIGHT-LABS for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.DELIGHT-LABS%2Fwalletconnect-mcp.svg)](https://sourceweft.com/mcp/io.github.DELIGHT-LABS%2Fwalletconnect-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP bridge to an EVM wallet over WalletConnect, letting an assistant read balances and request signatures and transactions non-custodially.

What you can do: Read EVM wallet balances through a WalletConnect session
Request message and transaction signing from the connected wallet
Initiate transactions that the wallet user must approve
Bridge the assistant to a non-custodial wallet rather than holding keys itself
When to use it: Useful when an assistant should check EVM balances or prepare and request wallet signatures and transactions, with the user approving each action in their own wallet app. Not needed for read-only chain data that needs no wallet.
Requirements: Runs as a local process on the user's machine via the npm package walletconnect-mcp over stdio; desktop only. A WalletConnect-compatible EVM wallet and an active pairing session are implied by the description. No environment variables, headers or authentication are declared.

Before you install

It can request signatures and transactions on an EVM wallet, which may move funds or approve spending; every request should be reviewed in the wallet before approval. The README and tool list are unavailable, so exact permissions and any data sent to WalletConnect relay services cannot be verified.

Installation

In SourceWeft

Open Walletconnect Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.0.4LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.