Semgrep vs squirrelscan
Semgrep is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). squirrelscan is a plugin bundle for AI coding tools published by squirrelscan. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 |  squirrelscan | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace squirrelscan/squirrelscan | Not listed | Listed Version: not stated 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 | Semgrep | squirrelscan |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.semgrep.ai/mcp) | Remote server (mcp.squirrelscan.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/squirrelscan/skills |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | Responded 14 h ago, requires a key | Responded 34 h ago, requires a key |
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
Semgrep
MCP server for using Semgrep to scan code for security vulnerabilities.
squirrelscan
Website QA tool built for coding agents (Claude Code, Cursor). 300+ rules across SEO, performance, security, accessibility & agent experience: audit from the CLI, fix findings in code, publish reports, and connect over MCP.
How to run each
Semgrep As a remote MCP server
claude mcp add --transport http semgrep https://mcp.semgrep.ai/mcpsquirrelscan As a Claude Code plugin
/plugin marketplace add squirrelscan/squirrelscan
/plugin install squirrelscan@squirrelscanCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of squirrelscan publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Semgrep · What it can do: squirrelscan · 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.