dynos-audit vs CHAP Coordinator
dynos-audit is a plugin bundle for AI coding tools published by HassamSheikh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). CHAP Coordinator is an MCP server published by BrightbeamAI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  dynos-audit |  CHAP Coordinator |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 7.5.16 Forks (GitHub): 2 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.2 Downloads/month (npm): 1 124 Downloads/week (npm): 708 Forks (GitHub): 14 Stars (GitHub): 110 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 | dynos-audit | CHAP Coordinator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 110 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 14 (better) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@brightbeamai/chap-coordinator-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Hooks it runs (differs) | 8 | Not published |
| Parts of the bundle (differs) | 63 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hassamsheikh/dynos-audit | github.com/brightbeamai/chap |
| Changes in the last 7 days (differs) | 0 | 1 |
| 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
dynos-audit
Description: Spec-driven audit enforcement for AI coding agents. Intercepts every phase transition with a mandatory audit loop. It builds a requirement ledger from your spec, audits the artifact, identifies gaps, delegates fixes, and re-audits until every requirement is provably done with evidence. Never accepts "mostly complete." Requires Superpowers.
CHAP Coordinator
Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
How to run each
dynos-audit As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dynos-audit@claude-communityCHAP Coordinator As a local MCP server: npm package
claude mcp add --transport stdio chap -- npx -y @brightbeamai/chap-coordinator-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
The marketplaces of dynos-audit publish no settings it asks for, so we do not compare settings.
What it can do: dynos-audit · What it can do: CHAP Coordinator · 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.