Ext Ops Panel
Open dashboard
Comparison

brandketing vs io.github.gigsoul/x402-api

brandketing is a plugin bundle for AI coding tools published by entro314-labs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.gigsoul/x402-api is an MCP server published by gigsoul. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplacebrandketingio.github.gigsoul/x402-api
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.0.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

brandketing vs io.github.gigsoul/x402-api
Factbrandketingio.github.gigsoul/x402-api
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (gig-x402-api.jayson-be1.workers.dev)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)13Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/entro314-labs/brandketinggithub.com/gigsoul/x402
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (10 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

brandketing

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

Marketing intelligence plugin that builds a living context store from product docs, customer calls, CRM data, and competitor research - then compiles structured briefs and generates copy through a 6-step strategy workflow with a built-in critic pass. Separates evidence collection, human approval, brief compilation, and copy generation into distinct steps so the model never does extraction, positioning, and writing in one jump.

io.github.gigsoul/x402-api

In its own words, on Official MCP Registry:

AI API for marketing, content and outreach. 22 endpoints. Pay with USDC on Base via x402.

How to run each

brandketing As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install brandketing@claude-community

io.github.gigsoul/x402-api As a remote MCP server

Claude Code
claude mcp add --transport http x402-api https://gig-x402-api.jayson-be1.workers.dev

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

Only io.github.gigsoul/x402-api 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: brandketing · What it can do: io.github.gigsoul/x402-api · 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