Ext Ops Panel
Open dashboard
Comparison

VeyraX vs Product Aura

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Product Aura is an MCP server published by productaura.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceVeyraXProduct Aura
Docker MCP Catalog Listed
Version: sha256:257d91533072
Forks (GitHub): 19
Pulls (Docker Hub): 18 904
Stars (Docker Hub): 4
Stars (GitHub): 48
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
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

VeyraX vs Product Aura
FactVeyraXProduct Aura
Marketplaces that list it11
Stars (GitHub) (differs)48 (better)0 (worse)
Pulls (Docker Hub) (differs)18 904No figure on Docker Hub
Forks (GitHub) (differs)19 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/veyrax)Remote server (productaura.co/api/mcp/account)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/veyrax/veyrax-mcpgithub.com/productaura/productaura
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-07
Endpoint at the last check (differs)no remote endpoint we checkResponded 11 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

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

Product Aura

In its own words, on Official MCP Registry:

Listing and ad images for Amazon, Etsy, Shopify, TikTok Shop and social ads, from one product photo.

How to run each

VeyraX As a local MCP server: Docker image

Claude Code
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

Product Aura As a remote MCP server

Claude Code
claude mcp add --transport http productaura https://productaura.co/api/mcp/account

Requires: PRODUCTAURA_API_KEY (secret)

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

Only Product Aura has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Product Aura publish no list of tools, so we do not compare tools.

Settings each asks for

Only VeyraX asks for

  • VEYRAX_API_KEY (secret)

Only Product Aura asks for

  • PRODUCTAURA_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: VeyraX · What it can do: Product Aura · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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