review-council vs Batch Review
review-council is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
review-council is a plugin bundle for AI coding tools published by DeployHQ. No marketplace we read lists it any more. 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-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Batch Review | |
|---|---|---|
| Community marketplace deployhq/review-council | Removed on 2026-10-17 Version: 0.10.1 Forks (GitHub): 0 Stars (GitHub): 3 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 | review-councilno longer listed · | Batch Review |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 2 |
| 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) | 10 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/deployhq/review-council | github.com/hevangel/batch-review-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of review-council
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI-powered code review using Codex — three-party consensus between Codex, Claude Code, and you
-
Code review with any AI model via OpenRouter. Run standard and adversarial reviews against your working tree or branch using Claude, GPT, Gemini, Llama, or any other model…
-
A research-backed code review plugin for Claude Code that orchestrates parallel concern-specialized agents, cross-validates findings with deterministic verification, and produces…
-
Comprehensive, project-agnostic, multi-agent code review for Claude Code with verification to eliminate false positives.
-
AI-to-AI code review router. Any OpenAI-compatible model reviews your code. No Codex CLI or Node.js required.
-
Automatic code review, adversarial review, and rescue via Codex through OpenRouter.
What each says it does
review-council
Multi-agent code review for Claude Code. Multiple AI models review your PR, code, or plan independently; a cross-family refutation pass and an active judge then distill the findings into a curated, severity-ranked list of what actually needs changing.
Batch Review
Git diff and markdown review with a web UI plus MCP stdio for AI agents.
How to run each
review-council
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Batch 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: review-council · What it can do: Batch Review · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.