Skip to main content
Glama
Sign In
crypto-payment-gateway-farsi

crypto-payment-gateway-farsi

by plilian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to crypto-payment-gateway-farsi

No user-submitted related servers found.

    Related Servers

    • Magpie MCP Server

      domdanao
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Magpie Payment Platform APIs for processing payments, creating checkout sessions, sending invoices, and managing payment links through natural conversation.
      24 npm
      2
      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
      447 npm
      9
      MIT
    • CoinVello MCP Server

      CoinVello MCP Serverofficial

      CoinVello
      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

    • Fin-MCP Payment Server

      Veri5ied
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with multiple payment providers (Stripe, Paystack) through a unified API. Supports payment initialization, verification, refunds, customer management, and invoicing without requiring knowledge of specific provider implementations.
      2
      -
    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

    B3.3/5.0

    Scored across 33 tools

    Disambiguation3/5

    Most account, store, wallet, credit, and invoice operations are distinguishable, but there is meaningful overlap between theypaid_create_invoice and theypaid_create_payment_link, and among theypaid_get_invoice, theypaid_check_payment, theypaid_recheck_invoice, and theypaid_wait_for_payment. Descriptions clarify boundaries somewhat, but an agent could still misselect among payment-status tools.

    Naming Consistency5/5

    All tools consistently use the theypaid_ prefix and snake_case, with predictable verb_noun-style naming such as get_invoice, create_invoice, and revoke_store_api_key. The convention is stable across the entire set.

    Tool Count2/5

    With 33 tools, the surface is heavy for an MCP server and exceeds the typical well-scoped range. The payment-gateway domain is broad, but several status-checking and invoice-creation tools could likely be consolidated.

    Completeness4/5

    The tool surface covers account lifecycle, store CRUD, wallet creation/connection/validation, asset status, API keys, credit top-up, invoices, and payment checking. Minor gaps remain, such as invoice cancellation/refund, wallet listing/deletion/disconnection, and possibly explicit store-asset addition.

    Resources