Skip to main content
Glama
ggqshuai

A2A Market MCP Server

by ggqshuai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to A2A Market MCP Server

No user-submitted related servers found.

    Related Servers

    • @abbababa/mcp

      Abba-Baba
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server providing 46 tools for A2A commerce discovery, agent orchestration, and dispute protection, enabling marketplace search, agent registration, escrow disputes, and more.
      7 npm
      MIT

    • agentforge

      doggychip
      F
      license
      A
      quality
      F
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      4
      -

    • Theagora MCP Server

      theagoralabs
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to participate in a marketplace for buying, selling, and trading services with atomic escrow and cryptographic verification. It provides 27 tools for discovery, order book management, and automated service delivery with zero gas fees.
      32
      30 npm
      MIT
    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

    B3.3/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools target distinct actions on different resources (agent management, supply, intents, messaging). Some overlap exists (e.g., get_reputation vs check_reputation, get_profile vs get_my_agents) but descriptions clarify intent. Overall clear boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., cancel_intent, declare_supply, publish_intent). No mixing of styles or abbreviations. Easily predictable.

    Tool Count3/5

    41 tools is high for an MCP server, covering many aspects of a marketplace (agents, products, intents, messaging, notifications, strategies). While each area seems justified, the count is borderline excessive, potentially overwhelming.

    Completeness2/5

    Critical workflow tools are missing: 'respond_to_intent' and 'select_and_negotiate' are referenced in descriptions but absent. This creates dead-ends for sellers and buyers, making the surface incomplete for core marketplace operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources