Remote MCP server that maps a free-text product description to a marketplace category path, with optional API key or per-call x402 payment.
What you can do
Categorize products: map a free-text product description to a marketplace category path, walking the taxonomy level by level and returning one match per level with the reason for each pick.
List marketplaces: show the store_id values whose taxonomies are loaded, which are the only accepted store_id values.
Check payment terms: return the x402 payment requirements (network, asset, recipient address, amount) for one categorization call.
When to use it
Useful when an assistant has to assign listings or products to the right category in a marketplace taxonomy and needs the full path plus a rationale per level. Also handy for agents without an API key that want to pay per call instead.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. An API key sent in the X-API-Key header, or no key at all to pay per call via x402. Network access to the provider's endpoint.
Before you install
Calls can cost money: without an API key each categorization is paid per call through x402, which involves signing a payment authorization with a network, asset, recipient address and amount. The API key is a secret sent in the X-API-Key header. Product descriptions are sent to a third-party service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.market-category-booster%2Fmcb/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Map a free-text product description to a marketplace category path.
Walks the taxonomy of the target marketplace one level at a time and
returns the full path: one match per level, from the broadest category down
to the most specific one, each with the reason it was picked. Use it to
assign a listing category to a product you only have prose for.
The last match carries `truncated: true` when the per-request token budget
stopped the descent before a leaf. Every successful call is billed: with no
`X-API-Key` header and no x402 payment proof the tool answers with the
payment requirements instead of a result.
Parametersstore_idrequireddescriptionrequired
list_stores
List the marketplaces whose taxonomies are loaded, as `store_id` values.
These are the only accepted values for the `store_id` argument of
`categorize_product`. Free of charge on purpose: without it an agent would
have to pay for a failed call to discover them.
Takes no parameters.
payment_info
Return the x402 payment requirements for one categorization call.
Meant for an agent that holds no API key: gives network, asset, recipient
address and amount as JSON, so the payment authorization can be signed
before calling `categorize_product`. Free of charge.
Takes no parameters.
Version history
1
v0.1.3LatestSep 18, 2026
Score
75%
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.
