skill-security-check vs io.github.securityscan-api/securityscan
skill-security-check is a plugin bundle for AI coding tools published by aliksir. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.securityscan-api/securityscan is an MCP server published by securityscan-api. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  skill-security-check |  io.github.securityscan-api/securityscan |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.5.0 Forks (GitHub): 2 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 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 | skill-security-check | io.github.securityscan-api/securityscan |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (securityscan-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aliksir/claude-code-skill-security-check | github.com/securityscan-api/securitystack-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 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
skill-security-check
Security audit plugin that scans Claude Code skills, hooks, and MCP configurations for threats. Detects 37 attack patterns including prompt injection, data exfiltration, supply chain attacks (ToxicSkills/ClawHavoc), credential theft, reverse shells, backdoor persistence, API endpoint hijacking, Unicode homoglyph attacks, and context window poisoning. Includes runtime hooks for Bash command validation and MCP response inspection.
io.github.securityscan-api/securityscan
Security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout.
How to run each
skill-security-check As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install skill-security-check@claude-communityio.github.securityscan-api/securityscan As a local MCP server: PyPI package
claude mcp add --transport stdio securityscan -- uvx securityscan-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: skill-security-check · What it can do: io.github.securityscan-api/securityscan · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.