← Back to directory
MCP ServerCommunity

Yolfi provides MCP tools for integrating crypto and stablecoin payments, including payment links, Checkout Sessions, payment status checks, and webhooks. It can also update organization settings and settlement wallet configuration through Yolfi's API. Developers and technical operations staff at advisory firms building crypto payment workflows would use it rather than portfolio trading or research teams.

crypto paymentsstablecoinspayment linkssubscriptionswebhooksdeveloper tools
Status
Community
Auth
OAuth
Hosting
Both
Community rating
Not rated yet
Role

Provides one system's data and actions. Reads and writes inside a single product of record; it can act, but only within its own walls. More on System servers → All seven roles →

Open documentation →

Caveats

  • The vendor describes payments as non-custodial, with merchants receiving funds directly into their wallets. This custody claim has not been independently verified; the supplied material does not establish broader payment-data retention practices.
  • Vendor-documented tools can create payments and checkout resources, change settlement settings, and modify or remove webhooks. This is not read-only access; securities or crypto trading order execution is not documented.
  • Vendor-reported availability depends on the connected backend and account settings. Checkout Sessions and settlement merge require supporting endpoints; recurring links require account support, and standalone Checkout Sessions support only one-time payments.
  • Remote MCP uses host-managed OAuth, while local MCP uses a stored credential. The vendor states that deployed applications need separately provisioned credentials and must not reuse the MCP host's OAuth session.
  • The vendor documents local storage of credentials and webhook signing secrets in a protected configuration file. Production webhook secrets must be provisioned separately rather than relying on a developer machine's configuration.
  • The repository lists an MIT license. Vendor documentation explicitly distinguishes successful authorization and local tests from live payment and webhook verification; end-to-end operation has not been independently verified.
  • Start with read-only scopes and keep client-side approval prompts on until the connection is proven.
Rate this server

How to connect Yolfi

Step 1

Remote server: paste a URL

Yolfi publishes a remote (Streamable HTTP) endpoint, so nothing is installed locally. Add it as a custom connector in Claude, ChatGPT or your IDE and paste the endpoint below.

Endpoint

https://app.yolfi.com/mcp

Client config snippet

{
  "mcpServers": {
    "21e58311-74fb-4bea-ad27-418cffb43e05": {
      "url": "https://app.yolfi.com/mcp"
    }
  }
}

Step 2

Authenticate with OAuth

Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Crypto & Digital Assets.

Digital asset holdings snapshot

One consolidated view across exchanges and wallets.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: consolidate my digital asset holdings across every connected source, exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs, into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.

Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.

Cost basis and realised gains review

A tax-ready view of what was sold and when.

Crypto & Digital AssetsCrypto & Digital AssetsAccounting & Tax

Read-only: list realised gains and losses on digital assets for <tax year> by combining exchange transaction history with on-chain transfer data, then compare the result to what is already recorded in my accounting or tax system. Show acquisition date, disposal date, proceeds, basis and the source tool for each line, and flag every transaction where basis is missing, inferred, or disagrees between the exchange and the books. Do not file, submit, amend or post any journal entry. This is a working draft for the tax preparer.

Guardrail · Draft only. Crypto basis data is often incomplete, verify before filing.

Venue and counterparty risk review

Where the assets actually sit and what that exposes you to.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: map where my digital asset exposure actually sits by combining exchange or custodial venue data, on-chain wallet and staking or DeFi data, and any crypto exposure held through brokerage accounts. For each venue describe the counterparty, smart-contract and liquidity risk, and note any concentration above <threshold>% of total digital assets across all sources combined. State which figures came from which tool and what you could not verify on-chain. No recommendations to move funds and no transactions.

Guardrail · Read-only. Never approve token allowances or transactions from a chat session.

Read the full connection guide →