Shield vs WalletTriage
A side-by-side look at the Shield and WalletTriage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Shield for security work as a local process; choose WalletTriage 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 Shield when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 63/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | EVM_PRIVATE_KEYGATEWAY_URLMAX_PAYMENT_ATOMICDEFAULT_SCAN_CHAIN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Shield | View WalletTriage |
Tools & capabilities
Shield tools
No tool names declared yet. Check the project README from the listing page.
WalletTriage tools 2
check_address_riskget_pricing
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.
Shield
{
"mcpServers": {
"aperionai-shield": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-postgres"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Shield is categorized under Security and uses a local stdio subprocess. WalletTriage belongs to Security and uses a local stdio subprocess. Pick Shield for security work and WalletTriage 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.
Shield is listed as free. Auth: no auth required. WalletTriage has no declared pricing — check the project's own site. 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 aperionai-shield and wallettriage as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shield has a quality signal of 63/100 (Good) with 5 views, 0 installs and 11 GitHub stars. WalletTriage has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.