VoucherVault MCP Server
Related Servers
Alternatives to VoucherVault MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables agents to manage Valeria Store's VCC card purchasing, balance checking, and order tracking via its internal REST API.-
- AlicenseAqualityDmaintenanceEnables AI agents to browse the giftcardshop catalog and purchase gift cards using Lightning payments, with no account or signup required.533 npmMIT

@walletap/mcp-serverofficial
AlicenseAqualityCmaintenanceEnables AI assistants to issue and manage Apple Wallet and Google Wallet passes, including template creation, pass issuance, notifications, stamping, and loyalty management.2667 npmMIT- FlicenseNot gradedqualityCmaintenanceEnables Bonus Pink sub-accounts to manage loyalty programs via AI agents, offering 84 tools for card issuance, points, stamps, visits, rewards, and communications.-
- FlicenseNot gradedqualityCmaintenanceEnables AI to view and manage e-commerce data such as products, orders, and coupons, and perform actions like updating prices, stock, and generating sales reports.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with an eCardWidget account using a scoped API key, allowing search and sending of eCards, directory management, and listing campaigns, widgets, and automations.41 npm1MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: list, get, create, update, mark used, and delete. There is no meaningful overlap between tools, and the toggle behavior of coupon_mark_used is clearly documented.
Tool names follow a consistent coupon_ prefix with action suffixes (get, create, update, delete, mark_used). The only deviation is coupons_list using the plural resource name instead of coupon_list, which is minor but noticeable.
Six tools provide a focused, well-scoped surface for managing vouchers, coupons, gift cards, and loyalty cards. Each tool covers a necessary part of the lifecycle without unnecessary bloat.
The tool set covers the full lifecycle: list/search, retrieve, create, update, mark as used, and delete. It also handles filtering and status behavior, making it complete for the stated domain.