Skip to main content
Glama
depixapp

depix-mcp

Official
by depixapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to depix-mcp

No user-submitted related servers found.

    Related Servers

    • AdvinPay MCP by AdvinPay

      AdvinPay MCPofficial

      AdvinPay
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server to connect AI assistants to the AdvinPay payment API, enabling PIX charges, transaction queries, and documentation search.
      MIT

    • PagSeguro

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to manage PagSeguro/PagBank payments, including orders, charges, checkouts, and public keys via official API.
      MIT

    • lipila-mcp

      zencoder01
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Lipila payment gateway, enabling AI agents to initiate mobile money and card collections, disburse funds, check transaction statuses, and verify webhook callbacks.
      1
      -

    • abacatepay-mcp

      JulioPeixoto
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating with Abacate Pay API, enabling management of customers, billings, PIX QR codes, and discount coupons via AI assistants like Claude.
      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/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource (product, checkout, wallet) or action (create, get, list, update, activate, deactivate, set_featured, simulate, wait_for). No two tools have overlapping purposes; even similar ones like list_checkouts and list_product_checkouts are differentiated by scope and description.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., create_product, get_checkout, wait_for_checkout). Verbs are descriptive and uniform across the set.

    Tool Count5/5

    16 tools is well-scoped for a payment and wallet server. Each tool covers a necessary operation without redundancy or bloat, staying within the optimal 3-15 range (just slightly above) and justifying its presence.

    Completeness4/5

    The tool surface covers product lifecycle (CRUD, activation, featured), checkout management (create, get, list, simulate, wait), and wallet status queries. Missing features like refunds or checkout cancellation are minor gaps given the server's stated purpose of Pix payments via hosted pages.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources