Semgrep vs io.github.invigil/invigil
Semgrep is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.invigil/invigil is an MCP server published by invigil. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  io.github.invigil/invigil | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.1 Downloads/month (PyPI): 191 Downloads/week (PyPI): 43 Forks (GitHub): 4 Stars (GitHub): 1 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 | io.github.invigil/invigil |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.semgrep.ai/mcp) | On your machine (invigil) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/invigil/invigil |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 h ago, requires a key | no 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
MCP server for using Semgrep to scan code for security vulnerabilities.
io.github.invigil/invigil
Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.
How to run each
Semgrep As a remote MCP server
claude mcp add --transport http semgrep https://mcp.semgrep.ai/mcpio.github.invigil/invigil As a local MCP server: PyPI package
claude mcp add --transport stdio invigil -- uvx --from "invigil[mcp]" invigil mcpCommands 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 io.github.invigil/invigil 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: io.github.invigil/invigil · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.