Grisoco AI security audits vs WalletTriage
A side-by-side look at the Grisoco AI security audits and WalletTriage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Grisoco AI security auditsSecuritySmart-contract security audits for EVM chains and DAML: quote, run and fetch reports.37FairAuth: not declaredVerdict: choose Grisoco AI security audits for security work; 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?
GChoose Grisoco AI security audits when
- You need dedicated capabilities in the Security domain.
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 | G Grisoco AI security audits | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | EVM_PRIVATE_KEYGATEWAY_URLMAX_PAYMENT_ATOMICDEFAULT_SCAN_CHAIN |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Grisoco AI security audits | View WalletTriage |
Tools & capabilities
Grisoco AI security audits 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.
Grisoco AI security audits
No confirmed install command for Grisoco AI security audits yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
Grisoco AI security audits is categorized under Security and uses an install path we have not confirmed yet. WalletTriage belongs to Security and uses a local stdio subprocess. Pick Grisoco AI security audits 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. Grisoco AI security audits has no confirmed install command yet — follow its own setup instructions.
Grisoco AI security audits is listed as a paid service. 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 grisoco-ai-security-audits and wallettriage as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Grisoco AI security audits has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. WalletTriage has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.