eCommerce

market-category-booster.com

An MCP server that maps free-text product descriptions to marketplace category paths, lists loaded store taxonomies, and returns payment requirements for categorization calls.

1 endpoint3 known toolsFirst detected September 18, 2026Last detected September 18, 2026

ENDPOINT 1

https://market-category-booster.com/mcp

No auth detected

MCP server metadata

Name: mcb
Version: 0.1.3

Capabilities

experimentalloggingprompts.listChangedresources.listChangedtools.listChangedextensions.io.modelcontextprotocol/ui

Server instructions

Market Category Booster maps free-text product descriptions onto the live category taxonomy of a marketplace (Amazon, eBay, Shopify, Google). Recommended order of calls: 1. `list_stores` (free) to learn the valid `store_id` values; 2. `payment_info` (free) if you have no API key and intend to pay per call; 3. `categorize_product` for the actual work. Two things surprise most clients: - `categorize_product` returns a LIST, one match per taxonomy level, from the broadest to the most specific — not a single category id. Read the whole list as a path. - the descent has a token budget per request. When it runs out the last match carries `truncated: true`: the path is valid but is not necessarily a leaf, and the call is billed in full. Authentication accepts either an `X-API-Key` HTTP header on the MCP session, or an x402 payment proof in the JSON-RPC `_meta` under `x402/payment`. With neither, `categorize_product` answers with the x402 payment requirements instead of a result.

Known tools 3

categorize_product

Map a free-text product description to a marketplace category path.

Inferred read-only

list_stores

List the marketplaces whose taxonomies are loaded, as `store_id` values.

Inferred read-only

payment_info

Return the x402 payment requirements for one categorization call.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mcb]
url = "https://market-category-booster.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mcb": {
      "type": "http",
      "url": "https://market-category-booster.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mcb
Remote MCP URL: https://market-category-booster.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mcb": {
      "url": "https://market-category-booster.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mcb": {
      "type": "http",
      "url": "https://market-category-booster.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mcb",
  "transport": "streamable-http",
  "url": "https://market-category-booster.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.