# io.github.26zl/cybersec-toolkit (oci · ghcr.io/26zl/cybersec-toolkit)

Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR.

- Trust score: 0/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

> **Recent critical change**: CVE-2026-114616 affects this package (2026-10-31). See the changelog below before you install this server.

## Components

- oci · `ghcr.io/26zl/cybersec-toolkit`: 0/100 (this document), [markdown](https://verifymcp.io/servers/26zl-cybersec-toolkit/ghcr-io-26zl-cybersec-toolkit.md), [page](https://verifymcp.io/servers/26zl-cybersec-toolkit/ghcr-io-26zl-cybersec-toolkit)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/26zl/cybersec-toolkit`
- Version: `1.4.0`
- 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-04.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to 26zl/cybersec-toolkit).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the io.github.26zl/cybersec-toolkit MCP server?

io.github.26zl/cybersec-toolkit runs locally as a container image, launched with docker run --rm -i -e CYBERSEC_MCP_ALLOW_EXTERNAL -e CYBERSEC_MCP_ALLOW_SCRIPTS ghcr.io/26zl/cybersec-toolkit:1.4.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add 26zl-cybersec-toolkit -- docker run --rm -i -e CYBERSEC_MCP_ALLOW_EXTERNAL -e CYBERSEC_MCP_ALLOW_SCRIPTS ghcr.io/26zl/cybersec-toolkit:1.4.0
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "26zl-cybersec-toolkit": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CYBERSEC_MCP_ALLOW_EXTERNAL",
        "-e",
        "CYBERSEC_MCP_ALLOW_SCRIPTS",
        "ghcr.io/26zl/cybersec-toolkit:1.4.0"
      ]
    }
  }
}
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "26zl-cybersec-toolkit": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CYBERSEC_MCP_ALLOW_EXTERNAL",
        "-e",
        "CYBERSEC_MCP_ALLOW_SCRIPTS",
        "ghcr.io/26zl/cybersec-toolkit:1.4.0"
      ]
    }
  }
}
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add 26zl-cybersec-toolkit -- docker run --rm -i -e CYBERSEC_MCP_ALLOW_EXTERNAL -e CYBERSEC_MCP_ALLOW_SCRIPTS ghcr.io/26zl/cybersec-toolkit:1.4.0
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "26zl-cybersec-toolkit": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "CYBERSEC_MCP_ALLOW_EXTERNAL",
        "-e",
        "CYBERSEC_MCP_ALLOW_SCRIPTS",
        "ghcr.io/26zl/cybersec-toolkit:1.4.0"
      ],
      "enabled": true
    }
  }
}
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  26zl-cybersec-toolkit:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "CYBERSEC_MCP_ALLOW_EXTERNAL", "-e", "CYBERSEC_MCP_ALLOW_SCRIPTS", "ghcr.io/26zl/cybersec-toolkit:1.4.0"]
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "26zl-cybersec-toolkit": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CYBERSEC_MCP_ALLOW_EXTERNAL",
        "-e",
        "CYBERSEC_MCP_ALLOW_SCRIPTS",
        "ghcr.io/26zl/cybersec-toolkit:1.4.0"
      ]
    }
  }
}
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "26zl-cybersec-toolkit": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "CYBERSEC_MCP_ALLOW_EXTERNAL",
        "-e",
        "CYBERSEC_MCP_ALLOW_SCRIPTS",
        "ghcr.io/26zl/cybersec-toolkit:1.4.0"
      ]
    }
  }
}
```

This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-10-31 (score 0, 0)

- [critical regression] CVE-2026-114616 affects this package: high
- [critical regression] CVE-2026-114615 affects this package: high

### 2026-10-30 (score 0, 0)

- [critical regression] CVE-2026-111497 affects this package: high

### 2026-10-28 (score 0, 0)

- [critical regression] CVE-2026-96760 affects this package: high

### 2026-10-21 (score 0, −20)

- [critical regression] GHSA-6q48-6c7w-9gw2 affects this package: none
- [critical regression] Score status: scored → failed
- [critical] Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0.
- [security improvement] CVE-2026-95210 no longer affects this package
- [security improvement] CVE-2026-88647 no longer affects this package

### 2026-10-15 (score 20)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities. The full working is on the page: https://verifymcp.io/servers/26zl-cybersec-toolkit/ghcr-io-26zl-cybersec-toolkit#diagnostics

## Score history

- 2026-11-04: 0
- 2026-11-03: 0
- 2026-11-02: 0
- 2026-11-01: 0
- 2026-10-31: 0
- 2026-10-30: 0
- 2026-10-29: 0
- 2026-10-28: 0
- 2026-10-27: 0
- 2026-10-26: 0
- 2026-10-25: 0
- 2026-10-24: 0
- 2026-10-23: 0
- 2026-10-22: 0
- 2026-10-21: 0
- 2026-10-20: 20
- 2026-10-19: 20
- 2026-10-18: 20
- 2026-10-17: 20
- 2026-10-16: 20
- 2026-10-15: 20

## Common questions

### What is the io.github.26zl/cybersec-toolkit MCP server?

io.github.26zl/cybersec-toolkit is an MCP server listed in the public MCP registry as io.github.26zl/cybersec-toolkit. Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR. This page covers its container image (ghcr.io/26zl/cybersec-toolkit).

### Is the io.github.26zl/cybersec-toolkit MCP server still maintained?

io.github.26zl/cybersec-toolkit is still listed as active in the MCP registry. We last reached this channel on 4 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 io.github.26zl/cybersec-toolkit MCP server under?

io.github.26zl/cybersec-toolkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/26zl/cybersec-toolkit
- Repository: https://github.com/26zl/cybersec-toolkit
- Changelog RSS feed: https://verifymcp.io/servers/26zl-cybersec-toolkit/ghcr-io-26zl-cybersec-toolkit.xml
- Changelog JSON feed: https://verifymcp.io/servers/26zl-cybersec-toolkit/ghcr-io-26zl-cybersec-toolkit.json
- HTML version of this page: https://verifymcp.io/servers/26zl-cybersec-toolkit/ghcr-io-26zl-cybersec-toolkit