What is the key difference between Ibmz and WalletTriage?

Ibmz belongs to the Security category with local stdio execution, while WalletTriage belongs to the Security category with local stdio execution.

How do I install Ibmz or WalletTriage in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Ibmz and WalletTriage free or paid?

Ibmz operates under a Free / Open Source model (No auth required). WalletTriage operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Ibmz lists 13 tools with 0 views and 0 GitHub stars. WalletTriage lists 2 tools with 1 views and 0 GitHub stars.

Can I use both Ibmz and WalletTriage together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Ibmz vs WalletTriage

In-depth architectural comparison of the Ibmz 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.

At a Glance & Executive Verdict

Ibmz

Security · Local stdio

Quality: 44/100 (Fair) | Auth: No auth required

WalletTriage

Security · Local stdio

Quality: 53/100 (Good) | Auth: No auth required

Verdict Summary: Choose Ibmz if you need specialized Security tools running via a local process. Choose WalletTriage if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Ibmz 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: key_protect_list_keys, key_protect_create_key, key_protect_get_key.

Explore Ibmz 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	Ibmz Security	WalletTriage Security
Summary	IBM Z mainframe MCP server - Key Protect HSM & z/OS	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

Ibmz Tools (13)

key_protect_list_keys

List encryption keys in Key Protect

key_protect_create_key

Create root or standard keys

key_protect_get_key

Get key details and metadata

key_protect_wrap_key

Wrap (encrypt) a DEK with a root key

key_protect_unwrap_key

Unwrap (decrypt) a wrapped DEK

key_protect_rotate_key

Rotate a root key

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).

Ibmz Configuration

mcpServers (Claude Desktop / Cursor)

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

WalletTriage Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Ibmz is categorized under Security and uses a local stdio subprocess. In contrast, WalletTriage belongs to Security using local stdio subprocess. Select Ibmz when you need capabilities focused on security and WalletTriage when you require tools for security.