Ext Ops Panel
Open dashboard
Comparison

deep-review vs com.mcparmory/codacy

deep-review is a plugin bundle for AI coding tools published by Iron-Ham. Marketplaces we read that list it: 1 (Community GitHub marketplaces). com.mcparmory/codacy is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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
Marketplacedeep-reviewcom.mcparmory/codacy
Community marketplace iron-ham/claude-deep-review Listed
Version: 5.8.0
Forks (GitHub): 2
Stars (GitHub): 38
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
Downloads/month (PyPI): 824
Downloads/week (PyPI): 160
Forks (GitHub): 4
Stars (GitHub): 32
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.0.3
Downloads/month (PyPI): 824
Downloads/week (PyPI): 160
Forks (GitHub): 4
Stars (GitHub): 32
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

deep-review vs com.mcparmory/codacy
Factdeep-reviewcom.mcparmory/codacy
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)38 (better)32 (worse)
Forks (GitHub) (differs)2 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcparmory-codacy)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/iron-ham/claude-deep-reviewgithub.com/mcparmory/registry
Changes in the last 7 days (differs)20
First seen (differs)2026-10-222026-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

deep-review

In its own words, on Community GitHub marketplaces:

Comprehensive code review skill with 53 specialized agents for architecture, code quality, error handling, types, comments, tests, accessibility, localization, concurrency, performance, simplification, security, and 30 platform-specific reviews with automatic detection and confidence scoring.

com.mcparmory/codacy

In its own words, on Official MCP Registry:

Analyze code quality, security issues, and coverage across repositories

How to run each

deep-review As a Claude Code plugin

Claude Code
/plugin marketplace add iron-ham/claude-deep-review
/plugin install deep-review@claude-deep-review

com.mcparmory/codacy As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio codacy -- uvx mcparmory-codacy

Commands 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

Neither one's marketplaces publish the settings it asks for.

What it can do: deep-review · What it can do: com.mcparmory/codacy · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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