sql-armor vs Scout Security
sql-armor is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
sql-armor is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. Scout Security is an MCP server published by Varpost. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  Scout Security | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.7 Downloads/month (PyPI): 121 Downloads/week (PyPI): 23 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 | sql-armorno longer listed · | Scout Security |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (scout-security) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/varpost/scout |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
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 sql-armor
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Security auditor and hardener for vibe-coded projects. 170+ vulnerability checks across 24 categories including injection, XSS, auth bypass, IDOR, Supabase RLS, prompt injection…
-
PreToolUse security reminder hook for Claude Code. Catches 12 common security anti-patterns in Edit/Write/MultiEdit operations BEFORE they happen — command injection (exec…
-
Finds authorization holes in Next.js + Supabase apps and live Supabase databases. No API key.
-
Semgrep catches security vulnerabilities in real-time and guides Claude to write secure code from the start.
-
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…
-
Veto — SQL Safety & Cost Oracle
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
What each says it does
sql-armor
Detect SQL injection vulnerabilities and fix queries
Scout Security
Deterministic, zero-token security scanner your AI agent calls to find and re-verify issues.
How to run each
sql-armor
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Scout Security As a local MCP server: PyPI package
claude mcp add --transport stdio scout -- uvx --from "scout-security[mcp]" scout-security scout-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: sql-armor · What it can do: Scout Security · 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.