Skip to main content
Glama
cryptunnel-mcp

cryptunnel-mcp

Official
by cryptunnel

Related Servers

Alternatives to cryptunnel-mcp

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
      B
      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.
      38
      532 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to accept non-custodial crypto payments by creating hosted checkout sessions and invoices, tracking payments and wallets, registering and verifying signed webhooks, purchasing prepaid credits, and querying or exporting the book of record. Test-mode payment simulation lets agents verify the full flow end to end.
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation on a distinct resource: create_payment (create checkout), get_payment (single lookup by id), list_payments (paged enumeration), list_currencies (static currency catalog). No two tools overlap in purpose and the descriptions reinforce the boundaries (e.g. get_payment needs the id from create_payment).

    Naming Consistency5/5

    Consistent snake_case verb_noun pattern throughout (create_payment, get_payment, list_payments, list_currencies). The singular/plural resource suffix follows a predictable creates-one vs lists-many convention.

    Tool Count4/5

    Four tools is slightly thin but well-matched to a narrowly scoped payment-checkout surface. Each tool earns its place with no redundancy, though the set is at the low end of the typical 3-15 range.

    Completeness4/5

    Covers the core accept-a-payment lifecycle: create checkout, poll status (created→pending→confirmed/failed/expired), enumerate by external_id, and enumerate receivable currencies. No explicit cancel/refund tool, but these are plausibly out of scope for a checkout-only surface, so only a minor gap remains.