stackhawk-hawkscan vs TLS Radar
stackhawk-hawkscan is a plugin bundle for AI coding tools published by stackhawk. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). TLS Radar is an MCP server published by tlsradar.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  stackhawk-hawkscan |  TLS Radar |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 2.6.0 Forks (GitHub): 3 Stars (GitHub): 16 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 2.6.0 Forks (GitHub): 3 Stars (GitHub): 16 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.1 Forks (GitHub): 0 Stars (GitHub): 3 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 | stackhawk-hawkscan | TLS Radar |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 16 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (tlsradar.com/api/v1/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/stackhawk/agent-skills | github.com/tls-radar/tlsradar-claude-plugin |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (2 days ago) |
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
stackhawk-hawkscan
Configure, run, and interpret HawkScan DAST results inside Claude Code. Generates stackhawk.yml configs, runs scans via CLI or Docker, and transforms security findings into prioritized fix tasks for your coding agent.
TLS Radar
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
How to run each
stackhawk-hawkscan As a Claude Code plugin
/plugin install stackhawk-hawkscan@claude-plugins-officialTLS Radar As a remote MCP server
claude mcp add --transport http tlsradar https://tlsradar.com/api/v1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TLS Radar 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
Neither one's marketplaces publish the settings it asks for.
What it can do: stackhawk-hawkscan · What it can do: TLS Radar · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.