Skip to main content
Glama

AI Orderability (AIO) Agents CPG with x402: Retail & Marketplace Sourcing

Server Details

CPG sourcing for AI Agents with x402: BPC brands, agent IM, Trading Desk. GreenCore Solutions Corp.

Ownership verified

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
greencore-solutions/gsc-marketplace
GitHub Stars
0
Server Listing
GSC-Marketplace
ChatGPT
–
Claude
–

TDQS

B3/5.0

Scored across 11 tools

Disambiguation3/5

The search_brands → get_brand → get_brand_identifiers sequence is explicitly staged (Step 1/2/3), which helps, but several tools (get_cpg_knowledge_graph, get_radar, get_marketplace_operators, get_aio_agent_fleet) all return network/registry metadata with blurry boundaries, and contact_trading_desk vs instant_message_agents overlap as contact channels. The dense, jargon-heavy descriptions make it harder for an agent to quickly tell which meta-lookup tool is the right one.

Naming Consistency4/5

A clear get_<noun> convention dominates (get_brand, get_radar, get_marketplace_operators, etc.), with only search_brands, contact_trading_desk, and instant_message_agents as verb-noun deviations. Minor inconsistencies (get_acm_68000, get_x402_rail use identifiers rather than nouns) but overall predictable.

Tool Count4/5

11 tools is a reasonable, well-scoped set for a discovery/sourcing server. A few tools are pure informational lookups (get_acm_68000, get_x402_rail, get_radar) that border on redundant context rather than distinct operations, but nothing is excessive.

Completeness3/5

Discovery is well covered end-to-end (found → verified → answerable), plus contact and payment-rail pointers. However, the actual sourcing/ordering action is deliberately offloaded ('no new write path here', terms live only in the 402 payload), so the server cannot execute the transaction implied by its 'Orderability/Sourcing' purpose — a notable functional gap.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Agentic commerce infrastructure for AI agents. MCP-native product discovery, contextual ad matching, and purchase facilitation with European privacy compliance (nDSG/GDPR).
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A2A Grocery is the Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for retail grocery procurement. It puts makers, brand owners, private label, distributors and importers in front of the AI agents that now do the grocery buying, and gives retail procurement desks every cleared supplier's record, ready to order. 20 markets on the SCHEMA algo record. No ads. No rank for sale. Trade only.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      AgentShare delivers structured product search and pricing signals for AI agents over REST and MCP (Streamable HTTP). Responses include freshness & coverage metadata so agents can reason about data recency. API keys secure billed endpoints; public discovery at /agent.json and /mcp.json. Currently integrates connected marketplaces and affiliate feeds – roadmap expands to global e-commerce (AliExpre
      4
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.