Skip to main content
Glama
theYahia

@theyahia/yookassa-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @theyahia/yookassa-mcp

No user-submitted related servers found.

    Related Servers

    • @theyahia/tkassa-mcp

      theYahia
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for T-Kassa (T-Bank/Tinkoff) payment API. Provides 16 tools for payments, refunds, recurring charges, customer management, saved cards, SBP, receipts, and T-Invest portfolio.
      35 npm
      MIT

    • robokassa-mcp

      artgas1
      A
      license
      A
      quality
      D
      maintenance
      MCP server for the Robokassa payment gateway, enabling AI agents to create invoices, check payments, process refunds, manage recurring subscriptions, and handle fiscal receipts via natural language.
      18
      1
      MIT

    • zen-mcp

      krystiangw
      A
      license
      A
      quality
      B
      maintenance
      MCP server for ZEN.com Payment Gateway enabling payment links, transaction lookup, refunds, payouts, and reporting.
      14
      21 npm
      MIT

    • lzt-dev-mcp

      open-lzt
      A
      license
      B
      quality
      A
      maintenance
      MCP server for lolzteam/lzt.market ecosystem providing 29 tools for raw API requests, flow scenario management, event subscriptions, and API introspection.
      29
      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/5.0

    Scored across 20 tools

    Disambiguation4/5

    Tools are largely distinct by resource and action, but the multiple 'create payment' variants (standard, SBP, split, recurring) could cause initial confusion. Descriptions clarify their unique purposes, so agents can differentiate with careful reading.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, capture_, cancel_, delete_, save_). The pattern is predictable and makes the function of each tool immediately clear.

    Tool Count4/5

    20 tools covers a broad payment API surface, but each tool maps to a distinct operation (payments, refunds, receipts, payouts, webhooks, shop info). The count is slightly above the ideal 3-15 range, but justified by the domain's complexity.

    Completeness4/5

    The core payment lifecycle is well covered (create, get, list, capture, cancel), along with refunds, receipts, payouts, and webhooks. Missing list_payouts and a get_receipt are minor gaps, but agents can still perform essential workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources