Skip to main content
Glama

Related Servers

Alternatives to pinduoduo-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables searching, normalizing, and signal-analyzing products on Pinduoduo, with built-in fraud signals to help Claude reason about product authenticity.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables login-free, read-only product discovery across Taobao, JD, and Pinduoduo by returning publicly indexed prices, general promotions, and links, while also generating official search links and parsing product IDs without network access.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Products, social posts, search results and AI answers from Amazon, TikTok, Google, ChatGPT and more, as MCP tools. Code mode: the model writes TypeScript against a typed client, run in a sandbox.
      3
      695 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents and humans to search products across multiple stores, compare prices, and place real orders directly from the terminal using 46 MCP tools.
      63 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to retrieve product details, customer reviews, and search results from retailers like Amazon, Target, Best Buy, Home Depot, and Walmart through a unified MCP interface.
      206 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation3/5

    Several tool pairs have soft boundaries: pdd_status vs pdd_resume (both inspect session/runtime state without navigating), pdd_search vs pdd_browse_home (both extract product cards), and pdd_read_item vs pdd_read_sku (both surface price/spec info). The very long descriptions do draw distinctions (e.g. link-as-identifier only, spec-combination requirement), so an agent can recover, but selection still requires careful reading rather than obvious intent.

    Naming Consistency4/5

    All ten tools share a uniform pdd_ prefix and are overwhelmingly verb_or_resource + noun (read_item, read_cart, read_sku, add_cart, browse_home, contact_seller). Minor deviations exist where the second segment is a bare noun or verb (pdd_status, pdd_resume, pdd_login), but the pattern remains predictable.

    Tool Count5/5

    Ten tools is well within the ideal range and each maps to a distinct stage of the shopping loop: status/login/resume for session handling, search/browse/read_item/read_sku for discovery, read_cart/add_cart for cart, contact_seller for communication. No tool looks like filler.

    Completeness3/5

    Read coverage is thorough, but the cart surface is write-once: there is pdd_add_cart and pdd_read_cart with no update-quantity, remove-item, or select/deselect tools, and no order placement or order-history tools at all. Some of this is deliberate read-only-by-design, but the lifecycle dead-ends (cannot correct a cart, cannot verify a purchase) will force agents to stop short.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues