Skip to main content
Glama
Sign In
hectortemich

@deonpay/mcp-server

by hectortemich
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to @deonpay/mcp-server

No user-submitted related servers found.

    Related Servers

    • wata-mcp

      votsie
      A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to manage merchant accounts, process payments, handle wallets and payouts, and sell digital goods through the wata.pro payment system.
      90
      MIT
    • PCP MCP Server by PAYONE-GmbH

      PCP MCP Serverofficial

      PAYONE-GmbH
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and LLMs to interact with the PAYONE Commerce Platform through MCP tools for managing commerce cases, checkouts, payments, orders, and payment information.
      -

    • 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
      37 npm
      MIT

    • aba-payway-mcp

      sim0ple
      A
      license
      A
      quality
      D
      maintenance
      Enables MCP-compatible AI tools to create checkouts, generate KHQR codes, check/list transactions, issue refunds, create payment links, and pull exchange rates via ABA Bank's PayWay API.
      12
      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.3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create, get, list, update) for specific entities like products, links, subscriptions, customers, and transactions. Even similar-sounding tools (e.g., get_subscription vs get_customer_subscription) are clearly differentiated by scope (plan vs individual subscriber).

    Naming Consistency5/5

    All tools follow a consistent `deonpay_<verb>_<resource>` pattern in snake_case (e.g., deonpay_create_product, deonpay_list_transactions). There are no deviations, making the convention predictable and easy to navigate.

    Tool Count5/5

    20 tools cover the key operations for a payment processing domain (CRUD for products, links, subscriptions, customers, transactions, plus metrics and checkout). The count is well-scoped—neither excessive nor insufficient—for the apparent purpose.

    Completeness4/5

    The tool surface covers core workflows (create/read/update/list for products and links, list/read for customers and transactions, subscription management). Minor gaps exist: lack of update_subscription (plans) and cancel customer subscription. Otherwise, the set is thorough.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources