Ext Ops Panel
Open dashboard
Comparison

Semgrep vs plugin-security-checker

Semgrep is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). plugin-security-checker is a plugin bundle for AI coding tools published by Diego Consolini. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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

Where each is published
MarketplaceSemgrepplugin-security-checker
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace diegocconsolini/claudeskillcollection Not listed Listed
Version: 3.2.0
Forks (GitHub): 0
Stars (GitHub): 7
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

Semgrep vs plugin-security-checker
FactSemgrepplugin-security-checker
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub7
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.semgrep.ai/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)8Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/diegocconsolini/claudeskillcollection
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)Responded 39 h ago, requires a keyno remote endpoint we check

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

In its own words, on Docker MCP Catalog:

MCP server for using Semgrep to scan code for security vulnerabilities.

plugin-security-checker

In its own words, on Community GitHub marketplaces:

Advanced security scanner for Claude Code plugins with 91 specialized pattern detection agents. Performs static code analysis using IntelligentOrchestrator with consensus voting, AccuracyCache shared learning, and MITRE ATT&CK/ATLAS framework mapping. Detects vulnerabilities, code obfuscation, hardcoded credentials, and security anti-patterns. Successfully scanned 987 real-world plugins with 100% accuracy. Includes adaptive routing, auto-evolving rules, and comprehensive reporting.

How to run each

Semgrep As a remote MCP server

Claude Code
claude mcp add --transport http semgrep https://mcp.semgrep.ai/mcp

plugin-security-checker As a Claude Code plugin

Claude Code
/plugin marketplace add diegocconsolini/claudeskillcollection
/plugin install plugin-security-checker@security-compliance-marketplace

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Semgrep has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of plugin-security-checker 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: plugin-security-checker · 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.

Where the data comes from: how the catalog is built