Enterprise DNAEnterprise DNA

MCP Servers

nikicat/mcp-wallet-signer

MCP server that routes blockchain transactions to browser wallets for signing

Our verdict

Not reviewed yet

We have not reviewed nikicat/mcp-wallet-signer yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About nikicat/mcp-wallet-signer

An MCP server that routes blockchain transactions to browser wallets for signing. It enables AI agents or tools to propose transactions that users approve directly in extensions like MetaMask. Written in TypeScript, it acts as a bridge between MCP-based systems and web3 wallets.

Best for

Developers building AI agents that need user-approved blockchain transactions

Use cases

  • Integrate blockchain transaction signing into AI agent workflows
  • Allow AI to propose transactions that users approve in their browser wallet
  • Bridge MCP-based tools with web3 wallets for secure signing

Notes

1 stars on GitHub. Last updated 2026-05-20. Licensed MIT.

Pros

  • Keeps private keys secure by using browser wallet signing
  • Enables AI agents to initiate transactions with user approval
  • Open source and written in TypeScript

Cons

  • Very early stage with only 1 star and minimal community adoption
  • Requires a browser wallet extension installed and connected
  • Limited documentation and proven reliability

Key facts

What we have checked

Days since the last commit
18
Checked GitHub
GitHub forks
2
Checked GitHub
GitHub stars
2
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
3
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

npx -y mcp-wallet-signer

Tools exposed

  • connect_wallet
  • send_transaction
  • sign_message
  • sign_typed_data
  • get_balance
  • get_token_balance
  • tron_connect_wallet
  • tron_send_transaction
  • tron_trigger_contract
  • tron_sign_message
  • tron_sign_typed_data
  • tron_get_balance
  • tron_get_token_balance
  • EVM_MCP_PORT
  • EVM_MCP_DEFAULT_CHAIN
  • TRON_MCP_PORT
  • TRON_MCP_DEFAULT_NETWORK

Clients the listing names (not checked here)

Claude Desktop, Claude Code, Cursor, Windsurf

Install

Add nikicat/mcp-wallet-signer to your client

Server verified

Checked : our lab installed version 0.1.3, started it and listed its 5 tools. How the lab checks

Maker? Show the badge on your own README or site

Our lab passed this server, so it can carry "Server verified on Enterprise DNA". The badge is a live link: it disappears if a later check fails, and it is never for sale.

HTML

<a href="https://enterprisedna.co/directories/mcp/nikicat-mcp-wallet-signer"><img src="https://enterprisedna.co/directories/badge/mcp-servers/nikicat-mcp-wallet-signer.svg" alt="Server verified on Enterprise DNA, checked 1 Nov 2026" width="300" height="44"></a>

Markdown

[![Server verified on Enterprise DNA, checked 1 Nov 2026](https://enterprisedna.co/directories/badge/mcp-servers/nikicat-mcp-wallet-signer.svg)](https://enterprisedna.co/directories/mcp/nikicat-mcp-wallet-signer)

Claude Code

Config checked

Run in your terminal (runs on your computer)

claude mcp add --transport stdio nikicat-mcp-wallet-signer -- npx -y mcp-wallet-signer@0.1.3

Version 0.1.3 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Claude Desktop

Config checked

Add to claude_desktop_config.json (runs on your computer)

{
  "mcpServers": {
    "nikicat-mcp-wallet-signer": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-wallet-signer@0.1.3"
      ]
    }
  }
}

Version 0.1.3 · From the Official MCP registry, read · Format checked against Claude Desktop's config docs

Cursor

Config checked

Add to .cursor/mcp.json (runs on your computer)

{
  "mcpServers": {
    "nikicat-mcp-wallet-signer": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-wallet-signer@0.1.3"
      ]
    }
  }
}

Version 0.1.3 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (runs on your computer)

{
  "servers": {
    "nikicat-mcp-wallet-signer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-wallet-signer@0.1.3"
      ]
    }
  }
}

Version 0.1.3 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (runs on your computer)

[mcp_servers.nikicat-mcp-wallet-signer]
command = "npx"
args = ["-y", "mcp-wallet-signer@0.1.3"]

Version 0.1.3 · From the Official MCP registry, read · Format checked against Codex's config docs

  • ChatGPT: ChatGPT connects only to remote servers that need no API key.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What nikicat/mcp-wallet-signer connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.1.3Config checkedClaude Code docs
Claude DesktopClientInstall recipe matches the client's documented formatRuns locally, version 0.1.3Config checkedClaude Desktop docs
CursorClientInstall recipe matches the client's documented formatRuns locally, version 0.1.3Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.1.3Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRuns locally, version 0.1.3Config checkedCodex docs

Stars and usage

How nikicat/mcp-wallet-signer is growing

GitHub stars

2 to 2

stars. 29 Oct 2026 to 19 Nov 2026, 4 readings.

Source: GitHub. Checked .

Health and security

Is nikicat/mcp-wallet-signer looked after, and what do its setup files show

Health score

0 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Archived0Repository is archived

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1 npm:mcp-wallet-signer@0.7.0. What it checks

Licence: MIT

  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

  1. Shut down

    Source: GitHub

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.