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/watsonx

NPM · WATSONX-MCP-SERVER · SCANNED SEP 22

IBM watsonx.ai MCP server for Claude integration

Available components

0 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 150 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 837 tokens (~64/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 Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
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/watsonx MCP server?

io.github.ExpertVagabond/watsonx runs locally as an npm package, launched with npx -y watsonx-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 · watsonx-mcp-server

# add to Claude Code
claude mcp add expertvagabond-watsonx -- npx -y watsonx-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "expertvagabond-watsonx": {
      "command": "npx",
      "args": [
        "-y",
        "watsonx-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "expertvagabond-watsonx": {
      "command": "npx",
      "args": [
        "-y",
        "watsonx-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add expertvagabond-watsonx -- npx -y watsonx-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "expertvagabond-watsonx": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "watsonx-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add expertvagabond-watsonx --command npx --arg -y --arg watsonx-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  expertvagabond-watsonx:
    command: "npx"
    args: ["-y", "watsonx-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "expertvagabond-watsonx": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "watsonx-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add expertvagabond-watsonx -t stdio -c npx -a -y watsonx-mcp-server
// mcp.json
{
  "mcpServers": {
    "expertvagabond-watsonx": {
      "command": "npx",
      "args": [
        "-y",
        "watsonx-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 0
    • Stability: 0.97 → pass security
  • 21 Sept 26 +1

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

  • 20 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 19 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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/watsonx-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 150 packages
Packages resolved 150
Stale 54
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~837 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 ~97

Create a new encryption key in IBM Key Protect (stored in FIPS 140-2 Level 3 HSM)

NameTypeReqDescription
descriptionstringDescription of the key's purpose
extractablebooleanWhether the key material can be extracted
namestringyesName for the new key
typestringKey type: root_key (for wrapping) or standard_key (for encryption)

No output schema declared.

No examples provided.

key_protect_delete_key ~53

Delete an encryption key from IBM Key Protect (irreversible)

NameTypeReqDescription
forcebooleanForce deletion even if key has associated resources
key_idstringyesThe ID of the key to delete

No output schema declared.

No examples provided.

key_protect_get_key ~37

Get details of a specific key from IBM Key Protect

NameTypeReqDescription
key_idstringyesThe ID of the key to retrieve

No output schema declared.

No examples provided.

key_protect_list_keys ~52

List encryption keys from IBM Key Protect (HSM-backed key management on IBM Z infrastructure)

NameTypeReqDescription
limitnumberMaximum number of keys to return
offsetnumberOffset for pagination

No output schema declared.

No examples provided.

key_protect_unwrap_key ~78

Unwrap (decrypt) data using a root key in IBM Key Protect

NameTypeReqDescription
aadarrayAdditional authentication data (must match wrap AAD)
ciphertextstringyesBase64-encoded wrapped data encryption key
key_idstringyesThe ID of the root key to use for unwrapping

No output schema declared.

No examples provided.

key_protect_wrap_key ~80

Wrap (encrypt) data using a root key in IBM Key Protect - for envelope encryption

NameTypeReqDescription
aadarrayAdditional authentication data (AAD) for AEAD encryption
key_idstringyesThe ID of the root key to use for wrapping
plaintextstringyesBase64-encoded data encryption key to wrap

No output schema declared.

No examples provided.

watsonx_chat ~59

Have a conversation with watsonx.ai chat models

NameTypeReqDescription
max_new_tokensnumber
messagesarrayyesArray of chat messages
model_idstringChat model ID
temperaturenumber

No output schema declared.

No examples provided.

watsonx_embeddings ~45

Generate text embeddings using watsonx.ai embedding models

NameTypeReqDescription
model_idstringEmbedding model ID
textsarrayyesArray of texts to embed

No output schema declared.

No examples provided.

watsonx_generate ~144

Generate text using IBM watsonx.ai foundation models (Granite, Llama, Mistral, etc.)

NameTypeReqDescription
max_new_tokensnumberMaximum number of tokens to generate
model_idstringModel ID (e.g., 'ibm/granite-3-3-8b-instruct', 'meta-llama/llama-3-70b-instruct')
promptstringyesThe prompt to send to the model
temperaturenumberTemperature for sampling (0-2)
top_knumberTop-k sampling
top_pnumberTop-p nucleus sampling

No output schema declared.

No examples provided.

watsonx_list_models ~21

List available foundation models in watsonx.ai

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

zos_connect_call_service ~93

Call a z/OS Connect service to interact with mainframe programs (CICS, IMS, batch). Requires ZOS_CONNECT_URL to be configured.

NameTypeReqDescription
operationstringOperation/method to invoke (e.g., GET, POST)
payloadobjectJSON payload to send to the mainframe service
service_namestringyesName of the z/OS Connect service to call

No output schema declared.

No examples provided.

zos_connect_get_service_info ~43

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

NameTypeReqDescription
service_namestringyesName of the z/OS Connect service

No output schema declared.

No examples provided.

zos_connect_list_services ~35

List available z/OS Connect services (RESTful APIs to mainframe programs). Requires ZOS_CONNECT_URL to be configured.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

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

io.github.ExpertVagabond/watsonx is an MCP server listed in the public MCP registry as io.github.ExpertVagabond/watsonx. IBM watsonx.ai MCP server for Claude integration. This page covers its npm package (watsonx-mcp-server).

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

io.github.ExpertVagabond/watsonx 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/watsonx MCP server expose?

io.github.ExpertVagabond/watsonx exposes 13 tools: watsonx_generate, watsonx_list_models, watsonx_embeddings, watsonx_chat, key_protect_list_keys, and 8 more. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.

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

io.github.ExpertVagabond/watsonx 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/watsonx MCP server under?

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