io.github.dingdawg/dingdawg-code-review vs io.github.invigil/invigil
io.github.dingdawg/dingdawg-code-review is an MCP server published by dingdawg. Marketplaces we read that list it: 1 (Official MCP Registry). 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-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
| Marketplace |  io.github.dingdawg/dingdawg-code-review |  io.github.invigil/invigil |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.6 Downloads/month (npm): 179 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
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 | io.github.dingdawg/dingdawg-code-review | io.github.invigil/invigil |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (dingdawg-code-review) | On your machine (invigil) |
| 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/dingdawg/dingdawg-agent-1 | github.com/invigil/invigil |
| 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.dingdawg/dingdawg-code-review
AI code review — security, quality, performance. Learns your patterns. Receipted.
io.github.invigil/invigil
Linters check your code. Invigil checks whether your repo is legible — to newcomers and AI agents.
How to run each
io.github.dingdawg/dingdawg-code-review As a local MCP server: npm package
claude mcp add --env "DINGDAWG_API_KEY=<YOUR_DINGDAWG_API_KEY>" --transport stdio dingdawg-code-review -- npx -y dingdawg-code-reviewRequires: DINGDAWG_API_KEY (secret)
io.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.
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.invigil/invigil publish no settings it asks for, so we do not compare settings.
What it can do: io.github.dingdawg/dingdawg-code-review · What it can do: io.github.invigil/invigil · 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.