Ext Ops Panel
Open dashboard
Comparison

tailwind-design-system vs dev.swatchdog/validator

tailwind-design-system is a plugin bundle for AI coding tools published by seungboshim. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). dev.swatchdog/validator is an MCP server published by swatchdog.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacetailwind-design-systemdev.swatchdog/validator
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 6
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

tailwind-design-system vs dev.swatchdog/validator
Facttailwind-design-systemdev.swatchdog/validator
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)6 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (swatchdog-mcp-970396648818.us-central1.run.app/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/seungboshim/skillsgithub.com/swatchdog-dev/swatchdog-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 h ago, requires a key

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

tailwind-design-system

In its own words, on Claude Code: claude-plugins-community:

Design system builder and refactorer for Tailwind CSS + Next.js projects. Audits existing styles, defines semantic color/typography tokens, extracts shared UI components, migrates codebases, and provides ongoing compliance review.

dev.swatchdog/validator

In its own words, on Official MCP Registry:

On-demand drift checks: declared CSS color, radius, spacing & type vs your own tokens or a pack

How to run each

tailwind-design-system As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tailwind-design-system@claude-community

dev.swatchdog/validator As a remote MCP server

Claude Code
claude mcp add --transport http validator https://swatchdog-mcp-970396648818.us-central1.run.app/mcp

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

Only dev.swatchdog/validator 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: tailwind-design-system · What it can do: dev.swatchdog/validator · 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.

Where the data comes from: how the catalog is built