Ext Ops Panel
Open dashboard
Comparison

drbinary-chat-plugin vs io.github.26zl/cybersec-toolkit

drbinary-chat-plugin is a plugin bundle for AI coding tools published by Deepbits Technology Inc.. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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). As of our marketplace pass on 2026-10-18. 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
Marketplacedrbinary-chat-pluginio.github.26zl/cybersec-toolkit
Community marketplace deepbitstechnology/claude-plugins Listed
Version: 1.1.0
Forks (GitHub): 5
Stars (GitHub): 49
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
Forks (GitHub): 13
Stars (GitHub): 76
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

drbinary-chat-plugin vs io.github.26zl/cybersec-toolkit
Factdrbinary-chat-pluginio.github.26zl/cybersec-toolkit
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)49 (worse)76 (better)
Forks (GitHub) (differs)5 (worse)13 (better)
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (mcp.deepbits.com/mcp)On your machine (ghcr.io/26zl/cybersec-toolkit:1.4.0)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)11873
Licence (differs)Apache-2.0MIT AND Apache-2.0 AND CC-BY-SA-4.0
Repository (differs)github.com/deepbitstechnology/claude-pluginsgithub.com/26zl/cybersec-toolkit
Changes in the last 7 days (differs)26
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

drbinary-chat-plugin

In its own words, on Community GitHub marketplaces:

Local cyber security assistant for PC issue detection, malware analysis, and system scanning

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.

How to run each

drbinary-chat-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add deepbitstechnology/claude-plugins
/plugin install drbinary-chat-plugin@deepbits

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

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

The marketplaces of drbinary-chat-plugin publish no settings it asks for, so we do not compare settings.

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

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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