Skip to main content
Glama
sim0ple

aba-payway-mcp

by sim0ple
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to aba-payway-mcp

No user-submitted related servers found.

    Related Servers

    • PCP MCP Server by PAYONE-GmbH

      PCP MCP Serverofficial

      PAYONE-GmbH
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and LLMs to interact with the PAYONE Commerce Platform through MCP tools for managing commerce cases, checkouts, payments, orders, and payment information.
      -

    • PayBridgeNP MCP Server

      paybridgenp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.
      8 npm
      1
      MIT

    • @deonpay/mcp-server

      hectortemich
      A
      license
      A
      quality
      D
      maintenance
      Talk to your DeonPay merchant account from any MCP-compatible AI host. Enables reading transactions, creating payment links, inspecting subscriptions, and more.
      20
      2 npm
      MIT
    • @payre/mcp by Payre-IO

      @payre/mcpofficial

      Payre-IO
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Payre's Web3 payment gateway for generating crypto checkout invoices, monitoring settlements, managing payout destinations, and inspecting analytics.
      18
      -
    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

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is minor overlap between check_transaction and get_transaction_details, and between create_payment_link and purchase. Descriptions clarify these differences sufficiently.

    Naming Consistency4/5

    All tools share the 'payway_' prefix and use snake_case, but the naming pattern is not uniform: 'docs', 'purchase', and 'exchange_rate' deviate from the verb_noun structure. Still, the overall style is consistent and predictable.

    Tool Count5/5

    12 tools is well-scoped for a payment gateway MCP, covering QR generation, payment links, transactions, refunds, exchange rates, and documentation without being overwhelming or thin.

    Completeness4/5

    The surface covers core payment operations (create, check, list, refund, close) and additional utilities like exchange rates and docs. Minor gaps exist (e.g., no payment link update/delete, no webhook management), but these are not critical for typical workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources