Skip to main content
Glama

Related Servers

Alternatives to paytabs-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.
      14
      21 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for PayMongo payment gateway (Philippines). Supports payment intents, sources, payments, refunds, and checkout sessions via Basic Auth.
      24
      11 npm
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for MAIB e-commerce payments (Moldova). Supports payments, refunds, recurring billing, one-click payments, and transaction status via OAuth 2.0.
      8
      13 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Bank of Georgia iPay payment gateway, enabling payment orders, refunds, recurring payments, and pre-authorization via OAuth 2.0 + JWT.
      8
      16 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for JazzCash mobile wallet and payments (Pakistan). Supports wallet payments, mobile account payments, vouchers, refunds, and balance inquiries.
      5
      11 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for VNPay payment gateway (Vietnam). Supports payment URL generation, transaction queries, refunds, tokenized payments, and IPN verification with HMAC-SHA512 signing.
      8
      10 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action: creating payment pages, querying, refunding, voiding, tokenization, charging tokens, listing, and fetching methods. No overlap exists.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (create_, query_, refund_, void_, list_, get_, charge_). The naming convention is uniform and predictable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a payment processing server, covering core payment operations without being bloated or sparse.

    Completeness4/5

    The surface covers the main payment lifecycle: creation, querying, refund, void, tokenization, and charging tokens. A minor gap is the lack of a capture/settlement operation, but most workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing