Hitachi VSP 360 (Community)
NPM · VSP360-MCP
Community MCP server for the Hitachi VSP 360 REST API: alerts, inventory, capacity and performance.
Available components
Last scanned (6 hours ago)
Scores higher than 72% of npm servers
Category Monitoring and Observability
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
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to visubramaniam/vsp360-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 26 Oct 26 −5
- Source repository: pass → fail ▼ security
- 25 Oct 26 +42
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Source repository: fail → pass ▲ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: visubramaniam/vsp360-mcp security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: unverified → pass ▲ functional
- Dependency health: unverified → 0.86 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.30 → 0.1.31 functional
- 24 Oct 26 −41
- CVE-2026-109869 affects this package: high ▼ security
- CVE-2026-109841 affects this package: high ▼ security
- CVE-2026-109924 affects this package: high ▼ security
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Source repository: pass → fail ▼ security
- Provenance: pass → fail ▼ security
- Known CVEs: pass → fail ▼ security
- The attested source repository moved: visubramaniam/vsp360-mcp security
- Dependency health: 0.85 → unverified ▼ functional
- 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 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 5 Nov 2026 · Analysed npm/vsp360-mcp@0.1.31
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | visubramaniam/vsp360-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/visubramaniam/vsp360-mcp/.github/workflows/release.yml@refs/tags/v0.1.31 |
| Rekor log index | 3465653722 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6771d4cffab130e1e9603d0a3d94dfdd2b67d602e9a1f79c00f74adf9f57c53eb028a419f503d66d94cd54633e65fc5610e871212874ba3ffedf817df |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
vsp360_call_operation ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
vsp360_describe_operation ~95
Show everything needed to call one VSP 360 operation: method and path, required permissions and prerequisites, parameters, request body schema and response schema.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | 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. |
No output schema declared.
No examples provided.
vsp360_list_operations ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · vsp360-mcp
claude mcp add visubramaniam-vsp360-mcp -- npx -y vsp360-mcp
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.