yeepay-mcp
Related Servers
Alternatives to yeepay-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceyop-mcp 是一个专为易宝支付开放平台(YOP)设计的 MCP (Model Context Protocol) Server,提供了一套完整的工具函数,帮助开发者通过AI助手(如Claude、Cursor等)更便捷地获取YOP平台的相关信息、生成密钥对、下载证书等操作。103Apache 2.0
- FlicenseBqualityDmaintenanceA Model Context Protocol (MCP) service for integration with external platforms, providing CRUD operations for 23 entity types through a standardized MCP interface.11-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for YApi that enables developers to search, view, create, and update API definitions directly from MCP-compatible IDEs.2MIT
- FlicenseAqualityCmaintenanceEnables MCP clients to manage YApi projects and interfaces, including searching and creating APIs, editing mock response bodies and advanced mock scripts, managing mock expectations, and testing mock URLs.111-
- 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
- AlicenseCqualityDmaintenanceMCP server for YApi integration that generates TypeScript types, mock data, and API request code.58 npm4MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one creates a payment order, and the other queries the payment status. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the task.
Both tools follow a consistent verb_noun pattern with underscores: 'create_webpage_yeepay_payment' and 'query_yeepay_payment_status'. The naming is predictable and readable, with no deviations in style or convention.
With only two tools, the server feels thin for a payment processing domain. While the tools cover creation and status querying, typical payment workflows might require additional operations like refunds, cancellations, or listing transactions, making the tool count insufficient for comprehensive coverage.
The tool set is severely incomplete for a payment processing server. It lacks essential operations such as refunding payments, canceling orders, handling webhooks, or retrieving transaction lists. This creates significant gaps that could lead to agent failures when attempting full payment lifecycle management.