mcpbeat Sign in

WalletTriage MCP Server

by wallettriage Your server? Claim it
local only

WalletTriage runs on your own machine — the client starts it, so there is no endpoint to ping. 50 installs a week from npm. Last commit 8 Jul 2026.

Real-time exploit-exposure risk check for EVM wallets, paid per query via x402 (USDC on Base).

Installs per day peak 24 · avg 6 · +47% w/w
a month agotoday
50
Installs / week
npm · wallettriage-mcp
0
Stars
0 open issues
8 Jul 2026
Last commit
no releases in 90 days
MIT
License
JavaScript

Nothing serious here today

Today is the operative word: we check WalletTriage every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add wallettriage-mcp -e 'EVM_PRIVATE_KEY=<EVM_PRIVATE_KEY>' -- npx -y wallettriage-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "wallettriage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wallettriage-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "<EVM_PRIVATE_KEY>"
      }
    }
  }
}
~/.codex/config.toml
[mcp_servers.wallettriage-mcp]
command = "npx"
args = ["-y", "wallettriage-mcp"]
env = { EVM_PRIVATE_KEY = "<EVM_PRIVATE_KEY>" }
.cursor/mcp.json
{
  "mcpServers": {
    "wallettriage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wallettriage-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "<EVM_PRIVATE_KEY>"
      }
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "wallettriage-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "wallettriage-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "<EVM_PRIVATE_KEY>"
      }
    }
  }
}

Put your own value in place of <EVM_PRIVATE_KEY> (Private key (0x + 64 hex) of a dedicated low-balance session wallet that signs gasless x402 USDC payments on Base. Never use your main key). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: GATEWAY_URL (WalletTriage API base URL. Defaults to the public production gateway; set to http://localhost:4021 for local development), MAX_PAYMENT_ATOMIC (Safety cap: refuse any x402 payment requirement above this many atomic USDC units (6 decimals). Default 100000 = US$0.10), DEFAULT_SCAN_CHAIN (Default chain when the caller omits one: eth, base, polygon, arbitrum, optimism, bsc).

Alternatives to WalletTriage

same job, measured the same way
Signal Feed API: market regime
by dinevdecor

Daily market regime (risk-on / risk-off) for trading agents, paid per call via x402 USDC on Base.

936 installs/wk local only
agent-audit + page-read (x402)
by agent-audit-x402

Pay-per-call page reader, quote check, link check and x402 seller audit. USDC on Base via x402.

7 tools answering
Chaink9
by chaink9

Token risk checks on BSC, ETH, Base and Arc: trades the token on a fork. Paid in USDC via x402.

398 installs/wk 15 tools answering
Paid Base Token Tools
by replit-paid-mcp-opportunity-lab-taylorboucher1

Base token facts and ERC-20 allowance checks. Per-call USDC on Base; x402 wallet required.

6 tools answering
Magneta Contract Risk
by bosacks

Smart-contract risk reports for AI agents on 20 EVM chains, paid per call via x402 ($0.02 USDC).

4 tools answering
Orchard Data MCP
by letom1176-spec

Pay-per-call market data for AI agents via x402 (USDC on Base): regime, track record, catalysts.

128 installs/wk local only
Agent Embassy
by tacticalnoot

Agents pay for work and prove it. Verified checks $0.15, recovery $1.00. USDC on Base via x402.

25 tools answering
Avo Cado Read
by workers-a-347-avocado-read-api

Web page to clean Markdown for agents. Pay per call ($0.003 USDC on Base) via x402.

2 tools answering

WalletTriage — questions

Answers built from our own checks of this server.

Why is there no uptime for WalletTriage?
WalletTriage runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package wallettriage-mcp was installed 50 times last week.
How do I connect WalletTriage?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls wallettriage-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use WalletTriage?
The npm package wallettriage-mcp was installed 50 times in the last week. Week over week that is +47%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is WalletTriage open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.