Skip to main content
Glama

Related Servers

Alternatives to AIMarket

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to discover and pay for AI services per call via USDC on Solana, supporting marketplace search, listing details, on-chain reputation, wallet info, and paid calls.
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to discover live MeshKore agents, see their current operational status and pricing, and directly invoke their skills without an SDK, account, or API key.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets AI agents search a marketplace of agent services, read seller storefronts, and prepare a checkout link that a human owner approves and pays in their browser. The agent never holds keys or signs.
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to discover governed capabilities, inspect machine-readable contracts, and request policy-checked procurements with signed receipts and audit trails.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, describe, and call paid data services from the Pocket Network agentic marketplace, paying per request in USDC via x402.
      16 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    market_search vs market_invoke and the three pipeline_* tools have clearly distinct actions, and the refund trio is likewise separable. The only friction is that pipeline_refund_prepare vs pipeline_prepare and pipeline_refund_status vs pipeline_status look similar at a glance, but descriptions make the boundary clear.

    Naming Consistency4/5

    All names are snake_case with a consistent prefix_action shape (market_*, pipeline_*, pipeline_refund_*). The addition of _status and _refund_* variants is slightly irregular but still fully predictable and readable.

    Tool Count5/5

    Eight tools is well-scoped: two for marketplace discovery/invocation and three each for the pipeline and refund lifecycles, with no redundant entries.

    Completeness4/5

    The surface covers search, invoke, and full prepare/invoke/status lifecycles for both pipelines and refunds, with clear recovery via status tools. Gaps are minor (no listing of a caller's runs/purchases or explicit cancellation), which agents can largely work around.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive