Skip to main content
Glama
yolfinance

Yolfi

Official
by yolfinance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Yolfi

No user-submitted related servers found.

    Related Servers

    • Yolfi MCP Server

      Nathalie2905
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to integrate stablecoin checkout, create payment links, check crypto payment status, verify webhooks, and implement webhook-based access logic through Yolfi.
      -

    • Yolfi Agent Kit MCP Server

      akiraleone14632
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to register a Yolfi workspace, create crypto paylinks and hosted checkout, poll payment status, and configure or verify signed webhooks so applications can accept stablecoin payments. Provides these payment workflows over stdio through JSON-first tools, alongside a CLI and SDK.
      -

    • Yolfi MCP Server

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

    • Yolfi MCP Server

      pandey81474
      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 access logic to applications through crypto payment APIs.
      -
    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

    A4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: organization, auth, settlements, webhooks, paylinks, and payments. Even similar-sounding tools like auth_status vs organization_get and webhooks_configure vs webhooks_verify are clearly separated by verification vs configuration intent.

    Naming Consistency5/5

    All tools share the yolfi_ prefix and follow a consistent resource_action pattern such as organization_get, paylinks_create, and webhooks_verify. Naming is uniformly snake_case with no camelCase or mixed verb styles, making the action/resource order highly predictable.

    Tool Count5/5

    13 tools is well inside the ideal range for a payment-adjacent MCP server. Each tool maps to a meaningful workflow step—registration, auth, organization settings, settlements, webhooks, paylinks, and payments—with no obvious redundancy.

    Completeness4/5

    Core lifecycles are well covered: paylinks support create/list/get/disable, payments support create/status, and webhooks support configure/verify. Minor gaps like no paylink update/enable, no payment cancellation or refund, and no webhook deletion exist, but agents can work around them by disabling/recreating paylinks or relying on existing coverage.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources