Ext Ops Panel
Open dashboard
Comparison

Shodan vs claude-bughunter

Shodan is an MCP server published by Cyreslab-AI. Marketplaces we read that list it: 1 (Docker MCP Catalog). claude-bughunter is a plugin bundle for AI coding tools published by Sachin Sharma. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
MarketplaceShodanclaude-bughunter
Docker MCP Catalog Listed
Version: sha256:f99f2d2d6955
Forks (GitHub): 12
Pulls (Docker Hub): 46 604
Stars (Docker Hub): 8
Stars (GitHub): 51
Not marked · First seen
Not listed
Community marketplace elementalsouls/claude-bughunter Not listed Listed
Version: 2.1.0
Forks (GitHub): 795
Stars (GitHub): 5 195
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

Shodan vs claude-bughunter
FactShodanclaude-bughunter
Marketplaces that list it11
Stars (GitHub) (differs)51 (worse)5 195 (better)
Pulls (Docker Hub) (differs)46 604No figure on Docker Hub
Forks (GitHub) (differs)12 (worse)795 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/cyreslab-ai-shodan)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)5Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle98
LicenceMITMIT
Repository (differs)github.com/cyreslab-ai/shodan-mcp-servergithub.com/elementalsouls/claude-bughunter
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16

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

Shodan

In its own words, on Docker MCP Catalog:

MCP server for Shodan — host/network recon, CVE and exploit lookup, InternetDB, and persistent alerts (34 tools).

claude-bughunter

In its own words, on Community GitHub marketplaces:

83-skill bug-hunting & external red-team bundle — 58 hunt-* web/vuln-class + framework skills, enterprise platform attack chains (M365/Entra, Okta, SharePoint, vCenter, SSL-VPN, APK/iOS), recon/OSINT, reporting & validation gates, Burp MCP integration. Skills auto-load by topic; 15 slash commands.

How to run each

Shodan As a local MCP server: Docker image

Claude Code
claude mcp add --env "SHODAN_API_KEY=<YOUR_SHODAN_API_KEY>" --transport stdio cyreslab-ai-shodan -- docker run -i --rm -e SHODAN_API_KEY mcp/cyreslab-ai-shodan

Requires: SHODAN_API_KEY (secret)

claude-bughunter As a Claude Code plugin

Claude Code
/plugin marketplace add elementalsouls/claude-bughunter
/plugin install claude-bughunter@elementalsouls

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

Tools each declares

The marketplaces of claude-bughunter publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of claude-bughunter publish no settings it asks for, so we do not compare settings.

What it can do: Shodan · What it can do: claude-bughunter · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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