Ramparts Security Scanner vs xss-shield
xss-shield is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
Ramparts Security Scanner is an MCP server published by highflame-ai. Marketplaces we read that list it: 1 (Docker MCP Catalog). xss-shield is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-28. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1ddf4303800e Forks (GitHub): 20 Pulls (Docker Hub): 35 636 Stars (Docker Hub): 0 Stars (GitHub): 98 Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 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 | Ramparts Security Scanner | xss-shieldno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 98 | 3 |
| Pulls (Docker Hub) (differs) | 35 636 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 20 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/ramparts) | On your machine (@barnburner121/plugin-hub-mcp) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/getjavelin/ramparts | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
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 xss-shield
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Comprehensive security scanner for vulnerabilities and OWASP Top 10 issues
-
Security scanning and vulnerability auditing following OWASP Top 10 guidelines with automated remediation
-
Client-side web security scanner — detects secrets, vulnerable JS libraries, misconfigurations, XSS sinks, CORS issues, and more
-
claude-code-vulnerability-check
Detect CVE (Common Vulnerability Exposure) in PHP / JS project. Auto apply minor fixes and patch Alert on necessity of major update (prevent breaking changes)
-
DevsForge comprehensive security vulnerability scanner with automated remediation suggestions.
-
Security best practices and vulnerability detection
What each says it does
Ramparts Security Scanner
A comprehensive security scanner for MCP servers with YARA rules and static analysis capabilities.
xss-shield
Scan for XSS vulnerabilities in templates and frontend code
How to run each
Ramparts Security Scanner As a local MCP server: Docker image
claude mcp add --transport stdio ramparts -- docker run -i --rm mcp/ramparts
xss-shield
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of xss-shield publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of xss-shield publish no settings it asks for, so we do not compare settings.
What it can do: Ramparts Security Scanner · What it can do: xss-shield · 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.