# Hitachi raidcom command builder (Community) (npm · raidcom-mcp)

Builds and checks Hitachi raidcom commands and scripts. Build-only: never contacts a storage system.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- npm · `raidcom-mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/visubramaniam-raidcom-mcp/raidcom-mcp.md), [page](https://verifymcp.io/servers/visubramaniam-raidcom-mcp/raidcom-mcp)

## Channel facts

- Registry: `npm`
- Package: `raidcom-mcp`
- Version: `0.1.8`
- 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-11-06.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to visubramaniam/raidcom-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2509 tokens (~228/item across 11 items; 8 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Hitachi raidcom command builder (Community) MCP server?

Hitachi raidcom command builder (Community) runs locally as an npm package, launched with npx -y raidcom-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add visubramaniam-raidcom-mcp -- npx -y raidcom-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "visubramaniam-raidcom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "raidcom-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "visubramaniam-raidcom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "raidcom-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add visubramaniam-raidcom-mcp -- npx -y raidcom-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add visubramaniam-raidcom-mcp --command npx --arg -y --arg raidcom-mcp
```

### Hermes

```yaml
mcp_servers:
  visubramaniam-raidcom-mcp:
    command: "npx"
    args: ["-y", "raidcom-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "visubramaniam-raidcom-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "raidcom-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add visubramaniam-raidcom-mcp -t stdio -c npx -a -y raidcom-mcp
```

### Other

```json
{
  "mcpServers": {
    "visubramaniam-raidcom-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "raidcom-mcp"
      ]
    }
  }
}
```

## 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-11-05 (score 85, +1)

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

### 2026-11-03 (score 84, +1)

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

### 2026-11-01 (score 83, +1)

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

### 2026-10-30 (score 82, +1)

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

### 2026-10-28 (score 81)

First indexed and scored.

## MCP tools (8)

### `raidcom_list_commands` (~226 tokens)

Find raidcom commands

Find raidcom commands. Use this first when you do not know the exact command name. With no arguments, lists every object (ldev, lun, host_grp, pool, ...) with the actions available on it. With `query` (plain words, e.g. "map a volume to a host group", "grow a pool", "show free ldev ids"), ranks matching commands and rates the confidence of the top result. With `action` and/or `object`, lists exactly those commands. Then call raidcom_describe_command, or raidcom_build_command if you already know the options.

Input parameters:

- `action` (string): Only this action: add, delete, get, modify, extend, initialize, set, reset, ...
- `limit` (integer): Maximum results for a query (default 10).
- `object` (string): Only this object: ldev, lun, host_grp, hba_wwn, pool, dp_pool, port, parity_grp, ...
- `query` (string): What you want to do, in plain words.

### `raidcom_describe_command` (~140 tokens)

Describe a raidcom command

Everything needed to build one raidcom command: what it does, which models support it, whether it is read-only, destructive or asynchronous, each syntax form, every option with the number and kind of values it takes (and the words it accepts, where it accepts only a few), and examples. Call it before raidcom_build_command when you are unsure which options a command needs or which of its syntax forms fits the request.

Input parameters:

- `command` (string, required): Command name, e.g. "add lun" or "raidcom get ldev".
- `option` (string): Only describe this option, e.g. "-ldev_id".

### `raidcom_build_command` (~522 tokens)

Build a raidcom command

Build one raidcom command from structured arguments and validate it. Nothing is executed and no storage system is contacted: you get command text to review and run elsewhere. Unknown options, wrong value counts, missing required options, bad port names and out-of-range LDEV, LUN, pool and serial numbers are reported as errors with a fix. Example: {"command": "add ldev", "options": {"-pool": 0, "-ldev_id": 256, "-capacity": "100G"}, "model": "vsp-one-b28", "global": {"instance": 0}} → `raidcom add ldev -pool 0 -ldev_id 256 -capacity 100G -I0`. For many similar commands use raidcom_build_script, not repeated calls. When the user asks for a command, show them the `command` from the result.

Input parameters:

- `command` (string, required): Command name: action and object, e.g. "add lun", "get ldev", "modify host_grp".
- `global` (object): Settings that apply to the whole command, not to one raidcom option.
- `model` (string): Storage model, so values are checked against its limits: vsp-one-b24, vsp-one-b26, vsp-one-b28, vsp-5000, vsp-e590, vsp-e790, vsp-e990, vsp-e1090. Aliases such as B28 or E990 work. Omit it to check a…
- `options` (object): raidcom options and their values, keyed by option name with or without the leading dash. A value is a string or number; an option that takes several values (for example -port takes a port and an opti…
- `strict` (boolean): Default true. The command catalogue is parsed from the manual, whose syntax lines are occasionally incomplete, so a "needs <option>" error can be a false alarm. If one looks wrong after reading raidc…

### `raidcom_check_command` (~271 tokens)

Check a raidcom command line

Validate and explain a raidcom command line the user already has (for example one pasted from a runbook). It is parsed, not executed: shell operators such as ; | & > are refused. Returns the normalised command, what each option means, and every problem found. Credentials after -login are dropped.

Input parameters:

- `command_line` (string, required): One raidcom command, e.g. "raidcom add lun -port CL1-A-0 -ldev_id 200 -lun_id 1".
- `model` (string): Storage model, so values are checked against its limits: vsp-one-b24, vsp-one-b26, vsp-one-b28, vsp-5000, vsp-e590, vsp-e790, vsp-e990, vsp-e1090. Aliases such as B28 or E990 work. Omit it to check a…
- `strict` (boolean): Default true. The command catalogue is parsed from the manual, whose syntax lines are occasionally incomplete, so a "needs <option>" error can be a false alarm. If one looks wrong after reading raidc…

### `raidcom_build_script` (~415 tokens)

Build a raidcom script

Build a shell script of raidcom commands from steps. Each step is a command with options, optionally repeated with `foreach` (every combination) or `zip` (values advance together), so "create LDEVs 100 to 109 in pool 0, then map each to port CL1-A" is two steps. Every expanded command is validated; the script is returned only if all of them are valid, otherwise you get the errors per step. The script checks each command's exit status, adds `raidcom get command_status` after asynchronous commands, and can lock the resource group and log in (credentials are read from RAIDCOM_USER and RAIDCOM_PASSWORD in the user's shell, never written into the script). Nothing is executed.

Input parameters:

- `description` (string): A one-line comment for the top of the script.
- `global` (object): Settings that apply to the whole command, not to one raidcom option.
- `lock_resource` (boolean): Wrap the commands in raidcom lock resource / unlock resource. Recommended for changing commands.
- `login` (boolean): Add raidcom -login / -logout using $RAIDCOM_USER and $RAIDCOM_PASSWORD.
- `model` (string): Storage model, so values are checked against its limits: vsp-one-b24, vsp-one-b26, vsp-one-b28, vsp-5000, vsp-e590, vsp-e790, vsp-e990, vsp-e1090. Aliases such as B28 or E990 work. Omit it to check a…
- `steps` (array, required)
- `strict` (boolean): Default true. The command catalogue is parsed from the manual, whose syntax lines are occasionally incomplete, so a "needs <option>" error can be a false alarm. If one looks wrong after reading raidc…

### `raidcom_list_recipes` (~147 tokens)

List raidcom recipes

Ready-made workflows: provision volumes to an FC, iSCSI or NVMe/TCP host, create or grow a pool, create a mainframe (3390) pool, extend or delete volumes, create a command device, reclaim zero pages, read-only inventory, copy groups. With no arguments lists them. With `recipe`, shows its parameters and steps. With `query`, ranks recipes by keyword. Use raidcom_build_recipe to turn one into a script.

Input parameters:

- `query` (string): Words describing the task, e.g. "new ESXi host".
- `recipe` (string): Recipe ID to show in detail, e.g. provision-fc-volumes.

