Skip to main content
Glama
mrslbt

paypay-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to paypay-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      21 npm
      MIT

    • bog-ipay-mcp

      theYahia
      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

    • 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
      12 npm
      2
      MIT

    • btcpayserver-mcp

      Abhijay007
      A
      license
      B
      quality
      F
      maintenance
      A comprehensive Model Context Protocol (MCP) server for BTCPayServer integration, providing tools for payment processing, store management, user administration, webhook handling and more with full API coverage.
      3
      8 npm
      3
      MIT

    • idpay-mcp

      theYahia
      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

    • @imazhar101/paypal-mcp

      imazhar101
      A
      license
      A
      quality
      C
      maintenance
      A lightweight MCP server that connects to the PayPal REST API, handling token lifecycle automatically and providing read-only tools for transactions, invoices, orders, disputes, and subscriptions by default.
      11
      9 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.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    create_qr_code and delete_qr_code are clearly distinct lifecycle actions, and get_payment_details vs wait_for_payment are differentiated as one-off status checks vs polling. There is slight conceptual overlap between the two payment-status tools, but the descriptions make the intended use clear.

    Naming Consistency5/5

    All tool names follow a consistent verb-first snake_case pattern: create_qr_code, get_payment_details, delete_qr_code, wait_for_payment. The naming is predictable and easy to reason about.

    Tool Count5/5

    Four tools is appropriate for a narrowly scoped PayPay QR code payment server. The count feels focused rather than sparse, with no redundant or filler tools.

    Completeness4/5

    The core lifecycle is covered: create a QR code, poll/wait for payment, fetch payment details, and invalidate an unpaid QR code. A refund/cancel operation is absent even though REFUNDED appears in the status enum, but this is likely beyond the server's primary checkout-focused scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources