WalletTriage vs Semgrep
A side-by-side look at the WalletTriage and Semgrep MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose WalletTriage for security work as a local process; choose Semgrep for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose WalletTriage when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EVM_PRIVATE_KEY, GATEWAY_URL, MAX_PAYMENT_ATOMIC, DEFAULT_SCAN_CHAIN. - You want tools like
check_address_risk, get_pricing.
Choose Semgrep when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 49/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | EVM_PRIVATE_KEYGATEWAY_URLMAX_PAYMENT_ATOMICDEFAULT_SCAN_CHAIN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 17,235 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View WalletTriage | View Semgrep |
Tools & capabilities
WalletTriage tools 2
check_address_riskget_pricing
Semgrep tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
WalletTriage
{
"mcpServers": {
"wallettriage": {
"command": "npx",
"args": [
"-y",
"wallettriage-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY_HERE",
"GATEWAY_URL": "YOUR_GATEWAY_URL_HERE",
"MAX_PAYMENT_ATOMIC": "YOUR_MAX_PAYMENT_ATOMIC_HERE",
"DEFAULT_SCAN_CHAIN": "YOUR_DEFAULT_SCAN_CHAIN_HERE"
}
}
}
}
Semgrep
{
"mcpServers": {
"semgrep-semgrep": {
"command": "uvx",
"args": [
"semgrep"
]
}
}
}
Frequently asked questions
WalletTriage is categorized under Security and uses a local stdio subprocess. Semgrep belongs to Security and uses a local stdio subprocess. Pick WalletTriage for security work and Semgrep for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
WalletTriage has no declared pricing — check the project's own site. Semgrep is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add wallettriage and semgrep-semgrep as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, WalletTriage has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Semgrep has 48/100 (Fair) with 1 views, 0 installs and 17,235 GitHub stars.