Skip to main content
Glama

Related Servers

Alternatives to payping-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin crypto checkout into applications by registering workspaces, configuring settlement wallets and webhooks, creating payment links and invoices, and verifying payment status and webhook signatures. It exposes these payment operations as tools over stdio so agents can complete end-to-end payment setup without manual dashboard work.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables assistants to read and modify contacts, conversations, messages, pipelines, tasks, inboxes, and AI agents through the CRM REST API, using separate read-only or read-write tool sets. Runs over local stdio or stateless Streamable HTTP with token-based scope separation.
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI clients work with one or more Stax Payments merchant accounts over stdio, discovering and switching between accounts, finding customers, listing saved payment methods, and reading transactions. Read-only by default, with opt-in write tools for creating customers, charging saved payment methods, capturing, refunding, and voiding transactions.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Lets an AI agent read a Pyxis dashboard's analytics — overviews, funnels, devices, acquisition, backend requests, visits and project settings — using a read-only access token created by an admin and revocable at any time. It runs locally over stdio, holds no state, and exposes only GET-style reads of the live Pyxis API.
      16
      2,203 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Talk to your DeonPay merchant account from any MCP-compatible AI host. Enables reading transactions, creating payment links, inspecting subscriptions, and more.
      20
      4 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair (get_payment vs list_transactions, get_withdrawal vs list_withdrawals, list_coupons vs get_coupon), and entity types (payment, customer, product, coupon, invoice, withdrawal) are clearly separated. Descriptions reinforce boundaries so an agent can reliably pick the right tool.

    Naming Consistency5/5

    Every tool uses the payping_ prefix followed by a consistent verb_noun pattern (get_, list_, create_, send_). No camelCase mixing or divergent verb styles; the convention is fully predictable.

    Tool Count4/5

    21 tools is on the heavier side, but the domain legitimately spans payments, customers, products, coupons, invoices, withdrawals, profile and sales, each with reads and creates. It is slightly wide but each tool earns its place.

    Completeness3/5

    Read coverage is thorough (list+get for every entity) and creation is covered, but there are no update or delete operations for customers, products, coupons or invoices, and no refund/payment-charge tool. These are notable gaps that leave several lifecycle operations as dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues