Skip to main content
Glama
khairulimran-97

Bayarcash MCP Server

by khairulimran-97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bayarcash MCP Server

No user-submitted related servers found.

    Related Servers

    • Payoza MCP Server

      Payoza
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects the Payoza crypto payments API to AI assistants, enabling users to manage transactions, subscriptions, and payment links across multiple blockchains. It provides a comprehensive suite of tools for handling checkout sessions, customers, and real-time revenue analytics through natural language commands.
      -

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

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

    • 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.
      -
    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 options. However, get_transaction and get_transaction_by_order could cause confusion as they both retrieve transaction details but by different identifiers, potentially leading to misselection if the agent is unclear about the available IDs.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as create_payment_intent, get_fpx_banks, and list_transactions. This predictability makes it easy for an agent to understand and navigate the tool set without ambiguity in naming conventions.

    Tool Count5/5

    With 8 tools, the server is well-scoped for payment processing, covering key operations like creating intents, retrieving details, and listing transactions. Each tool serves a clear purpose, and the count aligns with typical domain needs without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for payment processing, including creation, status checks, and transaction retrieval. A minor gap exists in the lack of update or delete operations for payment intents or transactions, which might limit agent flexibility in handling errors or modifications, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources