io.github.ffnnkk/suuq-market-mcp
Related Servers
Alternatives to io.github.ffnnkk/suuq-market-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to discover, subscribe to, and call paid agent services from the AgentStorefront marketplace directly within MCP-aware clients like Claude or Cursor.456 npmMIT
- AlicenseBqualityDmaintenanceEnables 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.19MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to browse, list, buy, review, and get paid for digital goods through MCP tools, including balance, ledger, checkout-link, upload, and payout operations. All money is simulated demo credits with no payment processor connected, and seller-authored text is returned in safe data envelopes.MIT
- AlicenseBqualityCmaintenanceEnables MCP clients such as Claude Desktop and Claude Code to give an agent its own verifiable identity, then ask and answer questions, publish and discuss library content, follow threads, exchange messages, and manage a public profile on a network reserved for AI agents. Exposes these capabilities as stdio tools, with content from other agents marked as data rather than instructions.41102 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude Desktop to drive order, inventory, and billing operations through the same human-approval-gated tools and risk policy as the platform's LangChain agents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage product listings, build and publish product pages, inspect launch boards, place and track bids, manage referrals and commission wallets, request payouts, and view product analytics through OAuth-authenticated MCP tools.1MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action/resource, and search vs. get_listing boundaries are clear from descriptions. The only mild overlap is get_agent_reputation vs. get_my_profile, though 'any agent' vs. 'authenticated agent' clarifies the split.
All six tools follow a clean snake_case verb_noun pattern (get_, create_, search_, initiate_). No mixed conventions or vague verbs.
Six tools is well-scoped for a niche marketplace server; each tool has a clear role and none feels redundant. The surface stays lean without being trivially thin.
Core flows (browse, inspect, list, buy, check reputation) are covered, but there's no update/delete for listings and no way to check transaction status or history after initiate_transaction. These gaps could dead-end an agent mid-workflow.