Skip to main content
Glama
asgard-ai-platform

mcp-buy123-vendor

by asgard-ai-platform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-buy123-vendor

No user-submitted related servers found.

    Related Servers

    • inventory-mcp

      ruanderson1
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for querying product inventory, providing tools to retrieve product details and stock quantities.
      -

    • SimpleShop MCP

      mikz
      A
      license
      B
      quality
      C
      maintenance
      A read-only MCP server for SimpleShop accounting data, enabling AI agents to find documents, download PDFs, inspect products, and review sales exports.
      5
      MIT

    • FinOps AI Copilot MCP Server

      anmolratna
      F
      license
      B
      quality
      C
      maintenance
      A secure, read-only MCP server that enables AI assistants to inspect transactions, vendor performance, wallet balances, and analytics through validated REST API calls.
      19
      -

    • Shopify MCP

      chatterjeearjun
      A
      license
      A
      quality
      C
      maintenance
      A read-only MCP server that lets AI assistants answer Shopify store operations questions via tools like get_shop, list_products, get_product, and list_orders.
      4
      MIT

    • flin-google-ads-mcp

      flin-agency
      A
      license
      B
      quality
      C
      maintenance
      Read-only MCP server for Google Ads, enabling querying campaigns, ad groups, ads, insights, and keywords without create/update/delete operations.
      9
      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

    C2.6/5.0

    Scored across 61 tools

    Disambiguation2/5

    Many tools have overlapping names and concepts, such as list_product_bundles vs list_bundles, list_items vs list_products, and multiple similar list_* endpoints for different resource types. An agent can easily confuse which list to call for a given purpose.

    Naming Consistency4/5

    The naming convention is mostly consistent with snake_case and verb_noun pattern (list_*, get_*, check_*). Minor exceptions like auth_status and vendor_login deviate slightly but remain readable and predictable.

    Tool Count2/5

    With 61 tools, the server is heavily over-scoped for most use cases. Many tools simply list enum values or static configurations, which bloats the tool surface and increases selection complexity.

    Completeness2/5

    The toolset is almost entirely read-only (list/get/check), lacking create, update, or delete operations for core entities like products, bundles, and vendors. This creates dead ends for management workflows and limits the server's practical utility.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources