# io.github.ExpertVagabond/ibmz (npm · ibmz-mcp-server)

IBM Z mainframe MCP server - Key Protect HSM & z/OS

- Trust score: 61/100 (medium)
- Change this week: +21
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `ibmz-mcp-server`: 61/100 (this document), [markdown](https://verifymcp.io/servers/expertvagabond-ibmz/ibmz-mcp-server.md), [page](https://verifymcp.io/servers/expertvagabond-ibmz/ibmz-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `ibmz-mcp-server`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 89/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (156 of 157), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (156 of 157), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 169 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 880 tokens (~67/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add expertvagabond-ibmz -- npx -y ibmz-mcp-server
```

### Codex

```bash
codex mcp add expertvagabond-ibmz -- npx -y ibmz-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "expertvagabond-ibmz": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ibmz-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add expertvagabond-ibmz --command npx --arg -y --arg ibmz-mcp-server
```

### Hermes

```yaml
mcp_servers:
  expertvagabond-ibmz:
    command: "npx"
    args: ["-y", "ibmz-mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "expertvagabond-ibmz": {
      "command": "npx",
      "args": [
        "-y",
        "ibmz-mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 61, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-08-01 (score 16, +16)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 0, −40)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-30 (score 40, +22)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 18, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 40)

First indexed and scored.

## MCP tools (13)

### `key_protect_list_keys` (~103 tokens)

List encryption keys from IBM Key Protect (HSM-backed on IBM Z infrastructure, FIPS 140-2 Level 3 certified)

Input parameters:

- `limit` (number): Maximum number of keys to return (default: 100)
- `offset` (number): Number of keys to skip for pagination
- `state` (array): Filter by key states: 1=Active, 2=Suspended, 3=Deactivated, 5=Destroyed

### `key_protect_create_key` (~126 tokens)

Create a new encryption key in IBM Key Protect HSM. Root keys protect other keys (envelope encryption). Standard keys encrypt data directly.

Input parameters:

- `description` (string): Description of the key's purpose
- `extractable` (boolean): If true, key material can be exported (only for standard_key)
- `name` (string, required): Unique name for the key
- `payload` (string): Optional: Base64-encoded key material to import (for BYOK scenarios)
- `type` (string): root_key for wrapping other keys, standard_key for direct encryption

### `key_protect_get_key` (~38 tokens)

Get metadata and details of a specific key from IBM Key Protect

Input parameters:

- `key_id` (string, required): The unique ID of the key

### `key_protect_wrap_key` (~99 tokens)

Wrap (encrypt) a data encryption key using a root key. Used for envelope encryption - protects DEKs with a KEK stored in HSM.

Input parameters:

- `aad` (array): Additional authenticated data for AEAD (optional, must match on unwrap)
- `key_id` (string, required): ID of the root key to use for wrapping
- `plaintext` (string, required): Base64-encoded plaintext data encryption key (DEK) to wrap

### `key_protect_unwrap_key` (~82 tokens)

Unwrap (decrypt) a wrapped data encryption key using a root key

Input parameters:

- `aad` (array): Additional authenticated data (must match what was used during wrap)
- `ciphertext` (string, required): Base64-encoded wrapped (encrypted) data encryption key
- `key_id` (string, required): ID of the root key used to wrap the DEK

### `key_protect_rotate_key` (~66 tokens)

Rotate a root key. Creates new key version while maintaining ability to unwrap data encrypted with previous versions.

Input parameters:

- `key_id` (string, required): ID of the root key to rotate
- `payload` (string): Optional: Base64-encoded new key material for BYOK rotation

### `key_protect_delete_key` (~64 tokens)

Delete a key from IBM Key Protect. WARNING: This is irreversible and data encrypted with this key becomes unrecoverable.

Input parameters:

- `force` (boolean): Force delete even if key has associated resources
- `key_id` (string, required): ID of the key to delete

### `key_protect_get_key_policies` (~37 tokens)

Get policies applied to a key (rotation, dual authorization)

Input parameters:

- `key_id` (string, required): ID of the key

### `zos_connect_list_services` (~41 tokens)

List all available z/OS Connect services (REST APIs exposing mainframe programs). Each service maps to CICS transactions, IMS programs, or batch jobs.

### `zos_connect_get_service` (~45 tokens)

Get detailed information about a z/OS Connect service including its OpenAPI specification and endpoint mappings

Input parameters:

- `service_name` (string, required): Name of the z/OS Connect service

### `zos_connect_call_service` (~125 tokens)

Call a z/OS Connect REST API to interact with mainframe programs. Maps JSON to COBOL copybooks automatically.

Input parameters:

- `method` (string): HTTP method
- `operation` (string): API operation path (e.g., /accounts, /customers/{id})
- `path_params` (object): Path parameters for URL template substitution
- `payload` (object): JSON request body (automatically mapped to COBOL structures)
- `query_params` (object): Query string parameters
- `service_name` (string, required): Name of the z/OS Connect service to invoke

### `zos_connect_list_apis` (~29 tokens)

List all deployed API requester configurations (outbound calls from z/OS to external services)

### `zos_connect_health` (~25 tokens)

Check the health status of the z/OS Connect server and connected subsystems

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/expertvagabond-ibmz/ibmz-mcp-server#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 61
- 2026-08-01: 16
- 2026-07-31: 0
- 2026-07-30: 40
- 2026-07-28: 18
- 2026-07-27: 40

## Links

- npm package: https://www.npmjs.com/package/ibmz-mcp-server
- Socket report: https://socket.dev/npm/package/ibmz-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/expertvagabond-ibmz/ibmz-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/expertvagabond-ibmz/ibmz-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/expertvagabond-ibmz/ibmz-mcp-server