com.seoapi/petalbot vs io.github.26zl/cybersec-toolkit
com.seoapi/petalbot is an MCP server published by seoapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-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
| Marketplace |  com.seoapi/petalbot |  io.github.26zl/cybersec-toolkit |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 1.4.0 Forks (GitHub): 17 Stars (GitHub): 85 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 | com.seoapi/petalbot | io.github.26zl/cybersec-toolkit |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 85 |
| Forks (GitHub) (differs) | No figure on GitHub | 17 |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Remote server (petalbot.seoapi.com/mcp) | On your machine (ghcr.io/26zl/cybersec-toolkit:1.4.0) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 873 |
| Licence (differs) | Not stated | MIT AND Apache-2.0 AND CC-BY-SA-4.0 |
| Repository (differs) | Not stated | github.com/26zl/cybersec-toolkit |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | no 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
com.seoapi/petalbot
Validate whether an IP address belongs to PetalBot. Remote MCP server exposing a validate_ip tool.
io.github.26zl/cybersec-toolkit
Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR.
How to run each
com.seoapi/petalbot As a remote MCP server
claude mcp add --transport http petalbot https://petalbot.seoapi.com/mcpio.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-bannerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.seoapi/petalbot has a remote endpoint we check. How we check endpoints
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 com.seoapi/petalbot publish no settings it asks for, so we do not compare settings.
What it can do: com.seoapi/petalbot · What it can do: io.github.26zl/cybersec-toolkit · 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.