Skip to main content
Glama
theYahia

payme-mcp

by theYahia

Related Servers

Alternatives to payme-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Payme — the leading payment system in Uzbekistan. Enables AI agents to process payments, manage cards, and generate checkout links through the Model Context Protocol.
      10
      12 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for IDPay payment gateway (Iran). Supports payment creation, verification, inquiry, transaction listing, and payment links.
      8
      18 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
      12 npm
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for JazzCash mobile wallet and payments (Pakistan). Supports wallet payments, mobile account payments, vouchers, refunds, and balance inquiries.
      5
      13 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
    • 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

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are mostly distinct in purpose, but 'check_perform_transaction' and 'check_transaction' could be confused if descriptions are not read carefully. Overall, each tool targets a specific action.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_transaction, create_payment_link). No mixing of conventions.

    Tool Count5/5

    8 tools cover the essential payment lifecycle (create, validate, perform, cancel, status, balance, statement, payment link) without being excessive or insufficient.

    Completeness4/5

    Core payment operations are covered, but missing refund or void capabilities. The surface is functional for basic workflows but has minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues