momo-xof-mcp
Related Servers
Alternatives to momo-xof-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenanceMCP server that connects AI assistants to the CinetPay API for mobile money payments across Africa, enabling balance checks, payment initialization, transfers, and more.718 npmMIT- AlicenseNot gradedqualityBmaintenanceAn MCP server for Mobile Money in Francophone West Africa that enables AI agents to make payments via MTN MoMo (sandbox) using tools like request_payment, check_payment_status, and disburse_payment.1MIT
- AlicenseAqualityCmaintenanceIt enables AI assistants to request payments, check account balances and status, and track transactions over MTN Mobile Money. It runs locked to MTN's sandbox unless a production country is explicitly selected and separately acknowledged.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to accept payments in Senegal via Flutterwave hosted checkout.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call Safaricom's M-Pesa Daraja API directly, sending STK push prompts, checking balances, looking up or reversing transactions, and receiving results as SUCCESS, FAILED, or UNKNOWN. Requests are sent once per idempotency key with sandbox-by-default operation, so agents can operate and test payments without risking double charges or real money.3MIT
- AlicenseNot gradedqualityBmaintenanceIvory Coast Payments MCP — let AI agents accept payments in Ivory Coast via Orange Money, MTN Mobile Money, Wave, and cards through Paystack's hosted checkout.MIT
TDQS
Scored across 3 tools
The three tools occupy clearly separate phases of a payment flow: static coverage lookup, payment initiation, and status polling. Descriptions explicitly disambiguate initiation (request-only, returns a link) from status checking (read-only, resolves outcome), so an agent cannot easily confuse them.
All three follow the same pattern: a shared momo_ namespace prefix plus verb_noun (list_operators, initiate_payment, check_payment_status). No mixed casing or inconsistent verb styles.
Three tools is exactly the surface needed for a narrow mobile-money payment scope: discover coverage, start a payment, check its result. Each tool earns its place and nothing extraneous is exposed.
The core lifecycle (coverage discovery -> initiate -> async status) is fully covered, including idempotency references and finality of FAILED states. Gaps remain around refunds, cancellation, and listing past transactions, but agents can work around these for the stated request-and-reconcile purpose.