Skip to main content
Glama
moolrehq

moolre-mcp

Official
by moolrehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to moolre-mcp

No user-submitted related servers found.

    Related Servers

    • @saperly/mcp by Saperly

      @saperly/mcpofficial

      Saperly
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Saperly that enables AI agents to provision phone numbers, place calls, send SMS, and manage credentials via 36 tools backed by the Saperly API.
      22 npm
      3
      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

    • agentforge

      doggychip
      F
      license
      A
      quality
      F
      maintenance
      MCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.
      5
      4
      -
    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

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have distinct purposes, especially between payments, SMS, and WhatsApp. However, there is potential ambiguity among SMS-related tools (e.g., sender_id_status vs list_sender_ids, and send_sms vs send_sms_get) which could cause confusion. Descriptions help but still could be clearer.

    Naming Consistency4/5

    Tool names predominantly follow a verb_noun pattern (e.g., create_account, send_sms), but a few like account_status and sender_id_status use noun_status instead of a verb. This minor inconsistency lowers the score slightly.

    Tool Count4/5

    With 24 tools covering payments, SMS, and WhatsApp, the count is slightly high but justified by the breadth of functionality. It remains manageable and each tool has a defined role.

    Completeness3/5

    Core operations are covered (create, read, update for accounts; send and check for SMS/WhatsApp), but there are notable gaps: no tool to update or delete sender IDs, no cancellation for transfers, and no listing of generated payment IDs or bank accounts. This may cause agent failures in some workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources