Skip to main content
Glama

Related Servers

Alternatives to monapay-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to integrate MONA Pay payments directly from the IDE, including creating VietQR codes, checking transactions, configuring and testing webhooks, verifying HMAC signatures, and generating webhook sample code.
      17
      112 npm
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      A unified MCP server that lets AI agents (Claude Code, Codex, Cursor) deploy web apps and VPS instances, provision Supabase-compatible Postgres/Auth/Storage databases, register DNS domains, and send transactional email using a shared MONA Pass identity and VND wallet. It also embeds MONA Pay tooling for VietQR top-ups, checkout, webhooks and reconciliation, so agents can handle payment requests, budget approvals and resource lifecycles end to end.
      186
      393 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.
      -
    • 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
      393 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, reserve, and buy .vn and international domains in VND directly from coding environments like Claude Code, Codex, and Cursor.
      MIT

    TDQS

    B3.4/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (checkouts, QR, webhooks, email, Zalo, keys, transactions), and the OTP/verification tools are well differentiated. The main overlap is monapay_me vs monapay_whoami, which both return account/connection profile info and could be confused, plus three separate 'verify_*' tools that need careful reading.

    Naming Consistency4/5

    Nearly everything follows a consistent monapay_verb_noun snake_case pattern (get_checkout, create_webhook, delete_zalo_group), which is very predictable. A few noun-only outliers (monapay_me, monapay_whoami, monapay_quickstart) break the verb pattern slightly.

    Tool Count2/5

    50 tools is heavy; while the domain genuinely spans multiple subsystems (bank linking, checkouts, QR, webhooks, email, Zalo, API keys), the surface is large enough to strain selection and could be consolidated (e.g. unified notification-channel CRUD). It sits at the extreme end of the recommended range.

    Completeness5/5

    Coverage is thorough: full CRUD plus test/logs/stats for webhooks, email and Zalo; a complete 4-step bank-linking OTP flow; checkout lifecycle (create/get/list/cancel); transactions, summaries, key management, signature verification and sandboxing. No obvious dead ends for the stated payment-receiving domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues