claude-security vs SecurityScan
claude-security is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
claude-security is a plugin bundle for AI coding tools published by 0x1337c0d3. No marketplace we read lists it any more. SecurityScan is an MCP server published by apisecurityscan.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  SecurityScan | |
|---|---|---|
| Community marketplace 0x1337c0d3/claude-security | Removed on 2026-10-18 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | claude-securityno longer listed · | SecurityScan |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (apisecurityscan.net/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) | 5 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/0x1337c0d3/claude-security | github.com/securityscan-api/securityscan-api |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (4 days ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of claude-security
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Frictionless security, compliance, and threat detection for Claude Code and Co-Work. Advanced Behavioral detection patterns catch credential exfiltration, reverse shells, prompt…
-
Security review for Claude-generated code. Pattern-based warnings on edits, LLM-powered diff review on Stop, and an agentic commit reviewer that catches injection, XSS, SSRF…
-
Aikido Security scanning for Claude Code — SAST, secrets, and IaC vulnerability detection powered by the Aikido MCP server.
-
The Harness SAST and SCA plugin for Claude Code enables Secure AI Coding, bringing real-time security into your AI-assisted development workflow. All AI-generated code is…
-
Security hardening and production-grade error handling expertise for Claude Code. Prevents OWASP Top 10 vulnerabilities (SQL injection, XSS, broken auth, secrets exposure) and…
-
Deep vulnerability scanning of your own code, run entirely inside your Claude Code session at a chosen effort tier, with every finding challenged before it is reported and the…
What each says it does
claude-security
Security toolkit for Claude Code — autonomous scanning (SAST, secrets, dependency audits) plus real-time prompt injection defense.
SecurityScan
Scan GitHub-hosted AI skills for vulnerabilities: prompt injection, malware, OWASP LLM Top 10.
How to run each
claude-security
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SecurityScan As a remote MCP server
claude mcp add --transport http securityscan https://apisecurityscan.net/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SecurityScan 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: claude-security · What it can do: SecurityScan · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.