Skip to main content
Glama
sepehr071

payping-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to payping-mcp

No user-submitted related servers found.

    Related Servers

    • Stax Payments MCP Connector

      IndianMarshmello
      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

    • @deonpay/mcp-server

      hectortemich
      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
      10 npm
      MIT

    • MyFatoorah MCP

      kuwaitdevs
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP hosts like Claude, VS Code, Cursor, and others to discover payment methods, create payment links, verify payments, inspect invoices, and manage refunds through focused tools, with a guided safe payment workflow and a restricted generic API escape hatch.
      7
      25 npm
      MIT
    • cryptunnel-mcp by cryptunnel

      cryptunnel-mcpofficial

      cryptunnel
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to create and look up crypto payments over stdio, returning checkout links, payment statuses, paged payment lists, and receivable currencies, with real payments gated behind an explicit opt-in environment flag.
      4
      MIT
    • Paymos MCP Server by Paymos-labs

      Paymos MCP Serverofficial

      Paymos-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      A local stdio server that lets coding agents build and verify a merchant payment integration against a sandbox, creating and cancelling invoices, simulating payment outcomes, checking invoice status, and validating webhook signatures. It also serves embedded docs as resources and refuses live or payout keys, keeping all work out of production paths.
      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.6/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool maps to a distinct action+resource: get vs list is consistently signalled by singular/plural names, and create/send operations are clearly separated. Descriptions explicitly clarify overlaps, such as list_transactions vs get_payment, so an agent can select the right tool without ambiguity.

    Naming Consistency5/5

    All tool names use the same payping_ prefix and snake_case verb_noun pattern. Verbs are predictable (get, list, create, send) and resource names are consistent across pairs.

    Tool Count4/5

    21 tools is on the heavy side for a single MCP server, but each maps to a distinct PayPing resource or action such as customers, products, coupons, invoices, payments, and withdrawals. The surface is broad rather than redundant, so it remains reasonable though somewhat large.

    Completeness3/5

    The set covers list/get for most resources and create/send for key workflows, including invoices, payment links, customers, products, and coupons. However, it lacks update/delete operations for mutable resources and has no refund or invoice-cancel tools, which are notable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources