Skip to main content
Glama
georgi-shulev

Yugo MCP Server

Related Servers

Alternatives to Yugo MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      18 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Centralizes payment gateway integrations for Pagar.me (customers, recipients, Pix, credit card, splits, charges) and Woovi/OpenPix (Pix charges, refunds, webhook verification) through MCP tools.
      3 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Velo Payments APIs for global payment operations, automatically generated using AG2's MCP builder from the Velo Payments OpenAPI specification.
      -
    • 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.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables interaction with the Conekta payment API to manage orders, customers, subscriptions, and financial transactions. It provides a comprehensive suite of tools for core payment operations like processing refunds, creating checkouts, and monitoring account balances.
      32
      2
      -

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource (payin, payout, bank, account) and action (create, list, get). The only potential confusion between create_payin and create_payout is resolved by the resource name in each.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern, using 'create_' for creation, 'get_' for retrieval, plural nouns for list operations, and '_by_id' for single item details. This makes the naming predictable and unambiguous.

    Tool Count5/5

    Eight tools adequately cover the core payment operations (create and query payins/payouts) along with supporting resources (banks, accounts). This is well-scoped for a payments server without unnecessary bloat.

    Completeness4/5

    The tool surface covers creation and retrieval for payins and payouts, plus listing banks and accounts. While there is no cancel or update operation, these are not essential for a payment flow; a cancel for payouts could be a minor addition but the current set is functionally sufficient.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues