Ext Ops Panel
Open dashboard
Comparison

evolve-loop vs ai.openhelm/dev-changes

evolve-loop is a plugin bundle for AI coding tools published by mickeyyaya. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ai.openhelm/dev-changes is an MCP server published by openhelm.ai. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
Marketplaceevolve-loopai.openhelm/dev-changes
Claude Code: claude-plugins-community Listed
Version: 8.11.1
Forks (GitHub): 2
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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

evolve-loop vs ai.openhelm/dev-changes
Factevolve-loopai.openhelm/dev-changes
Marketplaces that list it11
Stars (GitHub) (differs)5No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.openhelm.ai/dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mickeyyaya/evolve-loopNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

evolve-loop

In its own words, on Claude Code: claude-plugins-community:

A self-learning development pipeline that gets smarter with every cycle. It calibrates itself against your codebase, dynamically selects the highest-impact tasks, implements them in isolated git worktrees, and blocks bad code through eval gates — then learns from each cycle to make better decisions next time. 4 specialized agents (Scout, Builder, Auditor, Operator) work across 5 phases: DISCOVER → BUILD → AUDIT → SHIP → LEARN. The Scout uses multi-armed bandit scoring and 8-dimension quality benchmarks to target your codebase's weakest areas. The Builder implements in isolation. The Auditor blocks MEDIUM+ severity issues. After each cycle, the pipeline extracts reusable "instincts" — patterns about what worked and what failed — that compound over time. Every 5 cycles, a meta-cycle evaluates the pipeline itself and evolves its own agent prompts based on measured performance. It ran 151 cycles on its own codebase, shipping 67+ improvements and raising its quality score from 83.8 to 94.4 — all autonomously. No e

ai.openhelm/dev-changes

In its own words, on Official MCP Registry:

Turn described changes into reviewed pull requests: propose, triage, review, dependency audits.

How to run each

evolve-loop As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install evolve-loop@claude-community

ai.openhelm/dev-changes As a remote MCP server

Claude Code
claude mcp add --transport http dev-changes https://mcp.openhelm.ai/dev/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: evolve-loop · What it can do: ai.openhelm/dev-changes · 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.

Where the data comes from: how the catalog is built