perf vs Crispy Profiling
perf is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Crispy Profiling is an MCP server published by edgeorgie. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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: 0.6.0 Downloads/month (npm): 1 333 Downloads/week (npm): 1 333 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 | Crispy Profiling |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| 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 (crispy-profiling) |
| 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 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/agent-sh/perf | github.com/edgeorgie/crispy-profiling |
| Changes in the last 7 days | 2 | 2 |
| 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.
Crispy Profiling
Deterministic React render profiling: renders, wasted renders and their causes per component.
How to run each
perf As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install perf@claude-community
Crispy Profiling As a local MCP server: npm package
claude mcp add --transport stdio crispy-profiling -- npx -y crispy-profiling mcp
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: perf · What it can do: Crispy Profiling · 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 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.