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.rafaelgaspar/longhorn-mcp

NPM · LONGHORN-MCP · SCANNED AUG 26

MCP server for the Longhorn distributed storage manager API, with a --read-only mode.

Available components

+3 this week 82 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 →

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 5 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 11 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 8913 tokens (~86/item across 103 items; 103 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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
  • 10% 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 16 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 104 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
Install

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

# add to Claude Code
claude mcp add rafaelgaspar-longhorn-mcp -- npx -y longhorn-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "rafaelgaspar-longhorn-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "longhorn-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rafaelgaspar-longhorn-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "longhorn-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rafaelgaspar-longhorn-mcp -- npx -y longhorn-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rafaelgaspar-longhorn-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "longhorn-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rafaelgaspar-longhorn-mcp --command npx --arg -y --arg longhorn-mcp
# ~/.hermes/config.yaml
mcp_servers:
  rafaelgaspar-longhorn-mcp:
    command: "npx"
    args: ["-y", "longhorn-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rafaelgaspar-longhorn-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "longhorn-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rafaelgaspar-longhorn-mcp -t stdio -c npx -a -y longhorn-mcp
// mcp.json
{
  "mcpServers": {
    "rafaelgaspar-longhorn-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "longhorn-mcp"
      ]
    }
  }
}
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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

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

  • 23 Aug 26 +1

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

  • 21 Aug 26 +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.

  • 19 Aug 26 +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.

  • 17 Aug 26 +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.

  • 15 Aug 26 +12
    • Known CVEs: unverified → pass security
    • Dependency health: unverified → 1.00 functional
  • 14 Aug 26 0
    • Known CVEs: unverified → pass security
    • Stability: unverified → 0.03 functional
    • Dependency health: unverified → 1.00 functional
    • Package version: 0.1.3 → 0.1.6 functional
    • Package version: 0.1.3 → 0.1.5 functional
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 26 Aug 2026 · Analysed npm/longhorn-mcp@0.1.6

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.6
Rekor log index 2465110262
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:9d016575fe300c72a69cdc79cec6fdea9586d27105a2d9f1cd042bc03e6968dd016ee27756063f614a7f54bc1e97dc8521e47b3e86b2c2ee1fe3e1557
Dependencies 5 packages
Packages resolved 5
Tree resolution Complete
MCP tools · 103 exposed · ~7,705 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.

Tool Tokens
backingimage_backup_create ~115

Create a backup of a backing image. Longhorn does not publish a dedicated input schema for this action in /v1/schemas — use longhorn_describe_resource_type('backingImage') to check the deployed version's exact body shape, or pass fields via extra. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

NameTypeReqDescription
extraobjectAdditional Longhorn fields, merged verbatim into the request body.
namestringyes

No output schema declared.

No examples provided.

backingimage_cleanup ~92

Clean up backing image file copies on the given disks. 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.12.1/advanced-resources/backing-image/

NameTypeReqDescription
disksarrayyes
namestringyes

No output schema declared.

No examples provided.

backingimage_create ~182

Create a new backing image. With sourceType "download", Longhorn fetches `parameters.url` server-side from its own network position — only use with a URL the user has explicitly provided and trusts. 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.12.1/advanced-resources/backing-image/

NameTypeReqDescription
extraobjectAdditional Longhorn fields, merged verbatim into the request body.
namestringyes
parametersobjectyesSource-type-specific parameters (e.g. { url } for "download").
sourceTypestringyese.g. "download", "upload", "export-from-volume", "restore", "clone".

No output schema declared.

No examples provided.

backingimage_delete ~79

Delete a backing image. 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.12.1/advanced-resources/backing-image/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backingimage_get ~48

Get a single backing image by name. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backingimage_list ~39

List Longhorn backing images. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

backingimage_update_min_copies ~66

Update the minimum number of ready copies required for a backing image. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

NameTypeReqDescription
minNumberOfCopiesintegeryes
namestringyes

No output schema declared.

No examples provided.

backingimage_upload ~111

Trigger backing image upload. Longhorn does not publish a dedicated input schema for this action in /v1/schemas — use longhorn_describe_resource_type('backingImage') to check the deployed version's exact body shape, or pass fields via extra. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

NameTypeReqDescription
extraobjectAdditional Longhorn fields, merged verbatim into the request body.
namestringyes

No output schema declared.

No examples provided.

backup_get ~62

Get a single backup by id (plain read-only GET — available in --read-only mode). Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

backup_list ~56

List all backups across all backup volumes (plain read-only GET — available in --read-only mode). Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

backupbackingimage_delete ~86

Delete a backup backing image from the backup target. 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.12.1/advanced-resources/backing-image/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupbackingimage_get ~51

Get a single backup backing image by name. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupbackingimage_list ~45

List backed-up backing images on the backup target. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

backupbackingimage_restore ~74

Restore a backing image from the backup target. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/backing-image/

NameTypeReqDescription
dataEnginestring
namestringyes
secretstring
secretNamespacestring

No output schema declared.

No examples provided.

backuptarget_create ~70

Create a new backup target. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
extraobjectAdditional Longhorn fields, merged verbatim into the request body.
namestringyes

No output schema declared.

No examples provided.

backuptarget_delete ~84

Delete a backup target. 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.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backuptarget_get ~53

Get a single backup target by name. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backuptarget_list ~43

List configured backup targets. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

backuptarget_sync ~96

Force Longhorn to resync backup target/backup volume state. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes
syncAllBackupTargetsboolean
syncAllBackupVolumesboolean
syncBackupTargetboolean
syncBackupVolumeboolean

No output schema declared.

No examples provided.

backuptarget_update ~186

Update a backup target (e.g. backupTargetURL, credentialSecret, pollInterval). Fields you omit are left unchanged (read-merge-write under the hood — the API itself does a full replace on PUT). Repointing backupTargetURL changes where future backups go and can break restore access to existing ones. 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.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
backupTargetURLstring
credentialSecretstring
extraobjectAdditional Longhorn fields, merged verbatim into the request body.
namestringyes
pollIntervalstring

No output schema declared.

No examples provided.

backuptarget_update_name ~101

Update the backupTargetName reference on a backup target record. 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.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
backupTargetNamestringyes
namestringyes

No output schema declared.

No examples provided.

backupvolume_backup_delete ~97

Delete a specific backup belonging to a backup 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.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
backupNamestringyes
namestringyes

No output schema declared.

No examples provided.

backupvolume_backup_get ~82

Get a specific backup belonging to a backup volume via the volume-scoped action (requires write access — use backup_get for read-only introspection). Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
backupNamestringyes
namestringyes

No output schema declared.

No examples provided.

backupvolume_backup_list ~72

List backups belonging to a backup volume via the volume-scoped action (requires write access — use backup_list for read-only introspection). Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupvolume_backup_list_by_volume ~60

List backups for a backup volume, scoped by the source volume. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupvolume_delete ~88

Delete a backup volume record from the backup target. 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.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupvolume_get ~52

Get a single backup volume by name. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupvolume_list ~49

List Longhorn backup volumes (backup-target-side volume records). Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

backupvolume_sync ~57

Force a resync of a backup volume against the backup target. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

backupvolume_update ~94

Update a backup volume record. Fields you omit are left unchanged (read-merge-write under the hood — the API itself does a full replace on PUT). Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/backup-and-restore/

NameTypeReqDescription
extraobjectAdditional Longhorn fields, merged verbatim into the request body.
namestringyes

No output schema declared.

No examples provided.

engineimage_create ~91

Deploy a new Longhorn engine image. `image` is not validated against a known-good list. 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.12.1/deploy/upgrade/

NameTypeReqDescription
imagestringyes

No output schema declared.

No examples provided.

engineimage_delete ~78

Delete a Longhorn engine image. 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.12.1/deploy/upgrade/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

engineimage_get ~45

Get a single engine image by name. Longhorn docs: https://longhorn.io/docs/1.12.1/deploy/upgrade/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

engineimage_list ~36

List Longhorn engine images. Longhorn docs: https://longhorn.io/docs/1.12.1/deploy/upgrade/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

instancemanager_get ~26

Get a single instance manager by name.

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

instancemanager_list ~20

List Longhorn instance manager pods/records.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

longhorn_describe_resource_type ~52

Describe one resource type's fields and available actions via GET /v1/schemas/{id} (e.g. "volume", "backupTarget", "node").

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

longhorn_events ~21

List Kubernetes events Longhorn has recorded against its own resources.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

longhorn_list_resource_types ~34

List every resource type Longhorn's manager API exposes, self-described at runtime via GET /v1/schemas.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

longhorn_list_tags ~59

List node/disk/backing-image tags known to Longhorn, optionally filtered by type. Longhorn docs: https://longhorn.io/docs/1.12.1/nodes-and-volumes/nodes/

NameTypeReqDescription
typestring

No output schema declared.

No examples provided.

longhorn_raw_request ~133

Escape hatch for any Longhorn API endpoint not covered by a named tool. In --read-only mode, only GET requests succeed — everything else is refused before it reaches Longhorn. GET is always safe to call freely; for POST/PUT/DELETE, treat this exactly like the destructive tools elsewhere in this server — do not call with a mutating method unless the user has explicitly authorized that specific action in this conversation.

NameTypeReqDescription
bodyobject
methodstringyes
pathstringyesPath starting with /v1/, e.g. "/v1/volumes/my-volume".

No output schema declared.

No examples provided.

node_disk_update ~145

Update the disk configuration for a node. `disks` is the raw array of Longhorn Disk objects (path, allowScheduling, storageReserved, tags, diskType, ...) — inspect the node via node_get first to see the current shape. Disabling scheduling or shrinking storageReserved on a disk can strand replicas. 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.12.1/nodes-and-volumes/nodes/

NameTypeReqDescription
disksarrayyes
namestringyes

No output schema declared.

No examples provided.

node_get ~49

Get a single Longhorn node record by name. Longhorn docs: https://longhorn.io/docs/1.12.1/nodes-and-volumes/nodes/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

node_list ~46

List Longhorn node records (scheduling state, disks, conditions). Longhorn docs: https://longhorn.io/docs/1.12.1/nodes-and-volumes/nodes/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

node_update ~156

Update a Longhorn node record (e.g. allowScheduling, evictionRequested, tags). Fields you omit are left unchanged (read-merge-write under the hood — the API itself does a full replace on PUT). `evictionRequested: true` drains all replicas/backing images off the node. 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.12.1/nodes-and-volumes/nodes/

NameTypeReqDescription
allowSchedulingboolean
evictionRequestedboolean
namestringyes
tagsarray

No output schema declared.

No examples provided.

orphan_get ~53

Get a single orphan record by id. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/data-cleanup/orphaned-data-cleanup/

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

orphan_list ~51

List orphaned replica/engine instance directories Longhorn has detected. Longhorn docs: https://longhorn.io/docs/1.12.1/advanced-resources/data-cleanup/orphaned-data-cleanup/

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

recurringjob_create ~134

Create a new Longhorn recurring job. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/scheduling-backups-and-snapshots/

NameTypeReqDescription
concurrencyintegeryes
cronstringyesCron schedule expression.
groupsarray
labelsobject
namestringyes
parametersobject
retainintegeryes
taskstringyese.g. "snapshot", "backup", "snapshot-cleanup", "snapshot-delete", "filesystem-trim", "system-backup".

No output schema declared.

No examples provided.

recurringjob_delete ~88

Delete a Longhorn recurring job. 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.12.1/snapshots-and-backups/scheduling-backups-and-snapshots/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

recurringjob_get ~55

Get a single recurring job by name. Longhorn docs: https://longhorn.io/docs/1.12.1/snapshots-and-backups/scheduling-backups-and-snapshots/

NameTypeReqDescription
namestringyes

No output schema declared.

No examples provided.

Common questions

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 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 August 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 103 tools: volume_list, volume_get, volume_create, volume_delete, volume_attach, and 98 more. Their descriptions and schemas cost roughly 7,705 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 26 August 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.