io.github.zerotaldev/ozow
Related Servers
Alternatives to io.github.zerotaldev/ozow
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with the PayFast payment gateway to manage transactions, subscriptions, and refunds. It provides a suite of 13 tools with built-in human-in-the-loop safety confirmations for high-risk financial operations.1425 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to accept payments in South Africa using Paystack's hosted checkout for cards and instant EFT.MIT

ifthenpay paymentsofficial
FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely create payment references and requests for Multibanco, MB WAY, Payshop, Credit Card, PinPay, Cofidis Pay, PIX, and retrieve payment reports.-- AlicenseAqualityBmaintenanceEnables interaction with the Centrapay payments API for testing NZ payment flows, including creating, managing, and settling payment requests through natural language.93 npm1MIT

cryptunnel-mcpofficial
AlicenseAqualityBmaintenanceEnables coding agents to create and look up crypto payments over stdio, returning checkout links, payment statuses, paged payment lists, and receivable currencies, with real payments gated behind an explicit opt-in environment flag.4MIT- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Investec banking accounts, transactions, payments, and programmable cards through natural language.372MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: credential check, environment report, payment creation, transaction lookup, and cancellation. There is slight conceptual overlap between ozow_verify_credentials and ozow_environment (both configuration preflight checks), but the descriptions make the boundary clear.
All tools use a consistent ozow_ prefix and snake_case with verb_noun phrasing (verify_credentials, create_payment, get_transactions, cancel_payment). ozow_environment is a noun-only outlier, but overall the pattern is predictable.
Five tools is a tight, well-scoped surface for a payment integration. Every tool earns its place covering a distinct step in the payment flow.
The core flow (create, check status, cancel) is covered, but there are notable gaps: no refund, no settlement/payout inspection, no webhook or notification handling, and transaction listing is only scoped per payment request rather than a general ledger. Agents handling post-payment reconciliation would hit dead ends.