Ext Ops Panel
Open dashboard
Comparison

clio-coder-test vs Dunstan

clio-coder-test is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

clio-coder-test is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Dunstan is an MCP server published by BargLabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclio-coder-testDunstan
Community marketplace iowarp/clio-kit Removed on 2026-10-16
Version: 0.3.1
Forks (GitHub): 5
Stars (GitHub): 8
Not marked · First seen
Not listed
Community marketplace iowarp/clio-coder Removed on 2026-10-23
Version: 0.4.1
Forks (GitHub): 5
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.13
Downloads/month (npm): 543
Downloads/week (npm): 154
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

clio-coder-test vs Dunstan
Factclio-coder-testno longer listed · Dunstan
Marketplaces that list it (differs)01
Stars (GitHub) (differs)80
Forks (GitHub) (differs)50
Last release (differs)Not published2026-10-23
Where it runs (differs)Installs as a plugin bundleOn your machine (dunstan)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Apache-2.0AGPL-3.0-only
Repository (differs)github.com/iowarp/clio-codergithub.com/barglabs/dunstan
Changes in the last 7 days (differs)61
First seen (differs)2026-10-132026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of clio-coder-test

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • tdd-guard

    Enforces Test-Driven Development by intercepting file operations in Claude Code. When Claude attempts to edit or write files, TDD Guard validates the changes against TDD…

    by nizos · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • undercover

    Test coverage feedback loop plugin for Claude Code using the undercover Ruby gem

    by grodowski · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • testing

    Test-quality skills for Claude Code. AI-driven mutation testing, where Claude acts as the mutation engine to find weak tests, and agentic testing, where Claude drives the running…

    by Dawid Dahl · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • isitdone

    Make a coding agent prove it: run the repo's real tests, typecheck and lint before it says done.

    by raimondasl · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • tailtest

    tailtest automatically generates and runs tests every time Claude Code edits a file. No commands, no configuration, no reminders needed. It hooks into Claude's file write event…

    by avansaber · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • Mneme

    Prevent, catch, and verify architectural violations while Claude Code works.

    by Mneme HQ · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

clio-coder-test

In its own words, on Community GitHub marketplaces:

Verifies a Clio Coder source change against the current contract, smoke, boundary, and application test lanes, including temporary-state and local-provider harnesses. Not for deciding what may change; use clio-coder-dev.

Dunstan

In its own words, on Official MCP Registry:

Checks a coding agent's handback against the pull request's GitHub record. No model decides.

How to run each

clio-coder-test

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Dunstan As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio dunstan -- npx -y dunstan mcp

Requires: GITHUB_TOKEN (secret)

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

The marketplaces of clio-coder-test publish no settings it asks for, so we do not compare settings.

What it can do: clio-coder-test · What it can do: Dunstan · Compare two other plugins

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.

Where the data comes from: how the catalog is built