闲鱼 MCP
Related Servers
Alternatives to 闲鱼 MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables automating buyer-side workflows on Xianyu (Goofish) by searching products, sending individual or batch price inquiries, and retrieving seller responses through MCP tools.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
- AlicenseBqualityDmaintenanceEnables searching and monitoring of Goofish (闲鱼) items via Playwright automation, providing structured item details and keyword-based monitoring.48ISC
- FlicenseAqualityDmaintenanceAn MCP server that automates Xianyu marketplace operations through Playwright, allowing users to manage listings and conduct market research via natural language. It features integrated tools for generating AI-powered product descriptions and cover images using DashScope.1126-
- AlicenseBqualityAmaintenanceMCP server for automating Xianyu (Goofish) marketplace operations: publish, manage items, handle IM messages, and more via CLI or AI agents.17802 PyPI487Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables read-only monitoring of Xianyu (Goofish) listings, item details, chats, and account status through MCP tools for DeepSeek Harness.90 npm1MIT
TDQS
Scored across 18 tools
Most tools target distinct resources or actions, but several overlaps create ambiguity: get_sendable_conversations largely duplicates get_conversations with sendable_only=true, hello overlaps with check_server_status, generate_report overlaps with get_sales_analytics, and get_top_items overlaps with search_items when sorted by sales.
The tool set is consistently snake_case and mostly follows a verb_noun or get_noun pattern. The only notable outlier is 'hello', while names like check_server_status, search_items, and get_traffic_analytics fit the convention.
18 tools is slightly above the typical ideal range, but the server spans multiple subdomains: health checks, item search/publishing, messaging, and analytics. The count is mostly justified, though a few redundant tools inflate it.
The surface covers item CRUD, search, messaging, and several analytics views, which is strong for this domain. Minor gaps remain, such as a dedicated get_item detail endpoint and any order/transaction management, but core workflows are covered.