apinoa-mcp
OfficialRelated Servers
Alternatives to apinoa-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA suite of MCP servers that give AI agents read-only access to Chinese e-commerce platform business data, including advertising, orders, products, and more from platforms like Douyin, JD.com, Taobao, etc.2291 PyPI92MIT
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to company data across PostgreSQL, MongoDB Atlas, and flat files through MCP tools, allowing AI assistants to query and retrieve information via natural language.-

Unwrangle MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to retrieve product details, customer reviews, and search results from retailers like Amazon, Target, Best Buy, Home Depot, and Walmart through a unified MCP interface.7 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.4 npmISC

com.upscrape/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI clients to retrieve real-time structured data from 50+ commerce, grocery, social, and maps platforms over a remote MCP server using OAuth authentication.1MIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read Kaufland marketplace seller data as MCP tools, including orders, order units, offers, shipments, tickets, storefronts, and warehouses.AGPL 3.0
TDQS
Scored across 3 tools
The three tools occupy completely separate roles: search_docs is free documentation discovery, execute is the paid code runner for all API work, and translate_image is a single-purpose image transformation. The descriptions explicitly reinforce the boundary ('Free: it calls nothing', 'Use it before writing code'), so an agent cannot mistake one for another.
search_docs and translate_image use a consistent snake_case verb_noun pattern, while execute is a bare verb with no noun. That deviation is minor and idiomatic for a runner tool, so the set still reads predictably.
Three tools is thin in raw count, but the design deliberately collapses 35+ platforms and hundreds of operations behind a single typed executor plus a discovery tool, so each tool earns its place. The only slightly odd member is translate_image, which is a niche add-on unrelated to the discovery/execute core.
The discover-then-execute loop covers the full domain: search_docs lists every operation, parameter, cost and return field, and execute handles calls, pagination, fan-out, persistence and usage inspection. Minor gaps exist around pre-run budget/account checks and error diagnostics outside of code, but agents can work around these inside execute.