npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

web3-wallet-relay

v3.2.0

Published

Browser wallet signing relay for web3-tools-mcp — runs embedded or on a host

Readme

web3-wallet-relay

The browser signing page for web3-tools-mcp, and the WebSocket rendezvous behind it. The MCP server sends a transaction, the page shows what it does, and your wallet extension signs it — the relay only passes messages between the two and holds no keys.

You normally never install this. The MCP server embeds it and starts one on localhost when a transaction needs signing.

Install it separately only to host the page, so a machine without a browser can still have something signed. It depends only on express and ws, so it runs anywhere that keeps a Node process alive and supports WebSockets.

WALLET_TOKEN=<long random string> \
WALLET_PUBLIC_URL=https://wallet.example.com \
npx web3-wallet-relay

Then point the MCP server at it with WALLET_SERVER_URL and the same WALLET_TOKEN.

Run the relay at the same version as that server — npx [email protected] for web3-tools-mcp 3.2.0. The two share a version number because they share a protocol, and a mismatched pair cannot pair at all.

The pairing link carries a token derived from WALLET_TOKEN that can only answer signing requests, not make them. Sharing a pairing link is therefore not the same as sharing WALLET_TOKEN — but whoever has it can act as your wallet page, so a signing request can reach them instead of you.

| Variable | | | --- | --- | | WALLET_TOKEN | The MCP server's secret. Anyone holding it can send your browser a transaction to sign — treat it like a password, and serve over HTTPS. Generated per run if unset. The signing page gets a separate token derived from this one, which may only answer requests; that is what pairing links carry. | | PORT | Provided by most hosts. Set, the relay binds 0.0.0.0 and takes that one port; unset, it binds loopback and scans 3456-3460. | | HOST | Override the bind address. | | WALLET_PUBLIC_URL | The URL to print in pairing links, when it differs from the bind address. |

It is also usable as a library — WalletRelay, plus the TransactionRequest and TransactionResponse types.

Part of the web3-tools-mcp repo, where the full documentation lives.

MIT