zhizhuip-mcp
OfficialRelated Servers
Alternatives to zhizhuip-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables the full Ingram Micro Reseller purchasing lifecycle through a single stateless HTTP MCP service, covering catalog and pricing, quotes, quote-to-order, order placement/modification/cancellation/lookup, invoices, renewals, special deals, returns, and freight estimates with one set of credentials.24Apache 2.0

inflow-mcpofficial
AlicenseNot gradedqualityDmaintenanceMCP Server for agents to onboard, pay, and provision services autonomously with InFlow6MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to access Amazon Selling Partner and Advertising APIs for orders, inventory, pricing, ads, reports, and related read paths.MIT
- FlicenseNot gradedqualityCmaintenanceEnables managing Ozon Seller and Performance APIs through MCP, covering products, stocks, prices, orders, finance, analytics, advertising, reviews, and chat operations.-
- AlicenseAqualityCmaintenanceEnables MCP clients to search availability, read services, resources, bookings and customers, and, when writes are enabled, reserve slots, create or cancel bookings, and add or update customers.10MIT
- AlicenseAqualityCmaintenanceEnables eBay-backed product search, authenticated shopping carts, checkout quotes, and order management through MCP tools and resources.119 npmMIT
TDQS
Scored across 40 tools
Each tool targets a distinct resource and action—user info, pricing, orders, sub-account lifecycle, and bandwidth—with no overlapping purposes. Even similar tools like sub_account_update vs sub_account_update_batch are clearly separated by single vs batch operation.
All tools follow snake_case with consistent verb prefixes (order_, sub_account_, user_, etc.), making the naming predictable and easy to navigate. The pattern is uniform across the entire set.
40 tools is far beyond the typical well-scoped range and feels heavy. Many tools are batch variants or could be consolidated (e.g., sub_account_set_limit_flow and its batch counterpart), and the large surface increases cognitive load for agents.
The set covers core proxy operations comprehensively: user info, pricing, orders (buy/renew/upgrade/refund), sub-account management, and bandwidth queries. Minor gaps exist, such as no explicit order history or whitelist update tool, but these are not critical for typical workflows.