Skip to main content
Glama
spranab

icantmarket-mcp

by spranab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to icantmarket-mcp

No user-submitted related servers found.

    Related Servers

    • MCPLookup MCP by mcplookupdev

      MCPLookup MCPofficial

      mcplookupdev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to resolve server names, discover servers via taxonomy, and look up trust ratings for MCP servers through the MCPLookup independent trust layer.
      48 npm
      MIT

    • AgentLookup MCP Server

      peureka
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables search, discovery, lookup, and registration of AI agents from the public agentlookup.dev registry directly from any MCP-compatible client, with tools to find agents by capability or browse by popularity.
      30 npm
      MIT

    • Clawslist MCP Server

      srcnysf
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to interact with the Clawslist marketplace to browse, create, and manage listings using the Model Context Protocol. It provides a comprehensive set of tools for agent registration, messaging, and offer management directly within MCP-compatible clients.
      19
      3 npm
      MIT

    • mcp-mcpmarket

      xzeronelysium
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables discovery and automatic installation of MCP servers via mcpmarket.com integration. Searches repositories, scrapes GitHub READMEs for configuration details, and provides one-click installation to MCP clients.
      -
    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

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: products versus asks versus user identity, and list versus get versus submit/post. Even list_products and list_asks are clearly separated by domain (product vs ask), with no overlapping purposes.

    Naming Consistency4/5

    The vast majority follow a consistent verb_noun pattern: list_products, get_product, list_asks, get_ask, submit_review, post_ask. The lone exception is whoami, which is a conventional CLI-style command but does break the strict verb_noun pattern.

    Tool Count5/5

    Seven tools is well-scoped for the marketplace flow: product browsing, ask browsing, auth verification, review submission, and ask posting. Each tool maps to a clear user need without redundancy or bloat.

    Completeness4/5

    The core lifecycle—browse products, list/inspect asks, submit a review, post an ask—is fully covered. Minor gaps exist such as no tool to view one's own Review-to-Post balance or manage/delete an ask, but these are not required for the primary workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources