Skip to main content
Glama
theYahia

bog-ipay-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bog-ipay-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • bepaid-mcp

      theYahia
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for bePaid payment gateway enabling payment operations including create, capture, void, refund, card tokenization, and subscriptions through natural language prompts.
      17 npm
      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

    • paymongo-mcp

      theYahia
      A
      license
      A
      quality
      B
      maintenance
      MCP server for PayMongo payment gateway (Philippines). Supports payment intents, sources, payments, refunds, and checkout sessions via Basic Auth.
      24
      12 npm
      2
      MIT

    • @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

    • payme-mcp

      theYahia
      A
      license
      B
      quality
      F
      maintenance
      MCP server for Payme payment system (Uzbekistan). Supports transactions, statements, payment links, and balance queries via JSON-RPC 2.0.
      8
      4 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

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct payment operation: auth, order creation, status check, refund, recurring setup/charge, preauth and capture. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., get_auth_token, create_order, refund_order). Even compound verbs like preauth_order fit the pattern.

    Tool Count5/5

    8 tools is well-scoped for a payment processing server, covering core payment lifecycle without unnecessary bloat.

    Completeness4/5

    Covers the main payment lifecycle: auth, create, status, refund, recurring, preauth/capture. Missing explicit cancel/void for orders and recurring cancellation, but core workflows are functional.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources