Skip to main content
Glama
Yolfi
by yolfinance

Related Servers

Alternatives to Yolfi

No user-submitted related servers found.

    Related Servers

    • 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.
      -
    • 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.
      -
    • 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
    • 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
    • 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.
      -

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation3/5

    Most resource groups are clearly separated, but three creation tools (yolfi_paylinks_create, yolfi_checkout_sessions_create, yolfi_payments_create) have overlapping purposes that require careful reading to choose correctly. The four auth tools (agent_setup_start, agent_register, agent_checkin, auth_status) also have subtle boundaries, especially since checkin is shared across two flows, and webhooks_configure vs webhooks_update blur create/update.

    Naming Consistency4/5

    The dominant yolfi_<resource>_<action> snake_case pattern is applied consistently across paylinks, checkout_sessions, webhooks, organization, and payments. Minor deviations exist: yolfi_agent_setup_start puts the verb last, yolfi_agent_checkin has no resource/action split, and yolfi_webhooks_configure is really a create operation named inconsistently with the rest of the CRUD set.

    Tool Count3/5

    At 21 tools the surface is on the heavy side for a payments server, and the auth group alone consumes four tools that could likely be consolidated. The webhook group (six tools) is defensible given full lifecycle needs, but overall the count sits at the borderline of the 16-25 range.

    Completeness3/5

    Webhooks have full CRUD plus rotate and verify, and paylinks cover create/get/list/disable, but there are notable gaps: no paylink update or re-enable, no checkout session list or cancel/expire, and no payment list or refund operation. Agents handling real payment workflows will hit dead ends around refunds and session cleanup.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues