superbuy-mcp
Related Servers
Alternatives to superbuy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search Taobao products, read details, and view product images through a local relay, with limited browsing and no ordering or cart actions.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching Xianyu (Goofish) listings, fetching item details, taking keyword-monitor snapshots, and publishing secondhand products through MCP tools with local-session authentication.MIT
- AlicenseNot gradedqualityCmaintenanceEnables read-only, local browser-based access to logged-in sessions on Xianyu, Taobao/Tmall, JD, and Pinduoduo for product search, detail inspection, link building/parsing, and cookie status checks, without chat, cart, ordering, or payment actions.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to search Xianyu second-hand marketplace for product prices with automatic cookie detection.2-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control the Taobao Desktop client for product search, price comparison, cart management, and seller communication via the Model Context Protocol.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to automate Taobao shopping tasks such as searching products, viewing details, adding to cart, placing orders, and making payments via Playwright.31MIT
TDQS
Scored across 6 tools
Search, details, and publish form a clear pipeline, and status is diagnostically distinct. The only mild overlap is between superbuy_fetch (active raw fetch) and superbuy_captures (passive traffic log), which could be confused by a hurried agent, but descriptions clarify the difference.
The two superbuy_-prefixed snake_case tools sit alongside bare nouns (status, search, details, publish), so there's no single predictable pattern. Names remain readable and inferable, but the mix of prefixed and unprefixed conventions is noticeable.
Six tools is well within the healthy range and each maps to a step in the research-to-publish workflow. The two diagnostic tools (status, captures) are somewhat auxiliary but justified given the bridge/extension architecture.
The surface covers the core lifecycle: search → details → publish, with diagnostics for the bridge and API exploration. Minor gaps exist (no session listing/cleanup, no order or cart interaction), but the stated curation workflow is fully supported.