io.github.rafaelgaspar/longhorn-mcp
NPM · LONGHORN-MCP
MCP server for the Longhorn distributed storage manager API, with a --read-only mode.
Available components
Last scanned (20 hours ago)
Scores higher than 91% of npm servers
Category Cloud Infrastructure
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 Security100
- 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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to rafaelgaspar/longhorn-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 9544 tokens (~87/item across 109 items; 109 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% 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 17 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "volume_delete" 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 110 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +39
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.83 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.1.7 → 0.1.8 functional
- 13 Oct 26 0
- Package version: 0.1.7 → 0.1.8 functional
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Package version: 0.1.7 → 0.1.8 functional
- 11 Oct 26 −41
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.7 → 0.1.8 functional
- 4 Oct 26 0
- Stability: 0.97 → pass security
- 3 Oct 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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 16 Oct 2026 · Analysed npm/longhorn-mcp@0.1.8
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 | rafaelgaspar/longhorn-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/rafaelgaspar/longhorn-mcp/.github/workflows/release.yaml@refs/tags/v0.1.8 |
| Rekor log index | 3146177958 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e0c110ff3e08415789a0aa25a2193db7fb230ecc853f7447b9b6a5db9e456a3c5a0dce6ceda2cf4d375b1913ffe157bd27643f138ce632df8a03dda62 |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
volume_snapshot_delete Delete volume snapshot ~92
Delete a snapshot of a volume. Destructive. Do not call this unless the user has explicitly authorized it in this conversation — never proactively, speculatively, or as a side effect of another task. Longhorn docs: https://longhorn.io/docs/1.13.0/snapshots-and-backups/setup-a-snapshot/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| snapshotName | string | yes | – |
No output schema declared.
No examples provided.
volume_snapshot_get Get volume snapshot ~77
Get one snapshot of a volume via the volume-scoped action (requires write access — use snapshot_get for read-only introspection). Longhorn docs: https://longhorn.io/docs/1.13.0/snapshots-and-backups/setup-a-snapshot/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| snapshotName | string | yes | – |
No output schema declared.
No examples provided.
volume_snapshot_list List volume snapshots ~68
List snapshots for a volume via the volume-scoped action (requires write access — use snapshot_list for read-only introspection). Longhorn docs: https://longhorn.io/docs/1.13.0/snapshots-and-backups/setup-a-snapshot/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
volume_snapshot_purge Purge volume snapshots ~86
Purge removed snapshots of a volume. Destructive. Do not call this unless the user has explicitly authorized it in this conversation — never proactively, speculatively, or as a side effect of another task. Longhorn docs: https://longhorn.io/docs/1.13.0/snapshots-and-backups/setup-a-snapshot/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
volume_snapshot_revert Revert volume to snapshot ~101
Revert a volume to a snapshot, discarding all changes made since. Destructive. Do not call this unless the user has explicitly authorized it in this conversation — never proactively, speculatively, or as a side effect of another task. Longhorn docs: https://longhorn.io/docs/1.13.0/snapshots-and-backups/setup-a-snapshot/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| snapshotName | string | yes | – |
No output schema declared.
No examples provided.
volume_trim_filesystem Trim volume filesystem ~52
Trim the filesystem on a volume. Longhorn docs: https://longhorn.io/docs/1.13.0/nodes-and-volumes/volumes/create-volumes/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
volume_update_setting Update a volume setting ~168
Update one of Longhorn's per-volume settings. Valid "setting" values: replicaCount, replicaAutoBalance, rebuildConcurrentSyncLimit, dataLocality, accessMode, snapshotDataIntegrity, snapshotMaxCount, snapshotMaxSize, replicaRebuildingBandwidthLimit, ublkQueueDepth, ublkNumberOfQueue, backupCompressionMethod, unmapMarkSnapChainRemoved, replicaSoftAntiAffinity, replicaZoneSoftAntiAffinity, replicaDiskSoftAntiAffinity, freezeFilesystemForSnapshot, backupTargetName, offlineReplicaRebuilding. Longhorn docs: https://longhorn.io/docs/1.13.0/nodes-and-volumes/volumes/create-volumes/
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| setting | string | yes | – |
| value | string|number|boolean | yes | – |
No output schema declared.
No examples provided.
volumeattachment_get Get volume attachment ~25
Get a single VolumeAttachment record by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
volumeattachment_list List volume attachments ~21
List Longhorn VolumeAttachment records (attachment tickets per volume).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.rafaelgaspar/longhorn-mcp server?
io.github.rafaelgaspar/longhorn-mcp runs locally as an npm package, launched with npx -y longhorn-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 · longhorn-mcp
claude mcp add rafaelgaspar-longhorn-mcp -- npx -y longhorn-mcp
What is the io.github.rafaelgaspar/longhorn-mcp server?
io.github.rafaelgaspar/longhorn-mcp is listed in the public MCP registry as io.github.rafaelgaspar/longhorn-mcp. MCP server for the Longhorn distributed storage manager API, with a --read-only mode. This page covers its npm package (longhorn-mcp).
Is the io.github.rafaelgaspar/longhorn-mcp server safe to use?
io.github.rafaelgaspar/longhorn-mcp scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 io.github.rafaelgaspar/longhorn-mcp server expose?
io.github.rafaelgaspar/longhorn-mcp exposes 109 tools: volume_list, volume_get, volume_create, volume_delete, volume_attach, and 104 more. Their descriptions and schemas cost roughly 8,336 tokens of context every time the server is loaded.
Is the io.github.rafaelgaspar/longhorn-mcp server still maintained?
io.github.rafaelgaspar/longhorn-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 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.rafaelgaspar/longhorn-mcp server under?
io.github.rafaelgaspar/longhorn-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.