Developer · Local MCP server
Cybersec Toolkit
Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.26zl/cybersec-toolkit- Version
- 1.3.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-24
- Updated
- 2026-09-24
- Publisher
- 26zl (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/26zl) · how
- Repository
- github.com/26zl/cybersec-toolkit
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/26zl/cybersec-toolkit:1.3.0 | - | stdio |
How to connect Cybersec Toolkit
Cybersec Toolkit runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/26zl/cybersec-toolkit:1.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e CYBERSEC_MCP_ALLOW_EXTERNAL -e CYBERSEC_MCP_ALLOW_SCRIPTS ghcr.io/26zl/cybersec-toolkit:1.3.0. It reads these environment variables: CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"cybersec-toolkit": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CYBERSEC_MCP_ALLOW_EXTERNAL",
"-e",
"CYBERSEC_MCP_ALLOW_SCRIPTS",
"ghcr.io/26zl/cybersec-toolkit:1.3.0"
],
"env": {
"CYBERSEC_MCP_ALLOW_EXTERNAL": "<value>",
"CYBERSEC_MCP_ALLOW_SCRIPTS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| CvinbioSearch professional profiles from the CVin.Bio talent database. | Local · stdio |
| CvserverLive US options chains with Greeks and IV, a screener, SQL, and FMP fundamentals. | Remote · HTTPLive check: sign-in required |
| CyberLensSecurity scanning for websites, public repositories, and Open CLAW skills. | Local · stdio |
| Cybersec MCPCybersecurity MCP server: 323 prompts + 7 workflows for red team, blue team, SOC, cloud, OSINT. | Local · stdio |
| Cybersecurity Threat Intelligence MCPCVE search, vulnerability database, EPSS exploit prediction, KEV, IP reputation & threat feed. | Remote · HTTPLive check: ✗ no handshake |
| Cybersecurity Vulnerability IntelCVE lookup via NIST NVD, CISA KEV, EPSS, and MITRE ATT&CK. 7 tools. | Remote · HTTPLive check: ✗ no handshake |
| CyberSPFAssess a domain, IP or ASN: mail and DNS security, certificates, routing and a report card. | Local · stdio |
| Cygnus Ssh MCPSSH-based MCP control of remote Linux, macOS, and Windows servers -- 46 purpose-built tools. | Local · stdio |