xss-shield vs SecScan
xss-shield is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
xss-shield is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. SecScan is an MCP server published by secscan.us. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 | ||
|---|---|---|
| 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: 1.1.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 | xss-shieldno longer listed · | SecScan |
|---|---|---|
| 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) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (secscan.us/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| 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 | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 43 h ago returned HTTP 405 |
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.
-
OWASP-style review: injection, auth, data exposure, weak crypto. Severity-ranked with file:line + fix.
-
Prevents Cross-Site Scripting attacks through input sanitization, output encoding, and Content Security Policy. Use when handling user-generated content, implementing rich text…
-
Security audit patterns for PHP applications following OWASP guidelines. Covers XXE, SQL injection, XSS, CSRF detection, CVSS v3.1 scoring, and secure coding practices. By…
-
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.
What each says it does
xss-shield
Scan for XSS vulnerabilities in templates and frontend code
SecScan
Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.
How to run each
xss-shield
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SecScan As a remote MCP server
claude mcp add --transport http secscan https://secscan.us/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SecScan 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: xss-shield · What it can do: SecScan · 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.