Back to Browse

Wallettriage MCP Server

FinanceModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

WalletTriage MCP is a well-architected finance server with strong authentication and security controls. It requires a user-configured EVM private key for x402 payment signing, enforces HTTPS for remote gateways, validates input with Zod, and implements a payment cap mechanism. Minor code quality issues (broad error handling, environment variable type assertions) do not materially impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

4 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

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.Required

Environment variable: EVM_PRIVATE_KEY

WalletTriage API base URL. Defaults to the public production gateway; set to http://localhost:4021 for local development.Optional

Environment variable: GATEWAY_URL

Safety cap: refuse any x402 payment requirement above this many atomic USDC units (6 decimals). Default 100000 = US$0.10.Optional

Environment variable: MAX_PAYMENT_ATOMIC

Default chain when the caller omits one: eth, base, polygon, arbitrum, optimism, bsc.Optional

Environment variable: DEFAULT_SCAN_CHAIN

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wallettriage-wallettriage-mcp": {
      "env": {
        "GATEWAY_URL": "your-gateway-url-here",
        "EVM_PRIVATE_KEY": "your-evm-private-key-here",
        "DEFAULT_SCAN_CHAIN": "your-default-scan-chain-here",
        "MAX_PAYMENT_ATOMIC": "your-max-payment-atomic-here"
      },
      "args": [
        "-y",
        "wallettriage-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

  • check_address_risk (paid) — real-time risk for an EVM address: dangerous ERC20 approvals cross-referenced with a live threat feed of contracts under attack. Returns risk_score (0–100), risk_level and actionable findings.
  • get_pricing (free) — service status and current price per query.

Setup (Claude Desktop, Claude Code, Cursor)

Requires Node 20+. Add to your MCP config (e.g. claude_desktop_config.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.

EVM_PRIVATE_KEY 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

  • unable to verify the first certificate (common on Windows / corporate 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.
  • EVM_PRIVATE_KEY is malformed: the value must be 0x + 64 hex characters (the private key of the session wallet). Check for placeholder text, missing 0x or stray whitespace.
  • Gateway unreachable: GATEWAY_URL defaults to https://api.wallettriage.com. If you overrode it (e.g. to a local gateway), make sure that host is reachable and running.

Environment variables

VariableRequiredDefaultPurpose
EVM_PRIVATE_KEYyesSession key that signs x402 payments (USDC on Base)
GATEWAY_URLnohttps://api.wallettriage.comWalletTriage API base URL. Defaults to production; set http://localhost:4021 for local dev (https enforced for non-local hosts)
MAX_PAYMENT_ATOMICno100000 (US$0.10)Refuses any 402 requirement above this cap (atomic USDC units, 6 decimals)
DEFAULT_SCAN_CHAINnoethDefault chain: eth, base, polygon, arbitrum, optimism, bsc

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.ts

npm run build emits dist/server.js (the published bin).

Reviews

No reviews yet

Be the first to review this server!

Wallettriage MCP Server - Real-time exploit-exposure risk check for EVM wallets, paid | MCP Marketplace