InventPay MCP Server
Related Servers
Alternatives to InventPay MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI assistants to create USDT and USDC invoices, retrieve payment links, and check invoice and store payment status across connected payment-gateway stores via the Model Context Protocol.2101,449 npmMIT- AlicenseAqualityCmaintenanceEnables AI agents to autonomously browse inventory, negotiate terms, manage carts, and execute secure payments on Shopify stores using standardized protocols. It provides a bridge for LLMs to handle the entire commerce lifecycle from discovery to order tracking through a verifiable mandate chain.52MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI models to manage escrow payments, account monitoring, and blockchain-verified transactions through the Model Context Protocol.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access real-time cryptocurrency market data, manage accounts, execute trades, track portfolios, and perform wallet and risk-management operations through the Model Context Protocol.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to perform and manage payments through the Model Context Protocol, including paying, checking balances and history, registering bots, setting spending limits, discovering supported networks and tokens, inspecting commissions, and managing bot pools. It also supports governed tool calls with policy decisions, human approval, and tamper-evident audit traces.12Apache 2.0

Adyvance MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI apps to search shop orders, products, customers, and stock and, with explicit approval, update orders, products, and inventory through the Model Context Protocol.MIT
TDQS
Scored across 20 tools
Most tools target distinct resources and actions. Slight overlap exists between get_store and get_store_analytics (both show order/product counts) and between create_payment and create_invoice, but descriptions clarify their different use cases.
All tool names follow a consistent verb_noun pattern with snake_case: get, create, update, delete, list, add. Resources are singular for single-item operations and plural for list operations, with only minor naming variance like get_key_pool_stats.
With 20 tools, the count is higher than the ideal 3-15 range but appropriate for the broad merchant platform scope covering stores, products, keys, payments, withdrawals, orders, and analytics. Each tool has a distinct purpose, so it does not feel bloated.
The tool surface covers core lifecycle operations for stores, products, keys, payments, withdrawals, and orders. Minor gaps exist (e.g., no store deletion, no key revocation, no payment cancellation), but these are typically not required for merchant operations and can be worked around.