forge vs Batch Review
forge is a plugin bundle for AI coding tools published by UtkarshJain98. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Batch Review is an MCP server published by hevangel. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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 |  forge |  Batch Review |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 95ef910 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.3.0 Forks (GitHub): 0 Stars (GitHub): 2 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 | forge | Batch Review |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 2 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (https://github.com/hevangel/batch-review-mcp/releases/download/v1.3.0/batch-review-mcp-1.3.0.mcpb) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/utkarshjain98/forge | github.com/hevangel/batch-review-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| 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
forge
Description: Adversarial code hardening for Claude Code. Forge spawns two agents — a Builder and a Breaker — that iterate against each other until the code is unbreakable. The Builder implements a feature, the Breaker writes adversarial tests to prove bugs, and the Builder must fix the implementation without deleting or weakening the tests. The loop continues until the Breaker can't produce a failing test. The result is battle-tested code with a permanent adversarial test suite. Key features: - Evidence-based, not opinion-based. Every issue the Breaker raises must have a failing test that proves the bug. No test, no break. This eliminates false positives and subjective feedback. - Iterative adversarial loop. Builder and Breaker are separate agents that go back and forth for up to N rounds. The Builder cannot dismiss feedback; it must make the failing tests pass. - Adversarial tests are permanent. The Breaker's tests stay in the repo under tests/adversarial/ as a regression suite. Future changes are protected
Batch Review
Git diff and markdown review with a web UI plus MCP stdio for AI agents.
How to run each
forge As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install forge@claude-communityBatch Review
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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: forge · What it can do: Batch Review · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.