Skip to main content
Glama
XENTAL-PayLibre

Xental MCP Server

by XENTAL-PayLibre
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Xental MCP Server

No user-submitted related servers found.

    Related Servers

    • Brighty MCP Server

      razz-team
      A
      license
      Not graded
      quality
      C
      maintenance
      Banking infrastructure for AI agents: open accounts, issue cards, send SEPA/SWIFT payments, run mass payouts, and pay invoices via natural language.
      2
      MIT

    • wata-mcp

      votsie
      A
      license
      C
      quality
      C
      maintenance
      Enables AI agents to manage merchant accounts, process payments, handle wallets and payouts, and sell digital goods through the wata.pro payment system.
      90
      MIT

    • paygentic

      FoxRick
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to manage financial operations including balance checks, money transfers, invoicing, spending policies, and audit logs through the PayGent API.
      13
      -
    • Juspay MCP Tools by juspay

      Juspay MCP Toolsofficial

      juspay
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with Juspay's payment processing APIs and merchant dashboard for managing orders, transactions, refunds, customers, gateways, and reporting through natural language.
      21
      Apache 2.0
    • paystack-mcp-server by PaystackOSS

      paystack-mcp-serverofficial

      PaystackOSS
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with the full range of Paystack APIs, allowing operations like transaction management, customer creation, and payments through natural language.
      2
      50 npm
      55
      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.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. For example, get_transaction, list_transactions, and transactions_summary all serve different query scopes. The CRUD operations for virtual accounts and transfers are well-separated.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., create_virtual_account, list_banks). The only deviation is transactions_summary, which uses noun_verb, causing a minor inconsistency.

    Tool Count5/5

    13 tools is a reasonable count for a payment/virtual account server. Each tool covers a necessary operation without being overwhelming or too sparse.

    Completeness4/5

    Core operations are covered: CRUD on virtual accounts, transaction retrieval, transfer initiation, bank account lookup, and simulation. Minor gaps include no get_transfer tool to fetch a single transfer by reference.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources