Skip to main content
Glama
webimpianteam

Bayarcash MCP Server

by webimpianteam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bayarcash MCP Server

No user-submitted related servers found.

    Related Servers

    • OPSG MCP Server

      fredericktvf
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to manage transactions, initiate payments, and integrate with the OPSG/iPay88 payment gateway using local merchant credentials.
      -

    • Magpie MCP Server

      domdanao
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Magpie Payment Platform APIs for processing payments, creating checkout sessions, sending invoices, and managing payment links through natural conversation.
      20 npm
      2
      MIT

    • PayArk MCP Server

      Payark-Inc
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI agents to Nepal's payment infrastructure through the PayArk API. It enables users to monitor transaction history, manage projects, and generate hosted checkout links using natural language.
      11 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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have distinct purposes, such as create_payment_intent for initiating payments and get_fpx_banks for retrieving bank lists. However, get_transaction and get_transaction_by_order could be slightly confusing as they both retrieve transaction details using different identifiers, though their descriptions clarify the distinction.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern, such as create_payment_intent, get_fpx_banks, and list_transactions. There are no deviations in naming conventions, making the set predictable and easy to understand.

    Tool Count5/5

    With 8 tools, the server is well-scoped for payment processing, covering key operations like creating and retrieving payment intents, listing transactions, and accessing payment channels and portals. Each tool serves a clear purpose without redundancy.

    Completeness4/5

    The toolset provides good coverage for payment processing workflows, including creation, status checks, and transaction retrieval. A minor gap is the lack of tools for updating or canceling payment intents, which might limit full lifecycle management, but core operations are well-covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources