Skip to main content
Glama
Sign In
PushinPay MCP Server

PushinPay MCP Server

Official
by Pushin-Pay
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to PushinPay MCP Server

No user-submitted related servers found.

    Related Servers

    • zen-mcp

      krystiangw
      A
      license
      A
      quality
      D
      maintenance
      MCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.
      14
      44 npm
      MIT

    • paymongo-mcp

      theYahia
      A
      license
      A
      quality
      C
      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

    • @mogintel/mcp-jazzcash

      MogIntel
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server wrapping JazzCash payment provider APIs. Enables interaction with JazzCash services through natural language.
      MIT

    • payme-mcp

      theYahia
      A
      license
      B
      quality
      F
      maintenance
      MCP server for Payme payment system (Uzbekistan). Supports transactions, statements, payment links, and balance queries via JSON-RPC 2.0.
      8
      9 npm
      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

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: balance lookup, single-transaction status lookup by ID, and PIX charge creation. There is no plausible overlap that would cause misselection, and descriptions reinforce the boundaries (e.g. criar_cobranca_pix explicitly tells the agent to prefer webhooks over polling consultar_transacao).

    Naming Consistency5/5

    All three names follow a consistent Portuguese verb_noun pattern (consultar_saldo, consultar_transacao, criar_cobranca_pix) in snake_case with no mixed conventions. The vocabulary (consultar for reads, criar for writes) is predictable and readable.

    Tool Count4/5

    Three tools is lean but each earns its place for a narrow PIX cash-in integration, covering the core read-balance, read-status, and create-charge flows. It sits at the thin end of the acceptable range, since a payments API surface would typically warrant a few more operations.

    Completeness3/5

    Core cash-in lifecycle is covered (create charge, check status, check balance), but there are notable gaps: no transaction listing/history, no cancel or refund operation, and no webhook registration or management tool despite webhooks being the recommended confirmation path. Agents hitting those needs would have no tool to call.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources