Yolfi
OfficialRelated Servers
Alternatives to Yolfi
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAccept crypto payments from AI agents: create an invoice in one call and get a hosted checkout link (USDC/USDT on Celo, Base, Arbitrum, Polygon, BSC). No API key, instant self-custody settlement.MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to perform financial transactions such as direct payments, escrows, and bounty management using natural language with zero code integration. It provides a comprehensive suite of tools for fund streaming, subscriptions, and reputation tracking to facilitate secure agent-to-agent commerce.3 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to autonomously invoice, receive payments, and settle micro-transactions in USDC via Moove Agentic Payments, using cryptographic hash commitments for zero-custody fair exchange.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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-

PayAgents MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to autonomously make policy-controlled payments for APIs and tools via Bitcoin Lightning (L402) and Base USDC (x402), including paying paywalled endpoints, checking balances, and reviewing transactions.314 npmMIT- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to safely integrate cross-border payments by providing structured payment knowledge, deterministic validation of idempotency, security, and state-machine rules, webhook testing, executable pytest generation, and diagnosis for Python/FastAPI Checkout projects.-
TDQS
Scored across 13 tools
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.
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.
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.
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.