Skip to main content
Glama
pritam825

unified-pay-cli

by pritam825
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to unified-pay-cli

No user-submitted related servers found.

    Related Servers

    • app.wishpool/india-payments

      junter1989k-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that lets any AI agent accept payments in India via UPI, cards, netbanking, and wallets through Razorpay Payment Links. Bring your own credentials, stateless, no funds touched.
      MIT

    • Payments MCP

      lpillonwp
      A
      license
      Not graded
      quality
      D
      maintenance
      Centralizes payment gateway integrations for Pagar.me (customers, recipients, Pix, credit card, splits, charges) and Woovi/OpenPix (Pix charges, refunds, webhook verification) through MCP tools.
      6 npm
      MIT

    • razorpay-mcp

      indiamcp
      A
      license
      B
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that connects AI assistants like Claude directly to your Razorpay account.
      14
      23 npm
      1
      MIT

    • MCP Billing Gateway SDK

      sapph1re
      A
      license
      B
      quality
      D
      maintenance
      Universal billing gateway for MCP servers. Add Stripe subscription billing to any MCP server with one line of code. Supports tiered plans, usage tracking, and automatic access control.
      1
      2
      MIT

    • paymongo-mcp

      theYahia
      A
      license
      A
      quality
      B
      maintenance
      MCP server for PayMongo payment gateway (Philippines). Supports payment intents, sources, payments, refunds, and checkout sessions via Basic Auth.
      24
      16 npm
      2
      MIT

    • mcp-dev-brasil

      codespar
      A
      license
      Not graded
      quality
      C
      maintenance
      37 MCP servers for agentic commerce and Brazilian services. Covers Stripe ACP, x402 (Coinbase), AP2 (Google), Google UCP, plus 14 traditional Brazilian payment rails, fiscal, banking, communication, logistics, ERP, identity, and crypto APIs. ~480 tools. Supports stdio and Streamable HTTP.
      271
      MIT
    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.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools are clearly distinct, but create_payment_link and create_itemized_invoice both generate hosted checkout URLs, potentially causing confusion. Other tools (fees, webhooks, refunds, analytics) have clear boundaries.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (create_, compare_, trigger_, verify_, get_). The naming is uniform and predictable across the entire set.

    Tool Count5/5

    Seven tools is a well-scoped size for a payment CLI, covering common operations without overwhelming the user. Each tool addresses a distinct payment workflow, making the count appropriate.

    Completeness3/5

    Core operations like creating payments, refunds, and webhook verification are covered, but there are notable gaps such as no way to retrieve a payment by ID or list past payments. This forces agents to rely on analytics for status, which is a workaround rather than a direct access pattern.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources