Ext Ops Panel
Open dashboard
Comparison

designlang vs AllGoodInsp

designlang is a plugin bundle for AI coding tools published by Manavarya Singh. Marketplaces we read that list it: 1 (Community GitHub marketplaces). AllGoodInsp is an MCP server published by allgoodinsp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
MarketplacedesignlangAllGoodInsp
Community marketplace manavarya09/design-extract Listed
Version: 13.3.2
Forks (GitHub): 376
Stars (GitHub): 4 413
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.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

designlang vs AllGoodInsp
FactdesignlangAllGoodInsp
Marketplaces that list it11
Stars (GitHub) (differs)4 413No figure on GitHub
Forks (GitHub) (differs)376No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.allgoodinsp.com)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)15Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/manavarya09/design-extractNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-272026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-27

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

designlang

In its own words, on Community GitHub marketplaces:

Thirteen slash commands wrapping the designlang CLI: /extract (full design language → DTCG, Tailwind, Figma), /site (crawl a whole site → one canonical design system + consistency grade), /grade (shareable HTML report card + SVG badge), /battle (head-to-head graded comparison), /remix (restyle in 6 vocabularies — brutalist, swiss, art-deco, cyberpunk, soft-ui, editorial), /pack (one downloadable design-system bundle), /theme-swap (OKLCH-correct recolour around a new brand primary), /brand (full editorial brand-guidelines book — 13 chapters, hand-off-ready), /pair (fuse two designs across configurable axes — colours from one site, typography from another), /studio (live token-editor with component preview + export), /verify (rebuild from tokens and pixel-diff vs live for a fidelity score), /fidelity (score a clone vs the original — visual pixel-diff + motion fidelity — with a ranked correction plan), /gallery (build a shareable static gallery of measured clones).

AllGoodInsp

In its own words, on Official MCP Registry:

Curated design references for AI — real CSS values, typography specs, and color palettes.

How to run each

designlang As a Claude Code plugin

Claude Code
/plugin marketplace add manavarya09/design-extract
/plugin install designlang@designlang

AllGoodInsp As a remote MCP server

Claude Code
claude mcp add --transport http allgoodinsp https://mcp.allgoodinsp.com

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only AllGoodInsp has a remote endpoint we check. How we check endpoints

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: designlang · What it can do: AllGoodInsp · 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