InventPay MCP Server
Related Servers
Alternatives to InventPay MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables 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-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously issue single-use, merchant-locked virtual Visa cards and execute payments across supported merchants through the Model Context Protocol, with human-in-the-loop approval.8-
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to act as a merchant, selling catalog items and issuing USDC invoices with cross-chain payment support via Arcorapay.1 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage an online store for honey and beekeeping products, including order tracking, inventory updates, sales stats, and invoice resending via the Model Context Protocol.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform e-commerce operations through a standardized interface implementing the x402 and Agentic Commerce Protocol (ACP). Supports merchant sessions, product search, and payment orchestration with production-ready security features.-
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.