Skip to main content
Glama
muthanii

Wayl MCP

by muthanii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Wayl MCP

  • PayPal by paypal

    PayPalofficial

    paypal
    A
    license
    Not graded
    quality
    C
    maintenance
    The PayPal Model Context Protocol server allows you to integrate with PayPal APIs through function calling. This protocol supports various tools to interact with different PayPal services.
    488 npm
    194
    -

Related Servers

  • jazzcash-mcp

    theYahia
    A
    license
    A
    quality
    B
    maintenance
    MCP server for JazzCash mobile wallet and payments (Pakistan). Supports wallet payments, mobile account payments, vouchers, refunds, and balance inquiries.
    5
    7 npm
    1
    MIT

  • Satim Payment Gateway

    zakblacki
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server for integrating with the SATIM payment gateway system in Algeria, enabling AI assistants to process CIB/Edhahabia card payments through the SATIM-ePAY platform.
    5
    9 npm
    15
    GPL 3.0

  • maib-mcp

    theYahia
    A
    license
    A
    quality
    D
    maintenance
    MCP server for MAIB e-commerce payments (Moldova). Supports payments, refunds, recurring billing, one-click payments, and transaction status via OAuth 2.0.
    8
    13 npm
    MIT

  • bog-ipay-mcp

    theYahia
    A
    license
    A
    quality
    D
    maintenance
    MCP server for Bank of Georgia iPay payment gateway, enabling payment orders, refunds, recurring payments, and pre-authorization via OAuth 2.0 + JWT.
    8
    16 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.6/5.0

Scored across 18 tools

Disambiguation5/5

Every tool has a distinctly defined purpose, and the descriptions carefully cross-reference related tools (e.g., get_payment_link vs get_payment_links_batch vs check_order_paid, invalidate_payment_link vs invalidate_payment_link_if_pending). This makes selection unambiguous for an agent.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (create_, get_, list_, invalidate_, cancel_, verify_, parse_). The only outlier is wayl_status, which could have been get_status, but it remains understandable.

Tool Count4/5

18 tools is on the heavier side, but the server covers payment links, products, refunds, webhooks, and configuration—each area justifies several tools. The count feels appropriate for the scope, though some consolidation might be possible.

Completeness4/5

The core workflow (create payment link, monitor payment, verify webhook, refund) is fully covered. Minor gaps: product tools are read-only only, and there is no update operation for payment links, but these are not essential for the server's stated purpose of selling books.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources