# Hitachi VSP 360 (Community) (npm · vsp360-mcp)

Community MCP server for the Hitachi VSP 360 REST API: alerts, inventory, capacity and performance.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `vsp360-mcp`
- Version: `0.1.31`
- 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-05.

- **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 94 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Cryptographically verified build provenance (signed, bound to visubramaniam/vsp360-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 558 tokens (~186/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 VSP 360 (Community) MCP server?

Hitachi VSP 360 (Community) runs locally as an npm package, launched with npx -y vsp360-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-vsp360-mcp -- npx -y vsp360-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "visubramaniam-vsp360-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vsp360-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-04 (score 82, +1)

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

### 2026-11-02 (score 81, +1)

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

### 2026-10-31 (score 80, +1)

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

### 2026-10-29 (score 79, +1)

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

### 2026-10-27 (score 78, 0)

- [functional regression] Security disclosure: pass → unverified

### 2026-10-26 (score 78, −5)

- [security regression] Source repository: pass → fail

### 2026-10-25 (score 83, +42)

- [security regression] Stability: 0.20 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [security improvement] Source repository: fail → pass
- [security improvement] Provenance: fail → pass
- [security] The attested source repository moved: visubramaniam/vsp360-mcp
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Security disclosure: unverified → pass
- [functional improvement] Dependency health: unverified → 0.86
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.30 → 0.1.31

### 2026-10-24 (score 41, −41)

- [security regression] CVE-2026-109869 affects this package: high
- [security regression] CVE-2026-109841 affects this package: high
- [security regression] CVE-2026-109924 affects this package: high
- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security regression] Source repository: pass → fail
- [security regression] Provenance: pass → fail
- [security regression] Known CVEs: pass → fail
- [security] The attested source repository moved: visubramaniam/vsp360-mcp
- [functional regression] Dependency health: 0.85 → unverified
- [functional regression] Security disclosure: pass → unverified
- [functional] Package version: 0.1.27 → 0.1.30
- [functional] Package version: 0.1.27 → 0.1.29
- [functional] Package version: 0.1.27 → 0.1.28

## MCP tools (3)

### `vsp360_list_operations` (~185 tokens)

Browse the VSP 360 REST API. With no arguments, lists the API areas (tags) and how many operations each has. With `tag` and/or `query`, lists matching operations (operationId, method, path, summary). Use this first to find the operationId you need, then vsp360_describe_operation and vsp360_call_operation. Operations marked [write] are blocked because the server runs read-only.

Input parameters:

- `limit` (integer): Maximum results for a query (default 10).
- `query` (string): What you want to do, in plain words (e.g. 'volumes with no host path', 'replication pairs status'). Ranked by BM25 relevance with a confidence rating.
- `tag` (string): API area, e.g. 'Device Registry', 'Platform Alerts', 'Users'. Case-insensitive.

### `vsp360_describe_operation` (~95 tokens)

Show everything needed to call one VSP 360 operation: method and path, required permissions and prerequisites, parameters, request body schema and response schema.

Input parameters:

- `operationId` (string, required): operationId from vsp360_list_operations
- `resourceType` (string): analyticsRunQuery only: an MQL resource type (e.g. raidPort, raidPool, vm) to list all its attributes and relations.

### `vsp360_call_operation` (~278 tokens)

Call any VSP 360 REST API operation by operationId. Authentication is handled automatically. Pass path, query and header parameters by name in `params`, and the JSON request body in `body`. Collections are paginated with limit/offset (max 100 per page); set all_pages to follow the `next` link. Binary responses (ZIP, gzip, CSV downloads) are saved to the download folder and the file path is returned. Only read operations are allowed; the server runs read-only.

Input parameters:

- `all_pages` (boolean): Follow RFC 8288 `next` links and return every page (GET collections only).
- `body`: Request body (JSON object or array) for POST/PUT/PATCH operations. For multipart uploads, the non-file form fields.
- `files` (object): Multipart uploads only: form field name -> local file path
- `max_pages` (integer): Page cap when all_pages is set (default 20).
- `operationId` (string, required)
- `params` (object): Path, query and header parameters by name, e.g. {"id": "123", "limit": 100}
- `save_to` (string): Write the response to this file instead of returning it: a file name, or a path inside the download folder. Existing files are not overwritten.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 78
- 2026-10-25: 83
- 2026-10-24: 41
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 66
- 2026-10-19: 80
- 2026-10-18: 80

## Common questions

### What is the Hitachi VSP 360 (Community) MCP server?

Hitachi VSP 360 (Community) is an MCP server listed in the public MCP registry as io.github.visubramaniam/vsp360-mcp. Community MCP server for the Hitachi VSP 360 REST API: alerts, inventory, capacity and performance. This page covers its npm package (vsp360-mcp).

### Is the Hitachi VSP 360 (Community) MCP server safe to use?

Hitachi VSP 360 (Community) scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 VSP 360 (Community) MCP server expose?

Hitachi VSP 360 (Community) exposes 3 tools: vsp360_list_operations, vsp360_describe_operation, vsp360_call_operation. Their descriptions and schemas cost roughly 558 tokens of context every time the server is loaded.

### Is the Hitachi VSP 360 (Community) MCP server still maintained?

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

Hitachi VSP 360 (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 VSP 360 (Community) MCP server?

VerifyMCP ran 15 checks on Hitachi VSP 360 (Community), covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Hitachi VSP 360 (Community): Security disclosure. 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/vsp360-mcp
- Socket report: https://socket.dev/npm/package/vsp360-mcp
- Website: https://visubramaniam.github.io/vsp360-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/visubramaniam-vsp360-mcp/vsp360-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/visubramaniam-vsp360-mcp/vsp360-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/visubramaniam-vsp360-mcp/vsp360-mcp.json
- HTML version of this page: https://verifymcp.io/servers/visubramaniam-vsp360-mcp/vsp360-mcp