Skip to main content
Glama
mbilisphe13

momo-mcp

by mbilisphe13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to momo-mcp

No user-submitted related servers found.

    Related Servers

    • momo-mcp

      Tahsine
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for Mobile Money in Francophone West Africa that enables AI agents to make payments via MTN MoMo (sandbox) using tools like request_payment, check_payment_status, and disburse_payment.
      1
      MIT
    • cinetpay-mcp by cinetpay

      cinetpay-mcpofficial

      cinetpay
      A
      license
      A
      quality
      D
      maintenance
      MCP server that connects AI assistants to the CinetPay API for mobile money payments across Africa, enabling balance checks, payment initialization, transfers, and more.
      7
      8 npm
      MIT

    • Mono Banking MCP Server

      sin4ch
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to perform Nigerian banking operations including account management, payments, and identity verification through the Mono Open Banking API.
      59
      MIT

    • lipila-mcp

      zencoder01
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Lipila payment gateway, enabling AI agents to initiate mobile money and card collections, disburse funds, check transaction statuses, and verify webhook callbacks.
      1
      ISC
    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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action or resource: environment inspection, sandbox user provisioning, credential verification, balance reading, account activity checking, payment initiation, and payment status lookup. There is minimal risk of confusing tools, even though environment and verify_credentials both relate to configuration, because their outputs and purposes are explicitly different.

    Naming Consistency4/5

    All tools share a consistent momo_ prefix and snake_case formatting. The action/resource phrasing is slightly mixed (e.g., momo_environment and momo_account_balance are noun-like, while momo_verify_credentials and momo_request_to_pay are verb-like), but the pattern remains readable and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a focused MoMo payments integration surface. Each tool earns its place by covering setup, verification, account validation, payment initiation, and status checking without obvious redundancy.

    Completeness4/5

    The surface covers the core collection workflow end to end: environment discovery, credential setup and verification, account validation, payment request, and status polling. Minor gaps exist around refunds, disbursements, or transaction listing, but those may be outside the intended collections-only scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources