Skip to main content
Glama
parseen254

daraja-mcp

by parseen254
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to daraja-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-african-markets

      mutheejj
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-aware agents to initiate M-Pesa B2C/B2B payouts, query transaction status, validate phone numbers, and reconcile M-Pesa statements against ledger CSVs to surface discrepancies, plus structured lookups for county public data and KRA tax helpers. It runs in sandbox mode by default, uses idempotency keys for safe retries, and stays read-only for reconciliation and lookups.
      MIT
    • 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
      -

    • mpesa-mcp

      gabrielmahia
      A
      license
      A
      quality
      A
      maintenance
      MCP server for East African fintech APIs — trigger M-Pesa STK Push payments, check transaction status, send SMS to 20+ African networks, and top up airtime via Africa's Talking.
      5
      34 PyPI
      4
      MIT

    • Daraja MCP

      jameskanyiri
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that integrates AI applications with Safaricom's Daraja API, enabling AI-driven financial transactions and automation through M-Pesa services.
      14
      -

    • Safaricom Daraja MCP Server

      mboya
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that integrates Safaricom's M-PESA Daraja API with Claude, enabling natural language payment processing and real-time transaction notifications.
      3
      -
    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.5/5.0

    Scored across 25 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose and target. The paired 'and_wait' variants are explicitly distinguished by their descriptions as synchronous vs asynchronous, and other tools like pull_register vs pull_transactions or check_sim_swap vs check_age_on_network are clearly delineated.

    Naming Consistency3/5

    All names use snake_case, but the word order is inconsistent: some are verb_noun (check_sim_swap, generate_qr), some noun_verb (stk_push, ratiba_create), and several are pure nouns (b2c_payment, transaction_status). This mixing makes the pattern less predictable, though still readable.

    Tool Count3/5

    With 25 tools, the server is on the heavy side of typical MCP scopes. While the number is justified by the wide range of M-Pesa APIs covered, it approaches the upper limit of what is manageable without additional organization.

    Completeness5/5

    The tool set covers the full M-Pesa transaction lifecycle: collection (C2B, STK, Ratiba), disbursement (B2C, B2B), reconciliation (pull, callbacks, transaction_status), fraud prevention (sim swap, age check, identity validation), and operational needs (health, account_balance, reversal). No major Daraja API operations are missing.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources