Skip to main content
Glama
io.github.zerotaldev/ozow

io.github.zerotaldev/ozow

by zerotaldev

Related Servers

Alternatives to io.github.zerotaldev/ozow

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create Paystack checkout links, verify payments, read transaction history, and list supported banks across African markets, with test-mode enforcement and safety guards for live payments.
      20 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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.
      14
      52 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely create payment references and requests for Multibanco, MB WAY, Payshop, Credit Card, PinPay, Cofidis Pay, PIX, and retrieve payment reports.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to create stablecoin payment links with QR codes and hosted checkout pages, and to check, list, validate or delete payments across Stellar, Solana and Monad using an API key. Read-only mode, scoped keys and tool annotations keep fund-moving and destructive actions under user control.
      9
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with the Centrapay payments API for testing NZ payment flows, including creating, managing, and settling payment requests through natural language.
      9
      7 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.