BestPrice MCP
Related Servers
Alternatives to BestPrice MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search, track, and monitor product prices, retrieve price history, and set up price alerts via the Pricewatcha API.1Apache 2.0
- AlicenseAqualityBmaintenanceProvides AI assistants with access to ShopSavvy's comprehensive product data, pricing information, and historical price tracking, enabling product lookup by barcode or ASIN, current offers, price history, and scheduling for automatic monitoring.92,480 npm9MIT
- AlicenseAqualityAmaintenanceEnables AI agents to search Digikala's catalogue, compare every seller's offers and prices, review ~30 days of price history, read customer reviews and Q&A, and surface current deals, all through read-only tools.2326MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and compare Norwegian grocery prices across multiple chains, retrieve price history, and access product details through the kassal.app API.MIT
- FlicenseNot gradedqualityCmaintenanceEnables price comparison and market intelligence through seven tools for searching product prices across Idealo and Amazon, retrieving price history, comparing competitor pricing, and looking up product details by EAN/UPC barcode.1-
- AlicenseAqualityDmaintenanceEnables AI assistants to access Amazon price history, sales rank trends, product details, best-sellers, and deals via the Keepa API for product research and deal hunting.679 npmMIT
TDQS
Scored across 4 tools
Each tool targets a completely different stage of the shopping workflow: get_shopping_decision for recommendations/plans, search_products for product discovery, compare_offers for current merchant pricing, and get_price_history for historical trends. The long descriptions explicitly state when to use and not use each tool, leaving no ambiguity about which one to select.
The names follow a clear verb_noun pattern, but the verbs are mixed: get_shopping_decision and get_price_history share 'get_', while search_products and compare_offers use different verbs. This is still readable and predictable, but not perfectly uniform; minor deviation from a single convention.
Four tools is well within the ideal 3–15 range and each one earns its place. The server is tightly scoped to the shopping assistance domain with no redundant or filler tools, and every tool addresses a distinct consumer need.
The surface covers the core shopping journey: search for products, get a recommendation/plan, compare offers, and check price history. A minor gap is the lack of a direct get-product-by-ID tool, but search_products can retrieve product info by name/barcode and compare_offers works with an exact ID, so agents can work around this. Other excluded actions like checkout are intentionally out of scope.