Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ExpertVagabond/ibmz

NPM · IBMZ-MCP-SERVER · SCANNED SEP 22

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

Available components

npm · ibmz-mcp-server 78
+1 this week 78 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 54 of 154 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 880 tokens (~67/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "key_protect_delete_key" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.ExpertVagabond/ibmz MCP server?

io.github.ExpertVagabond/ibmz runs locally as an npm package, launched with npx -y ibmz-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ibmz-mcp-server

# add to Claude Code
claude mcp add expertvagabond-ibmz -- npx -y ibmz-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "expertvagabond-ibmz": {
      "command": "npx",
      "args": [
        "-y",
        "ibmz-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "expertvagabond-ibmz": {
      "command": "npx",
      "args": [
        "-y",
        "ibmz-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add expertvagabond-ibmz --command npx --arg -y --arg ibmz-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  expertvagabond-ibmz:
    command: "npx"
    args: ["-y", "ibmz-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "expertvagabond-ibmz": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "ibmz-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add expertvagabond-ibmz -t stdio -c npx -a -y ibmz-mcp-server
// mcp.json
{
  "mcpServers": {
    "expertvagabond-ibmz": {
      "command": "npx",
      "args": [
        "-y",
        "ibmz-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 21 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 18 Sept 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 17 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Analysed npm/ibmz-mcp-server@1.0.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 154 packages
Packages resolved 154
Stale 54
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~880 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
key_protect_create_key ~126

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

NameTypeReqDescription
descriptionstring–Description of the key's purpose
extractableboolean–If true, key material can be exported (only for standard_key)
namestringyesUnique name for the key
payloadstring–Optional: Base64-encoded key material to import (for BYOK scenarios)
typestring–root_key for wrapping other keys, standard_key for direct encryption

No output schema declared.

No examples provided.

key_protect_delete_key ~64

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

NameTypeReqDescription
forceboolean–Force delete even if key has associated resources
key_idstringyesID of the key to delete

No output schema declared.

No examples provided.

key_protect_get_key ~38

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

NameTypeReqDescription
key_idstringyesThe unique ID of the key

No output schema declared.

No examples provided.

key_protect_get_key_policies ~37

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

NameTypeReqDescription
key_idstringyesID of the key

No output schema declared.

No examples provided.

key_protect_list_keys ~103

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

NameTypeReqDescription
limitnumber–Maximum number of keys to return (default: 100)
offsetnumber–Number of keys to skip for pagination
statearray–Filter by key states: 1=Active, 2=Suspended, 3=Deactivated, 5=Destroyed

No output schema declared.

No examples provided.

key_protect_rotate_key ~66

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

NameTypeReqDescription
key_idstringyesID of the root key to rotate
payloadstring–Optional: Base64-encoded new key material for BYOK rotation

No output schema declared.

No examples provided.

key_protect_unwrap_key ~82

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

NameTypeReqDescription
aadarray–Additional authenticated data (must match what was used during wrap)
ciphertextstringyesBase64-encoded wrapped (encrypted) data encryption key
key_idstringyesID of the root key used to wrap the DEK

No output schema declared.

No examples provided.

key_protect_wrap_key ~99

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

NameTypeReqDescription
aadarray–Additional authenticated data for AEAD (optional, must match on unwrap)
key_idstringyesID of the root key to use for wrapping
plaintextstringyesBase64-encoded plaintext data encryption key (DEK) to wrap

No output schema declared.

No examples provided.

zos_connect_call_service ~125

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

NameTypeReqDescription
methodstring–HTTP method
operationstring–API operation path (e.g., /accounts, /customers/{id})
path_paramsobject–Path parameters for URL template substitution
payloadobject–JSON request body (automatically mapped to COBOL structures)
query_paramsobject–Query string parameters
service_namestringyesName of the z/OS Connect service to invoke

No output schema declared.

No examples provided.

zos_connect_get_service ~45

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

NameTypeReqDescription
service_namestringyesName of the z/OS Connect service

No output schema declared.

No examples provided.

zos_connect_health ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

zos_connect_list_apis ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

zos_connect_list_services ~41

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.ExpertVagabond/ibmz MCP server?

io.github.ExpertVagabond/ibmz is an MCP server listed in the public MCP registry as io.github.ExpertVagabond/ibmz. IBM Z mainframe MCP server - Key Protect HSM & z/OS. This page covers its npm package (ibmz-mcp-server).

Is the io.github.ExpertVagabond/ibmz MCP server safe to use?

io.github.ExpertVagabond/ibmz scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.ExpertVagabond/ibmz MCP server expose?

io.github.ExpertVagabond/ibmz exposes 13 tools: key_protect_list_keys, key_protect_create_key, key_protect_get_key, key_protect_wrap_key, key_protect_unwrap_key, and 8 more. Their descriptions and schemas cost roughly 880 tokens of context every time the server is loaded.

Is the io.github.ExpertVagabond/ibmz MCP server still maintained?

io.github.ExpertVagabond/ibmz is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.ExpertVagabond/ibmz MCP server under?

io.github.ExpertVagabond/ibmz declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.