What the BizNetAI MCP server does
BizNetAI MCP server provides commerce discovery for AI agents and shopping assistants. It searches live independent merchant storefronts across the United States and Canada, then returns structured merchant or product information. The service covers categories such as skincare, clothing, electronics, food, pet products, baby and kids, wellness, and home goods; the current category list should be retrieved at query time because coverage changes.
The product search does not perform unrestricted text matching across every possible product. Instead, it maps a natural-language request to one of BizNetAI’s curated, country-specific product varieties and returns that variety’s ranked results. A request that does not match a known variety returns an empty list.
How it works
The hosted service uses streamable HTTP at https://biznetaimcp.consumergenie.net/mcp. Each request must include an Authorization: Bearer <api_key> header. Requests are stateless, so the client does not need to establish a session before calling a tool.
Start with list_categories when the available merchant vocabulary is unknown. Use find_merchants to locate currently reachable merchants matching a natural-language query, or list_merchants to retrieve the complete database directory for a country and optional category. The two merchant tools serve different purposes: the complete directory can include endpoints that are temporarily unreachable, while live merchant search filters for current reachability.
For product discovery, list_product_varieties shows the country-specific varieties and approximate result counts. find_products then searches one of those varieties with pagination through limit and offset. Product records include titles, descriptions, price ranges, currency, availability, product URLs, images, merchant domains, merchant MCP endpoints, positions, and relevance scores.
Setup and configuration
The BizNetAI MCP server is hosted, so there is no local package or process to install. Request an API key through the developer-key registration API with an email address, name, and use-case description. The key is returned after approval, shown only once, and should be kept outside source control.
Clients that primarily use stdio can connect through mcp-remote, passing the remote endpoint and the BIZNETAI_API_KEY value as the authorization header. Raw HTTP clients can call the MCP endpoint directly with JSON-RPC and the required content negotiation headers. The default per-key rate limit is 60 requests per minute. Exceeding it produces HTTP 429 with Retry-After; missing, invalid, or revoked credentials produce HTTP 401.
Tools and capabilities
The BizNetAI MCP server exposes five tools:
list_categories returns the current merchant category vocabulary.find_merchants searches live merchants by natural-language query and ISO country code, with an optional result limit.list_merchants lists merchants from the database by country and optional category, with limit and offset paging.list_product_varieties reports country-specific product varieties and their result counts.find_products searches a matched product variety by country, with limit and offset paging.
Product availability is a boolean indicating whether at least one variant was in stock during the last catalog refresh. Exact stock quantities are not provided by all merchant backends. Results are capped by the matched variety’s available catalog, commonly around 50 products and sometimes fewer for niche searches. Relevance scores are supplied without a fixed acceptance threshold, so the calling application must decide what score is adequate.
Limitations and notes
Coverage is currently described as more than 18,000 live merchants across the US and Canada, but merchant and category coverage changes over time. Country codes are required for merchant and product queries, and product varieties may use different wording between countries.
list_merchants is complete relative to its database view but does not test endpoint liveness. find_merchants can omit a merchant whose endpoint is slow to respond. Product availability reflects the last catalog refresh rather than a guaranteed real-time stock check. API access also depends on an approved key and its rate limit.