### `raidcom_build_recipe` (~376 tokens)

Build a raidcom recipe script

Build the script for a recipe from its parameters (see raidcom_list_recipes). Lists such as ldev_ids accept ranges: ["100-109"]. Example: recipe provision-fc-volumes with {"pool": 0, "ldev_ids": ["100-103"], "capacity": "100G", "ports": ["CL1-A", "CL2-A"], "host_grp": "esx01", "host_mode": "VMWARE_EX", "wwns": ["210000e08b0256f8"]}. Returns the script and the individual commands. Nothing is executed.

Input parameters:

- `global` (object): Settings that apply to the whole command, not to one raidcom option.
- `lock_resource` (boolean): Wrap the commands in raidcom lock resource / unlock resource.
- `login` (boolean): Add raidcom -login / -logout using $RAIDCOM_USER and $RAIDCOM_PASSWORD.
- `model` (string): Storage model, so values are checked against its limits: vsp-one-b24, vsp-one-b26, vsp-one-b28, vsp-5000, vsp-e590, vsp-e790, vsp-e990, vsp-e1090. Aliases such as B28 or E990 work. Omit it to check a…
- `params` (object, required): Recipe parameters.
- `recipe` (string, required): Recipe ID.
- `strict` (boolean): Default true. The command catalogue is parsed from the manual, whose syntax lines are occasionally incomplete, so a "needs <option>" error can be a false alarm. If one looks wrong after reading raidc…

### `raidcom_model_limits` (~136 tokens)

Show storage model limits

Valid parameter ranges for a storage model (serial number, LDEV ID, pool ID, LU number, port names), taken from the Command Reference appendices. Without `model`, lists the models.

Input parameters:

- `model` (string): Storage model, so values are checked against its limits: vsp-one-b24, vsp-one-b26, vsp-one-b28, vsp-5000, vsp-e590, vsp-e790, vsp-e990, vsp-e1090. Aliases such as B28 or E990 work. Omit it to check a…

## Diagnostics

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

## Score history

- 2026-11-06: 85
- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81

## Common questions

### What is the Hitachi raidcom command builder (Community) MCP server?

Hitachi raidcom command builder (Community) is an MCP server listed in the public MCP registry as io.github.visubramaniam/raidcom-mcp. Builds and checks Hitachi raidcom commands and scripts. Build-only: never contacts a storage system. This page covers its npm package (raidcom-mcp).

### Is the Hitachi raidcom command builder (Community) MCP server safe to use?

Hitachi raidcom command builder (Community) scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Hitachi raidcom command builder (Community) MCP server expose?

Hitachi raidcom command builder (Community) exposes 8 tools: raidcom_list_commands, raidcom_describe_command, raidcom_build_command, raidcom_check_command, raidcom_build_script, and 3 more. Their descriptions and schemas cost roughly 2,233 tokens of context every time the server is loaded.

### Is the Hitachi raidcom command builder (Community) MCP server still maintained?

Hitachi raidcom command builder (Community) is still listed as active in the MCP registry. We last reached this channel on 6 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 Hitachi raidcom command builder (Community) MCP server under?

Hitachi raidcom command builder (Community) 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 Hitachi raidcom command builder (Community) MCP server?

VerifyMCP ran 16 checks on Hitachi raidcom command builder (Community), 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.

## Links

- npm package: https://www.npmjs.com/package/raidcom-mcp
- Socket report: https://socket.dev/npm/package/raidcom-mcp
- Repository: https://github.com/visubramaniam/raidcom-mcp
- Changelog RSS feed: https://verifymcp.io/servers/visubramaniam-raidcom-mcp/raidcom-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/visubramaniam-raidcom-mcp/raidcom-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/visubramaniam-raidcom-mcp/raidcom-mcp.json
- HTML version of this page: https://verifymcp.io/servers/visubramaniam-raidcom-mcp/raidcom-mcp