Ext Ops Panel
Open dashboard
Comparison

@stateset/cli vs Good Nature Vibe Catalog

@stateset/cli is an MCP server published by stateset. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Good Nature Vibe Catalog is an MCP server published by goodnaturevibe.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplace@stateset/cliGood Nature Vibe Catalog
npm registry (MCP servers) Listed
Version: 1.40.0
Downloads/month (npm): 1 390
Downloads/week (npm): 192
Forks (GitHub): 6
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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

@stateset/cli vs Good Nature Vibe Catalog
Fact@stateset/cliGood Nature Vibe Catalog
Marketplaces that list it11
Stars (GitHub) (differs)7 (better)0 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last release (differs)2026-10-22Not published
Where it runs (differs)On your machine (@stateset/cli)Remote server (catalog-mcp.goodnaturevibe.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MIT OR Apache-2.0Not stated
Repository (differs)github.com/stateset/stateset-icommercegithub.com/aiagentcycle/gnv-catalog-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-03
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h ago

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

@stateset/cli

In its own words, on npm registry (MCP servers):

AI-powered local-first commerce engine — orders, inventory, payments, policies, and integrations

Good Nature Vibe Catalog

In its own words, on Official MCP Registry:

Public read-only catalog and knowledge of the Good Nature Vibe shop. No login.

How to run each

@stateset/cli

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

Good Nature Vibe Catalog As a remote MCP server

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

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

Only Good Nature Vibe Catalog 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: @stateset/cli · What it can do: Good Nature Vibe Catalog · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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