payping-mcp
Related Servers
Alternatives to payping-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents and CLI users to perform confirmed shop operations, manage products, orders, collections, webhooks, and promotions, and handle bounded metadata exports and private uploads through a local stdio server.8616 npmAGPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables 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.-

Evo CRM MCPofficial
AlicenseBqualityCmaintenanceEnables 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.12MIT- AlicenseNot gradedqualityBmaintenanceLets 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
- AlicenseAqualityAmaintenanceLets 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.162,203 npmMIT
- AlicenseAqualityDmaintenanceTalk to your DeonPay merchant account from any MCP-compatible AI host. Enables reading transactions, creating payment links, inspecting subscriptions, and more.204 npmMIT
TDQS
Scored across 21 tools
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.
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.
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.
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.