Skip to main content
Glama
CedricConday

Centrapay MCP Server

by CedricConday

Related Servers

Alternatives to Centrapay MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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.
      32 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables integration with PayPal APIs for managing invoices, payments, disputes, subscriptions, and more through natural language.
      488 npm
      12
      Apache 2.0
    • A
      license
      A
      quality
      F
      maintenance
      Enables managing CloudPayments operations including one-step and two-step payments, refunds, subscriptions, orders, and transaction history through natural language.
      12
      53 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to operate Xental merchant accounts via natural language, provisioning virtual accounts, monitoring transactions, and executing payouts.
      13
      MIT
    • 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.
      31 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interactions with SumUp payment services and APIs, allowing users to manage their SumUp account, process payments, and access payment data through LLM-powered conversations.
      91 npm
      7
      Apache 2.0

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource (merchant or payment request) and action (create, get, list, pay, void, refund). No overlap between merchant and payment operations, and payment operations are clearly differentiated by action.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., create_merchant, get_payment_status, void_payment_request). No mixing of styles or ambiguous names.

    Tool Count5/5

    9 tools is well-scoped for a payment/merchant server covering core CRUD and lifecycle operations. Not excessive nor insufficient for the domain.

    Completeness5/5

    The tool set covers merchant management (create, get, list) and full payment lifecycle (create, status, list, pay, void, refund). No obvious gaps for the intended use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues