perf vs Code Review Analyst
perf is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Code Review Analyst is an MCP server published by j0hanz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 5.1.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.7.6 Forks (GitHub): 0 Stars (GitHub): 0 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 | perf | Code Review Analyst |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@j0hanz/code-review-analyst-mcp) |
| 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) | 15 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/agent-sh/perf | github.com/j0hanz/code-review-analyst-mcp |
| 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
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions — run by AI agents inside your editor. `/perf` enforces a rigorous 10-phase methodology derived from recorded real investigation sessions: establish a baseline, identify the breaking point, generate hypotheses, profile, run controlled experiments, measure, document. No random micro-optimizations; every change is baselined, isolated, measured, and either kept or reverted with evidence. Designed to keep the agent honest in a domain where intuition is usually wrong.
Code Review Analyst
Gemini-powered MCP server for code review analysis.
How to run each
perf
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Code Review Analyst As a local MCP server: npm package
claude mcp add --transport stdio code-review-analyst -- npx -y @j0hanz/code-review-analyst-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
Neither one's marketplaces publish the settings it asks for.
What it can do: perf · What it can do: Code Review Analyst · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.