Ext Ops Panel
Open dashboard
Comparison

frontend-design-audit vs Website Color Palette — Static CSS Literals, Alpha & Counts

frontend-design-audit is a plugin bundle for AI coding tools published by mistyhx. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Website Color Palette — Static CSS Literals, Alpha & Counts is an MCP server published by kriton-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacefrontend-design-auditWebsite Color Palette — Static CSS Literals, Alpha & Counts
Community marketplace mistyhx/frontend-design-audit Listed
Version: 1.0.0
Forks (GitHub): 14
Stars (GitHub): 101
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
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

frontend-design-audit vs Website Color Palette — Static CSS Literals, Alpha & Counts
Factfrontend-design-auditWebsite Color Palette — Static CSS Literals, Alpha & Counts
Marketplaces that list it11
Stars (GitHub) (differs)101No figure on GitHub
Forks (GitHub) (differs)14No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.apify.com)
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/mistyhx/frontend-design-auditNot stated
Changes in the last 7 days00
First seen (differs)2026-10-292026-11-02
Endpoint at the last check (differs)no remote endpoint we checkResponded 23 h ago, requires authentication

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

frontend-design-audit

In its own words, on Community GitHub marketplaces:

Audit and improve front-end usability using 15 established design principles. Acts as a Senior UX designer/engineer reviewing your interface end-to-end.

Website Color Palette — Static CSS Literals, Alpha & Counts

In its own words, on Official MCP Registry:

Extract declared website CSS color literals and counts without a browser or page text

How to run each

frontend-design-audit As a Claude Code plugin

Claude Code
/plugin marketplace add mistyhx/frontend-design-audit
/plugin install frontend-design-audit@frontend-design-audit

Website Color Palette — Static CSS Literals, Alpha & Counts

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

Requires: Authorization header

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

Only Website Color Palette — Static CSS Literals, Alpha & Counts 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: frontend-design-audit · What it can do: Website Color Palette — Static CSS Literals, Alpha & Counts · 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