Ext Ops Panel
Open dashboard
Comparison

io.github.26zl/cybersec-toolkit vs Cork

io.github.26zl/cybersec-toolkit is an MCP server published by 26zl. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Cork is an MCP server published by WYRE-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.26zl/cybersec-toolkitCork
Official MCP Registry Listed
Version: 1.4.0
Forks (GitHub): 17
Stars (GitHub): 85
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.26zl/cybersec-toolkit vs Cork
Factio.github.26zl/cybersec-toolkitCork
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)85 (better)0 (worse)
Forks (GitHub) (differs)17 (better)0 (worse)
Last release (differs)2026-10-16 (worse)2026-10-22 (better)
Where it runs (differs)On your machine (ghcr.io/26zl/cybersec-toolkit:1.4.0)On your machine (ghcr.io/wyre-ai/cork-mcp:v1.0.1)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 04, secrets among them: 1
Parts of the bundle (differs)873Not a bundle
Licence (differs)MIT AND Apache-2.0 AND CC-BY-SA-4.0Not stated
Repository (differs)github.com/26zl/cybersec-toolkitgithub.com/wyre-ai/cork-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.26zl/cybersec-toolkit

In its own words, on Official MCP Registry:

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

Cork

In its own words, on Official MCP Registry:

MCP server for Cork's cyber-insurance API for MSPs.

How to run each

io.github.26zl/cybersec-toolkit As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio cybersec-toolkit -- docker run -i --rm --entrypoint uv --security-opt no-new-privileges ghcr.io/26zl/cybersec-toolkit:1.4.0 run --directory mcp_server fastmcp run server.py --transport stdio --no-banner

Cork As a local MCP server: Docker image

Claude Code
claude mcp add --env "CORK_API_KEY=<YOUR_CORK_API_KEY>" --transport stdio cork-mcp -- docker run -i --rm -e CORK_API_KEY ghcr.io/wyre-ai/cork-mcp:v1.0.1

Requires: CORK_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.26zl/cybersec-toolkit asks for

  • CYBERSEC_MCP_ALLOW_EXTERNAL
  • CYBERSEC_MCP_ALLOW_SCRIPTS

Only Cork asks for

  • AUTH_MODE
  • CORK_API_KEY (secret)
  • LOG_LEVEL
  • MCP_TRANSPORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.26zl/cybersec-toolkit · What it can do: Cork · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built