mcp-server-vippsmobilepay
Related Servers
Alternatives to mcp-server-vippsmobilepay
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to access Amazon Selling Partner and Advertising APIs for orders, inventory, pricing, ads, reports, and related read paths.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to create payment links, check link and payment status, cancel links, issue full or partial refunds, list merchants, and summarize recent collections using the platform's API key.9MIT

WhizzyCommerce MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables merchants to read shop data and propose changes to orders, pricing, catalogue, translations, and design through an MCP client, with every write previewed and confirmed in the dashboard.MIT- AlicenseAqualityBmaintenanceEnables MCP clients to query proxy sub-accounts, traffic, pricing, and inventory, and to place orders, renew, and modify configurations after user confirmation.40MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing Ozon Seller and Performance APIs through MCP, covering products, stocks, prices, orders, finance, analytics, advertising, reviews, and chat operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables merchants to manage their U.CASH Pay account from an MCP client by creating hosted checkouts, verifying settlement webhook signatures via HMAC, and reading safe agent settings plus Discord, Telegram, BigCommerce, Ecwid, and Wix integration credentials.77 PyPIMIT
TDQS
Scored across 14 tools
Tools split cleanly along three domains (funds ledger reporting, ePayment, Recurring agreements) and each action targets a distinct resource+verb: get_payment vs capture/refund/cancel_payment, and the *_charge variants are unambiguously scoped to Recurring charges. Even the closely related reads (list_ledgers vs get_funds_summary vs list_transactions) are differentiated by their descriptions (accounts, sums, entries). No two tools appear to do the same thing.
Every tool uses the same vipps_ prefix followed by a verb_noun pattern (list_ledgers, get_payment, capture_payment, refund_charge, cancel_charge, check_connection). Resource suffixes (payment vs charge vs agreement vs ledger) are used consistently to distinguish domains.
14 tools is well within a comfortable range and each one maps to a real operation: 4 ledger/reporting, 4 ePayment, and 6 Recurring agreement/charge tools. Nothing looks redundant or like filler.
Read and money-moving coverage is solid for existing payments, agreements and charges, but there is no way to initiate a payment, create an agreement or create a charge, and payments can only be fetched by reference with no list/search operation. These gaps are workable (creation often happens via the frontend/SDK) but will cause dead ends for agents asked to start a payment flow or reconcile an unknown payment.