WalletTriage MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GATEWAY_URL | No | WalletTriage API base URL. Defaults to https://api.wallettriage.com | https://api.wallettriage.com |
| EVM_PRIVATE_KEY | Yes | Session key that signs x402 payments (USDC on Base). Must be 0x + 64 hex characters. | |
| DEFAULT_SCAN_CHAIN | No | Default chain: eth, base, polygon, arbitrum, optimism, bsc | eth |
| MAX_PAYMENT_ATOMIC | No | Refuses any 402 requirement above this cap (atomic USDC units, 6 decimals). Default 100000 ($0.10) | 100000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_address_riskA | Real-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_pricingA | Free: returns WalletTriage service status and the current price per risk query (paid via x402, USDC on Base). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have entirely distinct purposes: one performs a risk check on an address, the other retrieves pricing/status. There is no overlap or ambiguity.
Both tools follow a clear verb_noun pattern (check_address_risk, get_pricing), using consistent snake_case naming.
With only 2 tools, the server is very light. For a 'triage' server, one might expect more operations, but the focused paid-query model makes the count borderline acceptable.
The server only offers a single core risk-check tool plus a pricing tool. Missing features like batch checks, historical data, or transaction simulation leave notable gaps for a 'triage' service.