Skip to main content
Glama
payrehq

@payre/mcp

Official
by payrehq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @payre/mcp

No user-submitted related servers found.

    Related Servers

    • Payoza MCP Server

      Payoza
      F
      license
      Not graded
      quality
      D
      maintenance
      Connects the Payoza crypto payments API to AI assistants, enabling users to manage transactions, subscriptions, and payment links across multiple blockchains. It provides a comprehensive suite of tools for handling checkout sessions, customers, and real-time revenue analytics through natural language commands.
      -
    • MercanPay MCP Server by MercanPay

      MercanPay MCP Serverofficial

      MercanPay
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to create, look up, list, and cancel crypto invoices, manage reusable payment links, check USDT and TRX rates, and simulate test payments through a secure API.
      7
      MIT

    • perly-pay-mcp

      volodymyrslipak
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an AI coding assistant to create and manage products, prices, payment links, invoices, customers, subscriptions, entitlements, refunds, and webhooks, simulate test payments, read payments and receipts, and verify buyer access through a crypto payment API.
      0
      MIT

    • BlindPay MCP Server

      blindpaylabs
      A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to interact with BlindPay's stablecoin payment infrastructure, allowing users to create receivers, process payouts and payins across multiple blockchains, manage virtual accounts and wallets, and configure payment operations through natural language.
      93
      1,022 npm
      9
      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.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Business-related tools (list, get, create, update, delete, switch) are clearly separated, and invoice, transaction, stats, chain, webhook, and key tools have unambiguous purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_invoice, get_business, list_transactions). There are no mixed conventions or vague verbs.

    Tool Count5/5

    With 18 tools, the server covers merchant profile, business management, invoices, transactions, stats, chains, webhooks, and API keys. Each tool serves a clear function without redundancy or excessive bloat.

    Completeness4/5

    The server provides comprehensive coverage of merchant payment workflows including business CRUD, invoice lifecycle, transactions, stats, and webhook introspection. Minor gaps like lack of invoice update or webhook configuration updates are non-critical and workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources