Wallet Mcp

Created By
TP Laba year ago
Seamlessly connect your plugin wallet to an LLM—no private key setup required. Developed by TokenPocket.
Overview

Wallet MCP

Connect your crypto wallet to AI Client.

👉 Learn more at https://mcp.tp.xyz/

Overview

Wallet MCP is an npm package that provides a seamless integration between AI Clients and user's crypto wallets. This package allows AI Clients to interact with blockchain functionality through natural language processing.

Features

  • Wallet Connection: Easily connect to a user's wallet to retrieve their address
  • Transaction Signing: Support for signing transactions and messages
  • Multi-chain Support: Currently supports Ethereum and Solana networks

Usage

Installation

  {
    "mcpServers": {
      "wallet-mcp": {
        "command": "npx",
        "args": [
          "wallet-mcp"
        ]
      }
    }
  }

Architecture

Wallet MCP interacts with the Wallet MCP DApp to handle the secure connection to user wallets and transaction signing.

Workflow

  1. Wallet Connection: AI Client -> Wallet MCP -> DApp -> User Wallet
  2. Transaction Signing: AI Client -> Wallet MCP -> DApp -> User Wallet -> Signed Transaction

License

MIT

Server Config

{
  "mcpServers": {
    "wallet-mcp": {
      "command": "npx",
      "args": [
        "wallet-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TP Lab
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago