nexi-xpay-mcp-server
Related Servers
Alternatives to nexi-xpay-mcp-server
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.24 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to operate Xental merchant accounts via natural language, provisioning virtual accounts, monitoring transactions, and executing payouts.13MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search a shop's products, retrieve product details, prepare PayPal checkout links, and check order status over MCP. Payment approval remains with the buyer in PayPal.1MIT

Deliverect MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query live restaurant sales, orders, menus, opening hours, and operational health across locations and ordering channels. Access is read-only and scoped to what the signed-in user can see.MIT
Qonto MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Qonto financial data including organization info, account balances, transaction history, and business operations through natural language.42MIT
TDQS
Scored across 4 tools
Each tool targets a distinct resource or aspect: orders list, order details, payment methods, and warnings. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tool names use snake_case, which is consistent. However, the pattern is not uniform: 'list_orders' follows verb_noun, while 'order_details', 'payment_methods', and 'warnings' are noun_noun or noun-only. This minor inconsistency prevents a perfect score.
With 4 tools, the server is scoped to a focused set of read operations. While slightly low, it covers the essential queries for the Nexi XPay Back Office without unnecessary bloat, making it appropriate for its purpose.
The tools cover the main read operations: listing orders, getting details, viewing payment methods, and checking warnings. Missing operations like creating or updating orders are not expected if the server is read-only, so the surface is largely complete for its intended use.