AlipayPlus MCP Server
OfficialRelated Servers
Alternatives to AlipayPlus MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) compatible server that integrates Ant International's Antom payment APIs, enabling AI assistants to handle payment and refund operations seamlessly.57MIT- AlicenseAqualityCmaintenanceEnables AI assistants to handle WeChat Pay V3 and Alipay signing, order creation, and callback verification locally without touching funds.11MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to interact with multiple payment providers (Stripe, Paystack) through a unified API. Supports payment initialization, verification, refunds, customer management, and invoicing without requiring knowledge of specific provider implementations.2-
- FlicenseNot gradedqualityBmaintenanceEnables secure, bilingual AI assistants to query and manage payments, orders, refunds, transactions, wallets, fraud risk, and statistics with per-user data isolation enforced on every tool call.-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to manage transactions, initiate payments, and integrate with the OPSG/iPay88 payment gateway using local merchant credentials.-
- AlicenseAqualityBmaintenanceAn MCP server that exposes Alipay AI Pay capabilities to AI agents, enabling skill discovery, payment integration guides, and merchant onboarding workflows via Alipay's payment APIs.4114 npmMIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: payment creation, payment query, payment cancellation, refund creation, customs declaration, and customs query. No overlap exists, and the purposes are clearly separated.
Most tools follow a clear verb_noun pattern (create_payment, query_payment, cancel_payment, create_refund). However, 'customs_declare' and 'query_customs_declare' use a different structure, deviating from the pattern established by the other tools.
With 6 tools, the set is well-scoped for a payment processing server. Each tool covers a distinct aspect of the payment lifecycle, and the number is neither too small nor excessive.
The server covers the main payment operations (create, query, cancel) and refunds, but lacks a dedicated refund query tool. While refunds can be initiated, agents cannot independently verify refund status, which is a notable gap in lifecycle coverage.