io.github.26zl/cybersec-toolkit vs io.github.certindex/certindex-mcp
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). io.github.certindex/certindex-mcp is an MCP server published by certindex. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
| Marketplace |  io.github.26zl/cybersec-toolkit |  io.github.certindex/certindex-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.0 Forks (GitHub): 16 Stars (GitHub): 84 Not marked · First seen |
Listed Version: 0.2.0 Downloads/month (PyPI): 168 Downloads/week (PyPI): 55 Forks (GitHub): 1 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
| Fact | io.github.26zl/cybersec-toolkit | io.github.certindex/certindex-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 84 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 16 (better) | 1 (worse) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | On your machine (ghcr.io/26zl/cybersec-toolkit:1.4.0) | On your machine (certindex-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 873 | Not a bundle |
| Licence (differs) | MIT AND Apache-2.0 AND CC-BY-SA-4.0 | Not stated |
| Repository (differs) | github.com/26zl/cybersec-toolkit | github.com/certindex/certindex-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR.
io.github.certindex/certindex-mcp
Certificate Transparency search for AI agents: certs, subdomains, issuance history, expiry.
How to run each
io.github.26zl/cybersec-toolkit As a local MCP server: Docker image
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-bannerio.github.certindex/certindex-mcp As a local MCP server: PyPI package
claude mcp add --env "CERTINDEX_API_KEY=<YOUR_CERTINDEX_API_KEY>" --transport stdio certindex-mcp -- uvx certindex-mcpRequires: CERTINDEX_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_EXTERNALCYBERSEC_MCP_ALLOW_SCRIPTS
Only io.github.certindex/certindex-mcp asks for
CERTINDEX_API_KEY (secret)
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: io.github.certindex/certindex-mcp · 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.