Skip to main content
Glama
Paymos MCP Server

Paymos MCP Server

Official
by Paymos-labs

Related Servers

Alternatives to Paymos MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin crypto checkout into applications by registering workspaces, configuring settlement wallets and webhooks, creating payment links and invoices, and verifying payment status and webhook signatures. It exposes these payment operations as tools over stdio so agents can complete end-to-end payment setup without manual dashboard work.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to answer Cryptbrew product questions and check live API health without merchant authentication. Exposes tools for pricing, FAQs, invoice flow, and health probes over stdio or streamable HTTP.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to create and look up crypto payments over stdio, returning checkout links, payment statuses, paged payment lists, and receivable currencies, with real payments gated behind an explicit opt-in environment flag.
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to create Snap payments, check transaction status with a safe-to-fulfill verdict, perform production-gated transaction actions, verify webhook signatures, send signed test webhook notifications to local handlers, and search payment gateway documentation.
      566 npm
      MIT

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: invoices, payment channels, channel deposits, webhook verification, and integration recommendation are cleanly separated. Sandbox simulation tools are explicitly scoped to their respective resources, and CRUD-style operations are unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, such as create_payment_channel, get_invoice, list_invoices, and cancel_invoice. The resource ordering in simulate_invoice_payment versus simulate_payment_channel_deposit is slightly different but still predictable and readable.

    Tool Count5/5

    Fifteen tools is well-scoped for a payment platform covering invoices, payment channels, sandbox simulation, and webhook verification. Each tool maps to a meaningful operation without obvious redundancy.

    Completeness4/5

    The surface covers core invoice and payment channel lifecycles, including create, read, list, cancel, block/unblock, deposits, and sandbox simulation. Minor gaps exist around refunds, disputes, or webhook endpoint management, but the main workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues