digikala-mcp
Related Servers
Alternatives to digikala-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to discover products, build carts, and complete purchases across multiple downstream commerce services through a secure, contract-driven API.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover products, verify signed catalog feeds, negotiate within published policies, and place mandate-bound orders with signed receipts via MCP, A2A, or REST.MIT
- AlicenseNot gradedqualityFmaintenanceEnables intelligent ecommerce tools for agents and applications, including product catalog access, product addition, and shopping policies.1Apache 2.0
- AlicenseAqualityCmaintenanceEnables eBay-backed product search, authenticated shopping carts, checkout quotes, and order management through MCP tools and resources.1111 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI shopping agents to send plain-language requests and receive deterministically ranked, cross-merchant product offers with grounded reasons and inline product images. Enforces a merchant-controlled disclosure layer so individual product facts can be hidden from the agent while still used for matching.1,470,813 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to securely search products, obtain signed quotes, create checkouts, and track orders without directly handling prices or payment amounts, enforcing spending policies and audit trails.1-
TDQS
Scored across 40 tools
Many tools have overlapping purposes: compare_products, compare_offers, and compare_product_sellers all compare offers/specs; get_product_variants, list_offers, and get_product all surface offers. The dual cart API sets (add_to_cart vs add_to_account_cart, read_cart vs read_account_cart, get_cart_operation vs get_account_cart_operation) are nearly identical but target different auth contexts, creating significant misselection risk.
Tool names are overwhelmingly snake_case with verb_noun patterns, but there are minor inconsistencies: get_cart_limits vs read_cart, and the account-specific prefixing creates near-duplicate names (e.g., add_to_cart vs add_to_account_cart). The convention is mostly predictable, with occasional get/read variation.
40 tools is heavy for an e-commerce product research and cart server. Many tools are redundant due to two parallel cart operation sets and multiple comparison endpoints, so the surface feels inflated rather than well-scoped.
The product research side is comprehensive (search, details, variants, offers, reviews, Q&A, ratings, media, price history, recommendations, categories, filters, trends). Cart lifecycle is fully covered for both account modes, including login/logout and reconciliation. Missing checkout, order history, and payment tools, but those may be intentionally out of scope.