Skip to main content
Glama
goofish-z-mcp

goofish-z-mcp

by E-R-Butch

Related Servers

Alternatives to goofish-z-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      MCP server for automating Xianyu (Goofish) marketplace operations: publish, manage items, handle IM messages, and more via CLI or AI agents.
      17
      1,060 PyPI
      498
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching Xianyu (Goofish) listings, fetching item details, taking keyword-monitor snapshots, and publishing secondhand products through MCP tools with local-session authentication.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables automating buyer-side workflows on Xianyu (Goofish) by searching products, sending individual or batch price inquiries, and retrieving seller responses through MCP tools.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Alibaba's Xianyu (Goofish) second-hand marketplace as MCP tools so AI agents can publish and delist listings, upload images, recommend categories, fetch default addresses, search items, and read or send instant messages with real-time event streaming. It also includes built-in rate limiting and risk-control guards for safe automated operations.
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Read-only MCP server that lets AI agents query second-hand Xianyu (Goofish) listing prices collected by local watch tasks, returning price statistics, daily trends, cheapest matching items, recent listings and an overview of monitored keywords. It works entirely against the local SQLite database, so lookups are fast and carry no scraping risk.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and manage Xianyu items, publish or edit physical products, handle conversations and messages, and complete QR-code login with cookie setup.
      -

    TDQS

    C2.8/5.0

    Scored across 37 tools

    Disambiguation3/5

    Most tools are cleanly separated by namespace and action, but several pairs overlap: item.get vs item.view both retrieve item details, auth.doctor vs auth.risk-status both diagnose health/risk state, and watch.start/watch.run/watch.job/watch.jobs/watch.list have confusingly similar boundaries. watch.enable also packs two operations (enable/disable) into one tool, adding ambiguity.

    Naming Consistency4/5

    The set consistently follows a lowercase namespace.action pattern (e.g., auth.login, item.publish, message.send, watch.add), which is predictable and easy to scan. Minor deviations include item.mine and location.default using non-action terms, and singular/plural pairs like watch.job vs watch.jobs, but these do not break the overall pattern.

    Tool Count2/5

    37 tools is too many for most agents to reason about effectively, especially when 14 belong to watch.* and 5 to auth.*. While the domain is fairly broad, the count crosses the 'too many' threshold and would benefit from consolidation or sub-namespace grouping.

    Completeness3/5

    The set covers login, publishing, searching, item detail, messaging, blacklist rules, and price monitoring, so the core seller workflow is present. However, there is no item.update/edit operation, no auth.logout, no message read/delete capability, and watch items cannot be modified after creation, leaving noticeable lifecycle gaps.