Compliance Evidence vs WalletTriage

In-depth architectural comparison of the Compliance Evidence and WalletTriage MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

C

Choose Compliance Evidence when:

• You need dedicated capabilities in the Security domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Compliance Evidence Details

Choose WalletTriage when:

• You need dedicated capabilities in the Security domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: check_address_risk, get_pricing.

Explore WalletTriage Details

Feature & Specification Comparison

Specification	C Compliance Evidence Security	WalletTriage Security
Summary	Dated, signed compliance-evidence packs: gov-fact-grounded claims + exclusion screens + trap-facts.	Real-time exploit-exposure risk check for EVM wallets, paid per query via x402 (USDC on Base).
Category & Scope	Security	Security
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "compliance-evidence": {
      "command": "npx",
      "args": [
        "-y",
        "compliance-evidence"
      ]
    }
  }
}

{
  "mcpServers": {
    "wallettriage": {
      "command": "npx",
      "args": [
        "-y",
        "wallettriage-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons