Skip to main content
Glama
themonagroup

monapay-mcp

Official

Related Servers

Alternatives to monapay-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to manage MONA Cloud resources such as VPS and databases, use a shared VND wallet, integrate MONA Pay payments, and send transactional email via MONA Mail, all through natural language in MCP-compatible clients.
      135
      2,572 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to safely integrate cross-border payments by providing structured payment knowledge, deterministic validation of idempotency, security, and state-machine rules, webhook testing, executable pytest generation, and diagnosis for Python/FastAPI Checkout projects.
      -
    • F
      license
      A
      quality
      C
      maintenance
      Enables AI agents to integrate Tunzaa Payments by generating accurate boilerplate code and webhook handlers. Operates in mock mode by default with optional live verification against Tunzaa APIs when credentials are provided.
      10
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to integrate Midtrans payments by providing comprehensive documentation, API references, and code examples for 15+ payment methods across 5 languages. Includes tools for generating charge requests, webhook handlers, and searching documentation without requiring API keys.
      9
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Yolfi Agent Kit for AI coding agents: receive crypto, SaaS payment, stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic to applications through Yolfi
      13
      38 npm
      178
      MIT

    TDQS

    A3.5/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: profile, bank accounts, virtual accounts, QR codes, transactions, webhooks, and signature/key utilities. Even the webhook-related tools are cleanly separated by operation (create/update/delete/test/logs/stats). There is no meaningful overlap between tool responsibilities.

    Naming Consistency4/5

    All tools share the consistent monapay_ prefix, and most follow a clear monapay_verb_noun pattern. Minor deviations exist, such as monapay_me, monapay_webhook_logs, and monapay_webhook_stats, which read as noun phrases rather than action-oriented names, but the overall convention is still predictable.

    Tool Count4/5

    17 tools is slightly above the typical sweet spot for a well-scoped MCP server, but each tool earns its place in the payment/webhook lifecycle. QR management, webhook CRUD, webhook diagnostics, transaction lookup, and signature verification are all meaningful separate concerns.

    Completeness5/5

    The server covers the full incoming-payment workflow: QR creation/cancellation, bank/virtual account discovery, transaction reconciliation, webhook configuration and delivery monitoring, retry, and local HMAC verification. There are no obvious dead ends for the stated purpose of integrating with MONA Pay webhooks and VietQR payments.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues