Semgrep vs io.github.hellosg/coderegistry
Semgrep is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.hellosg/coderegistry is an MCP server published by hellosg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 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.hellosg/coderegistry |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.semgrep.ai/mcp) | Remote server (integrator.app.thecoderegistry.com/api/ai/router) |
| Transport | Streamable HTTP | Streamable HTTP |
| 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/the-code-registry/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | not checked yet | not checked yet |
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.hellosg/coderegistry
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.
How to run each
Semgrep
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.hellosg/coderegistry As a remote MCP server
claude mcp add --transport http coderegistry https://integrator.app.thecoderegistry.com/api/ai/routerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.hellosg/coderegistry 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.hellosg/coderegistry · 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.