Skip to main content
Glama
stables-money

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Stables MCP Server

No user-submitted related servers found.

    Related Servers

    • Yolfi MCP Server

      LanOgawa53420
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin crypto checkout, payment links, payment status checks, webhook verification, and webhook-based access logic into applications.
      MIT

    • Yolfi MCP Server

      rCho24
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based access logic into applications.
      MIT

    • Yolfi MCP Server

      emre08189
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to add stablecoin checkout, payment links, payment status checks, webhook verification, and webhook-based entitlement logic to applications. It also provides tools for workspace registration, settlement and webhook configuration, paylink creation, and crypto payment status checks.
      -
    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.4/5.0

    Scored across 51 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action, and the descriptions actively disambiguate near-pairs such as list_rfis vs list_customer_rfis, create_customer vs create_customer_onboarding_link, get_verification_link vs the onboarding link, and validate_payment_method vs create_transfer. The main friction is the same entity being called both a 'virtual account' and a 'payment route' (create_virtual_account vs update_route_destination), plus several update_* tools on routes that require reading descriptions to tell apart.

    Naming Consistency4/5

    Nearly everything follows a clear snake_case verb_noun pattern (list_/get_/create_/update_/delete_/add_/submit_/simulate_). Minor deviations: request_entitlements is a bare verb with no noun, and the vocabulary drifts between 'virtual_account' and 'route' for the same object, so the names alone are not fully predictable.

    Tool Count2/5

    51 tools is a large surface, well past the 15-tool comfort band, and the agent must choose among many closely related CRUD endpoints. The domain genuinely is broad (customers, KYC, quotes, transfers, routes, RFIs, entitlements, documents, webhooks, balance), so the tools are not gratuitous, but the count is still heavy for reliable selection.

    Completeness4/5

    Coverage is strong across the lifecycle: customers (create/update/metadata/onboarding link), transfers (create/get/list), quotes (create/get), routes (create/update/list/history/whitelist/payid), documents (add/list/download/delete), webhooks, API keys, balance, entitlements and RFIs. Gaps are modest but real: no cancel/refund a transfer, no delete/close a payment route, and no get/update for an individual webhook.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources