Ext Ops Panel
Open dashboard
Comparison

audit-project vs ai.openhelm/dev-changes

audit-project is a plugin bundle for AI coding tools published by agent-sh. 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-13. 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
Marketplaceaudit-projectai.openhelm/dev-changes
Claude Code: claude-plugins-community Listed
Version: 5.1.0
Forks (GitHub): 2
Stars (GitHub): 3
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

audit-project vs ai.openhelm/dev-changes
Factaudit-projectai.openhelm/dev-changes
Marketplaces that list it11
Stars (GitHub) (differs)3No 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)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agent-sh/audit-projectNot 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

audit-project

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

Multi-agent iterative code review until zero issues remain. Spawns up to 10 specialist reviewers (code quality, security, performance, test coverage, architecture, database, API, frontend, backend, DevOps) chosen based on the project's signals. Each pass produces certainty-graded findings (HIGH / MEDIUM / LOW); HIGH findings auto-fix where safe. The orchestrator iterates passes until zero open issues remain or a max-iteration cap is reached. Specialists are role-based (defined inline via Task tool, not file-based agents) so they don't bloat the plugin's agent count. Designed to plug into /next-task and /prepare-delivery as the deep-review phase.

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

audit-project As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install audit-project@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: audit-project · 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