Skip to main content
Glama
agentpay-vn

agentpay-vn

by phuocdu

Related Servers

Alternatives to agentpay-vn

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for crypto payments: an AI agent opens its own merchant account and accepts, sends and exchanges crypto.
      32
      77 npm
      MIT
    • 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
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to make autonomous Bitcoin Lightning Network payments using the L402 protocol. Agents can pay for API access, purchase resources, and complete transactions without human intervention — invoice comes in, sats go out, done.
      17
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that lets any AI agent accept PromptPay QR, credit/debit cards, TrueMoney wallet, internet banking payments in Thailand, and check payment status.
      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
      156 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose: creating a payment request, checking status, awaiting settlement, and listing recent payments. No two tools overlap in functionality, ensuring an agent can easily select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (create_payment_request, check_payment, await_settlement, list_recent_payments). The naming is predictable and unambiguous.

    Tool Count4/5

    Four tools is a reasonable number for a focused payment processing server. While it covers core operations, it is slightly lean; adding a cancel tool might improve completeness, but the count is appropriate.

    Completeness4/5

    The tool set covers the main lifecycle of a payment request: create, check, await, and list. Missing an explicit cancel/expire function, but the await tool handles timeouts gracefully. Minor gap, but overall sufficient for typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data