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.daleweaver1981/cockpit-mcp

NPM · COCKPIT-MCP · SCANNED SEP 20

40 AI prompts + self-hosted ops dashboard for homelab and small-team sysadmins

Available components

0 this week 64 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 → 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
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 119 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 86 tokens (~17/item across 5 items; 0 tools + 5 resources), lean.Pass
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety25
  • Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • An AI judge read all 1 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
Install

How do I install the io.github.daleweaver1981/cockpit-mcp server?

io.github.daleweaver1981/cockpit-mcp runs locally as an npm package, launched with npx -y cockpit-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 · cockpit-mcp

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

  • 19 Sept 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.

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 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.

  • 12 Sept 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.

  • 10 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/cockpit-mcp@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

The sandbox run completed and this package exposed no tools.

Common questions

What is the io.github.daleweaver1981/cockpit-mcp server?

io.github.daleweaver1981/cockpit-mcp is listed in the public MCP registry as io.github.daleweaver1981/cockpit-mcp. 40 AI prompts + self-hosted ops dashboard for homelab and small-team sysadmins. This page covers its npm package (cockpit-mcp).

Is the io.github.daleweaver1981/cockpit-mcp server safe to use?

io.github.daleweaver1981/cockpit-mcp scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.daleweaver1981/cockpit-mcp server expose?

io.github.daleweaver1981/cockpit-mcp exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the io.github.daleweaver1981/cockpit-mcp server still maintained?

io.github.daleweaver1981/cockpit-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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.daleweaver1981/cockpit-mcp server under?

io.github.daleweaver1981/cockpit-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.