Skip to main content
Glama
Paymos-labs

Paymos MCP Server

Official
by Paymos-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Paymos MCP Server

No user-submitted related servers found.

    Related Servers

    • Yolfi MCP Server

      mKaplan88916
      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.
      -
    • cryptbrew-mcp by cryptbrew

      cryptbrew-mcpofficial

      cryptbrew
      A
      license
      A
      quality
      B
      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
    • cryptunnel-mcp by cryptunnel

      cryptunnel-mcpofficial

      cryptunnel
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create/get/list/cancel target the invoice lifecycle, simulate_invoice_payment is explicitly sandbox-only, and verify_webhook_signature is a local crypto check. No overlap or ambiguity between any two tools.

    Naming Consistency5/5

    All six tools follow a consistent verb_noun snake_case pattern (create_invoice, get_invoice, list_invoices, cancel_invoice, simulate_invoice_payment, verify_webhook_signature). The singular/plural shift (get_invoice vs list_invoices) is idiomatic and does not hurt predictability.

    Tool Count5/5

    Six tools is well-scoped for an invoice/payment server, covering CRUD reads/writes plus sandbox and webhook concerns without padding. Each tool earns its place with no redundant variants.

    Completeness4/5

    Core lifecycle (create, get, list, cancel) plus sandbox testing and webhook verification is covered, with no obvious dead ends for standard flows. Minor gaps exist — no refund/dispute tool and no manual (non-sandbox) payment status adjustment — but these are edge operations agents can work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources