Ext Ops Panel
Open dashboard
Comparison

Amazon Q Business vs parfum1 Perfume API

Amazon Q Business is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). parfum1 Perfume API is an MCP server published by parfum1.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
MarketplaceAmazon Q Businessparfum1 Perfume API
Docker MCP Catalog Listed
Version: sha256:e6e17afb81df
Forks (GitHub): 1 867
Pulls (Docker Hub): 13 467
Stars (Docker Hub): 0
Stars (GitHub): 9 899
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Amazon Q Business vs parfum1 Perfume API
FactAmazon Q Businessparfum1 Perfume API
Marketplaces that list it11
Stars (GitHub) (differs)9 899No figure on GitHub
Pulls (Docker Hub) (differs)13 467No figure on Docker Hub
Forks (GitHub) (differs)1 867No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/amazon-qbusiness-anonymous-mcp-server)Remote server (parfum1.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)6, secrets among them: 2Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpNot stated
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 checkStatus out of date: last check 2 days ago returned HTTP 405

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

Amazon Q Business

In its own words, on Docker MCP Catalog:

AI assistant for ingested content with anonymous access.

parfum1 Perfume API

In its own words, on Official MCP Registry:

parfum1 perfume catalogue: notes, 3/10/30 ml sizes, EUR prices, stock, houses, delivery, returns.

How to run each

Amazon Q Business As a local MCP server: Docker image

Claude Code
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio amazon-qbusiness-anonymous -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/amazon-qbusiness-anonymous-mcp-server

Requires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)

parfum1 Perfume API As a remote MCP server

Claude Code
claude mcp add --transport http perfumes https://parfum1.com/mcp

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

Only parfum1 Perfume API has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of parfum1 Perfume API publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of parfum1 Perfume API publish no settings it asks for, so we do not compare settings.

What it can do: Amazon Q Business · What it can do: parfum1 Perfume API · 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