design-council vs Inspectrum
design-council is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
design-council is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. Inspectrum is an MCP server published by yannmenec. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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
| Marketplace |  Inspectrum | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.6.0 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Community marketplace iowarp/clio-coder | Removed on 2026-10-23 Version: 0.6.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.3 Downloads/month (npm): 192 Downloads/week (npm): 77 Forks (GitHub): 1 Stars (GitHub): 2 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 | design-councilno longer listed · | Inspectrum |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 2 |
| Forks (GitHub) (differs) | 5 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (inspectrum) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/yannmenec/inspectrum |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-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 design-council
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Collaborative technical discussion with proactive requirements gathering
-
Design operations: critique, handoff specs, sprint planning, team workflows.
-
Debate implementation approaches with structured pros and cons analysis
-
Plan execution with devil's advocate and code review, a writing style guide, design, testing, architecture and database skills, and session post-mortems
-
Design reviews at scale, planning cadence, decision frameworks, delegation, operating rhythm.
-
Convene a team of specialist agents out of a 20-agent roster in a 3-round deliberation council on your hardest engineering decisions. Walk away with a unified design and a phased…
What each says it does
design-council
Convenes several expert perspectives that challenge each other on a design decision with real trade-offs before code is written; quick mode runs a single round. Not for a one-question-at-a-time interrogation of a plan; use grill-me. Not for splitting implementation across workers; use dispatch directly.
Inspectrum
Review coding-agent plans on demand with peer models, attributed findings, and a structured verdict.
How to run each
design-council
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Inspectrum As a local MCP server: npm package
claude mcp add --transport stdio inspectrum -- npx -y inspectrumCommands 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: design-council · What it can do: Inspectrum · 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.