Skip to main content
Glama
danchev

SpherePay MCP Server

by danchev

Related Servers

Alternatives to SpherePay MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and MCP hosts to register a workspace, create stablecoin checkout and payment links, configure webhooks, verify crypto payment status, and add webhook-based access logic to applications.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI tools to manage financial operations through the Cresium Partner API, including transactions, payments, invoices, and wallet balances. It supports secure workflows such as bank address lookups, transfer previews, and signature request management.
      12
      5
      MIT
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to set up CoinPay crypto payments in one idempotent pass: provisioning payout addresses, a business, payout wallets, webhooks, and supported coins. It also supports creating, checking, and verifying payments through the CoinPay API.
      269 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents and MCP hosts to register payment workspaces, create stablecoin paylinks, configure webhooks, verify payment signatures, and check payment status so applications can add hosted crypto checkout and webhook-based entitlements without manual dashboard setup.
      MIT

    TDQS

    B3.4/5.0

    Scored across 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear descriptions that prevent ambiguity between similar entities like wallets, offloader wallets, and virtual accounts.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern, but creation operations use varying verbs (create, onboard, setup) instead of a single convention, which is a minor inconsistency.

    Tool Count4/5

    24 tools is slightly above the typical well-scoped range, but still reasonable for the breadth of functionality covered in a payment platform.

    Completeness3/5

    The tool set covers core workflows but lacks update or delete operations for entities like customers, bank accounts, and webhooks, which could hinder full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues