Skip to main content
Glama
E-R-Butch

goofish-z-mcp

by E-R-Butch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to goofish-z-mcp

No user-submitted related servers found.

    Related Servers

    • goofish-cli

      fancyboi999
      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.
      4
      17
      463 PyPI
      221
      Apache 2.0

    • xianyu-buyer-mcp

      xhjiang1998
      A
      license
      Not graded
      quality
      C
      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.
      MIT

    • dsh-goofish-mcp

      zhengjy01
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only monitoring of Xianyu (Goofish) listings, item details, chats, and account status through MCP tools for DeepSeek Harness.
      464 npm
      MIT

    • FishClaw MCP

      TnoobT
      F
      license
      A
      quality
      D
      maintenance
      An 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.
      11
      24
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources