io.github.notasandy/mcp-code-sanitizer vs io.github.selvage-lab/selvage
io.github.notasandy/mcp-code-sanitizer is an MCP server published by notasandy. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.selvage-lab/selvage is an MCP server published by selvage-lab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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.notasandy/mcp-code-sanitizer |  io.github.selvage-lab/selvage |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (PyPI): 67 Downloads/week (PyPI): 21 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.4.1 Downloads/month (PyPI): 135 Downloads/week (PyPI): 24 Forks (GitHub): 8 Stars (GitHub): 36 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 | io.github.notasandy/mcp-code-sanitizer | io.github.selvage-lab/selvage |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (worse) | 36 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 8 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-code-sanitizer) | On your machine (selvage) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/notasandy/mcp-code-sanitizer | github.com/selvage-lab/selvage |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
io.github.notasandy/mcp-code-sanitizer
Strict AI code reviewer powered by Groq. Finds bugs and vulnerabilities.
io.github.selvage-lab/selvage
An LLM-based code review MCP server with AST-powered smart context extraction
How to run each
io.github.notasandy/mcp-code-sanitizer As a local MCP server: PyPI package
claude mcp add --env "GROQ_API_KEY=<YOUR_GROQ_API_KEY>" --transport stdio mcp-code-sanitizer -- uvx mcp-code-sanitizerRequires: GROQ_API_KEY (secret)
io.github.selvage-lab/selvage As a local MCP server: PyPI package
claude mcp add --transport stdio selvage -- uvx selvageCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.selvage-lab/selvage publish no settings it asks for, so we do not compare settings.
What it can do: io.github.notasandy/mcp-code-sanitizer · What it can do: io.github.selvage-lab/selvage · Compare two other plugins
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.