Skip to main content
Glama
TegroTON

Tegro.money MCP Server

Official
by TegroTON
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tegro.money MCP Server

No user-submitted related servers found.

    Related Servers

    • Alternative Payments MCP Server by WYRE-AI

      Alternative Payments MCPofficial

      WYRE-AI
      F
      license
      Not graded
      quality
      A
      maintenance
      Provides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.
      -
    • @payre/mcp by Payre-IO

      @payre/mcpofficial

      Payre-IO
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Payre's Web3 payment gateway for generating crypto checkout invoices, monitoring settlements, managing payout destinations, and inspecting analytics.
      18
      -

    • PayBridgeNP MCP Server

      paybridgenp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.
      31 npm
      1
      MIT

    • @moncashconnect/mcp

      SantaClaus007
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to interact with MonCashConnect payment data read-only, including checking balances, listing transactions, and viewing payment details, without moving money.
      3 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 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating orders, generating payment links, checking balance, and querying orders/shops. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent 'tegro_verb_noun' snake_case pattern, using standard verbs like create, get, list. No mixing of styles.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a payment system, covering order creation, payment links, balance, and listings without being excessive or too thin.

    Completeness4/5

    The tool surface covers core payment workflows (create, retrieve, list) but lacks refund/cancel capabilities, which are minor gaps but not severe for basic usage.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources