Skip to main content
Glama
theYahia

jazzcash-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to jazzcash-mcp

No user-submitted related servers found.

    Related Servers

    • @mogintel/mcp-jazzcash

      MogIntel
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server wrapping JazzCash payment provider APIs. Enables interaction with JazzCash services through natural language.
      MIT

    • payme-mcp

      theYahia
      A
      license
      B
      quality
      F
      maintenance
      MCP server for Payme payment system (Uzbekistan). Supports transactions, statements, payment links, and balance queries via JSON-RPC 2.0.
      8
      8 npm
      MIT

    • maib-mcp

      theYahia
      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

    • zen-mcp

      krystiangw
      A
      license
      A
      quality
      B
      maintenance
      MCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.
      14
      29 npm
      MIT

    • paymongo-mcp

      theYahia
      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
      6 npm
      2
      MIT

    • vnpay-mcp

      theYahia
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: status inquiry, wallet payment, CNIC-based payment, OTC voucher creation, and refund. Descriptions clearly differentiate them, with no functional overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., check_payment_status, create_payment), making it predictable for agents.

    Tool Count5/5

    With 5 tools covering creation, status, and refunds, the set is well-scoped for a payment MCP. No unnecessary tools and no obvious missing critical operations.

    Completeness4/5

    Covers core payment lifecycle: create (3 types), status, refund. Minor gaps like a tool to list all transactions or cancel a pending payment are absent, but the domain is sufficiently addressed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources