Skip to main content
Glama
Bigabou007-dev

WariMCP

by Bigabou007-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to WariMCP

No user-submitted related servers found.

    Related Servers

    • PayLink MCP Server by paylink-ai

      PayLink MCP Serverofficial

      paylink-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      Open-source MCP server that streamlines payment integration for AI agents and financial apps in Africa, providing unified tools for providers like M-Pesa.
      1
      -

    • lipila-mcp

      zencoder01
      F
      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
      -

    • Interswitch MCP Server

      Dairus01
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Interswitch APIs for payments, transfers, VAS, cardless paycodes, Transaction Search, Card 360, lending, payouts, agency banking, and fintech card-processing utilities.
      74
      35 npm
      1
      MIT

    • momo-mcp

      Tahsine
      A
      license
      Not graded
      quality
      C
      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.
      MIT

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      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.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Tools are mostly distinct, but initiate_payment and generate_payment_link both create payment flows, which could cause confusion. Other tools (verify, refund, list, payout) are clearly separated.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear verbs (list, initiate, verify, refund, generate) and nouns (providers, payment, link, payout, transactions). No mixed conventions.

    Tool Count5/5

    8 tools is well-scoped for a payments server, covering payment and payout operations without unnecessary bloat.

    Completeness4/5

    The server covers the main payment lifecycle (initiate, verify, refund, list) and payout lifecycle (initiate, verify). Missing a dedicated single-transaction retrieval or cancel operation, but these can be worked around with list/verify.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources