io.github.ExpertVagabond/ibmz
NPM · IBMZ-MCP-SERVER
IBM Z mainframe MCP server - Key Protect HSM & z/OS
Available components
Last scanned (19 hours ago)
Scores higher than 59% of npm servers
Category Security
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
- 48 of 147 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 279 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.93 functional
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
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 21 Nov 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 147 packages
| Packages resolved | 147 |
|---|---|
| Stale | 48 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Description of the key's purpose |
| extractable | boolean | – | If true, key material can be exported (only for standard_key) |
| name | string | yes | 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 |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force delete even if key has associated resources |
| key_id | string | yes | ID 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
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The 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)
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | ID 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)
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | ID of the root key to rotate |
| payload | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| aad | array | – | Additional authenticated data (must match what was used during wrap) |
| ciphertext | string | yes | Base64-encoded wrapped (encrypted) data encryption key |
| key_id | string | yes | ID 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.
| Name | Type | Req | Description |
|---|---|---|---|
| aad | array | – | Additional authenticated data for AEAD (optional, must match on unwrap) |
| key_id | string | yes | ID of the root key to use for wrapping |
| plaintext | string | yes | Base64-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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Name 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
| Name | Type | Req | Description |
|---|---|---|---|
| service_name | string | yes | Name 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.
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
claude mcp add expertvagabond-ibmz -- npx -y ibmz-mcp-server
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 21 November 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 21 November 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.
What did VerifyMCP test on the io.github.ExpertVagabond/ibmz MCP server?
VerifyMCP ran 16 checks on io.github.ExpertVagabond/ibmz, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.