WalletTriage MCP server
io.github.wallettriage/wallettriage-mcp·v0.1.5Real-time exploit-exposure risk check for EVM wallets, paid per query via x402 (USDC on Base).
0 stars31 downloads/wk
Reviews
Write oneNobody has reviewed WalletTriage yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
WalletTriage tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_address_riskReal-time risk check for an EVM wallet address BEFORE acting on it. Cross-references active ERC20 approvals with a live exploit threat feed (contracts under attack right now). Returns risk_score (0-100), risk_level (low/medium/high/critical) and actionable findings. PAID per query via x402 (USDC on Base) using the configured session key — no signup, no API key.
get_pricingFree: returns WalletTriage service status and the current price per risk query (paid via x402, USDC on Base).
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan2 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 79 days ago12/15
- Maintainer identityregistry namespace matches repository owner7/10
How WalletTriage compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 31
- more than 19% of 12,191 servers with a package
What its tools let an agent do: 2 read
Install WalletTriage in Claude Code, Cursor or VS Code
Runs npx -y wallettriage-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add wallettriage-mcp -- npx -y wallettriage-mcp
What the publisher says
From the WalletTriage repository's README, as published. We do not edit it. Read it on GitHub
wallettriage-mcp
<!-- mcp-name: io.github.wallettriage/wallettriage-mcp -->
MCP server for WalletTriage — real-time exploit-exposure check for EVM wallets, built for AI agents. Each query is paid via x402 (USDC on Base) signed locally by a session key: no signup, no API key, no prompts. Stateless — nothing about you or your queries is persisted.
Tools
ERC20 approvals cross-referenced with a live threat feed of contracts under attack. Returns riskscore (0–100), risklevel and actionable findings.
- checkaddressrisk (paid) — real-time risk for an EVM address: dangerous
- getpricing** (free) — service status and current price per query.
Setup (Claude Desktop, Claude Code, Cursor)
Requires Node 20+. Add to your MCP config (e.g. claudedesktopconfig.json):
{
"mcpServers": {
"wallettriage": {
"command": "npx",
"args": ["-y", "wallettriage-mcp"],
"env": {
"GATEWAY_URL": "https://api.wallettriage.com",
"EVM_PRIVATE_KEY": "0xREPLACE_WITH_SESSION_WALLET_PRIVATE_KEY",
"MAX_PAYMENT_ATOMIC": "100000"
}
}
}
}Fund the session wallet with a few USDC on Base. Use a dedicated, low-balance wallet — never your main key. It only signs gasless EIP-3009 USDC payments; WalletTriage never holds or moves funds.
EVMPRIVATEKEY is the wallet's private key (0x + 64 hex), not its address. No ETH needed — payments are gasless (EIP-3009). Test connectivity first with the free get_pricing tool before funding.
Then ask your agent: "Check the risk of 0xd8dA… before I interact with it."
Troubleshooting
networks): your antivirus or proxy intercepts TLS and Node doesn't use the system certificate store by default. Add "NODE_OPTIONS": "--use-system-ca" to the env block. Never disable TLS verification — payments travel in headers and must not be tamperable.
- unable to verify the first certificate (common on Windows / corporate
(the private key of the session wallet). Check for placeholder text, missing 0x or stray whitespace.
- EVMPRIVATEKEY is malformed: the value must be 0x + 64 hex characters
https://api.wallettriage.com. If you overrode it (e.g. to a local gateway), make sure that host is reachable and running.
- Gateway unreachable: GATEWAY_URL defaults to
Environment variables
Local development
npm install
cp .env.example .env # set EVM_PRIVATE_KEY
npm start # runs src/server.ts via tsx (stdio)Point at a local gateway with GATEWAY_URL=http://localhost:4021, or test with the MCP Inspector:
npx @modelcontextprotocol/inspector npx tsx src/server.tsnpm run build emits dist/server.js (the published bin).
Nothing above is checked by us. What we check is on the safety report.
WalletTriage: common questions
- Is WalletTriage MCP server safe?
- Mostly: it is graded B (77/100). Read the WalletTriage safety report
- How do I install WalletTriage?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does WalletTriage need an API key?
- Yes. The registry entry asks for
EVM_PRIVATE_KEY. - Is WalletTriage maintained?
- The last commit was 119 days ago (2026-07-08). The latest release is v0.1.5.
- How does WalletTriage compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.