Skip to main content
Glama
artgas1

robokassa-mcp

by artgas1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to robokassa-mcp

No user-submitted related servers found.

    Related Servers

    • satsrail-mcp by SatsRail

      satsrail-mcpofficial

      SatsRail
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to accept Bitcoin Lightning payments. It allows agents to create orders, generate invoices, check payment status, and manage the full SatsRail merchant API through natural language.
      MIT

    • adaptis-mcp-server

      fredericktvf
      F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI agents interact with the Adaptis (MEG) payment gateway, enabling payment link creation, transaction queries, refunds, and integration helpers like generating signed forms and verifying callbacks.
      -

    • PagSeguro

      mcp-dir
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to manage PagSeguro/PagBank payments, including orders, charges, checkouts, and public keys via official API.
      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

    A3.6/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., hold_init, hold_confirm, hold_cancel are separate steps). The only potential confusion is between refund_create and partner_refund, but descriptions clarify the difference. Overall, tools are well-differentiated.

    Naming Consistency4/5

    Tool names predominantly follow a verb_noun pattern (e.g., build_split_invoice, create_invoice). A few deviate (hold_cancel, hold_confirm), but the naming is still predictable and readable.

    Tool Count4/5

    With 18 tools covering standard payments, holds, recurring, refunds, fiscal receipts, and utilities, the count is slightly high but well-justified for a comprehensive payment MCP server.

    Completeness4/5

    The tool surface covers core payment lifecycle operations. Missing an explicit cancel payment tool for non-hold payments, but agents can work around via states. Overall, nearly complete for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources