Yolfi Agent Kit

MCP金融服务

提供方 未标注

金融服务 stdio · 本地进程 API Key 社区 / 第三方 ClaudeCursorVS CodeCodex
查看接入方式

使用公开的 Yolfi Agent Kit 创建加密货币支付链接、查询支付状态并集成结账功能。

一句话选型结论

按资料字段整理

Yolfi Agent Kit 属于金融服务类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类金融服务 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

金融服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

金融

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
npx -y @yolfi/agent help npx -y @yolfi/agent auth:status

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
行情与财务数据

查行情、财报、汇率等金融数据。

支付与账务查询

查订单、账单与交易流水。

风控与核验

做身份、信用与风险信息核验。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在金融服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Yolfi Agent Kit当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
Alpaca MCP 62 stdio · 本地进程 支持远程部署 有 2026-05-18
OpenNews MCP 11 stdio · 本地进程 支持远程部署 有 2026-05-17
MCP Server 273df76d 未标注 stdio · 本地进程 本地部署 有 2026-05-17
tradingview-mcp 未标注 stdio · 本地进程 本地部署 有 2026-04-19
goat (Goat SDK) 未标注 未标注 未标注 无 2026-05-17

服务器档案

金融服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类金融服务本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

12.8 KB
来自项目仓库与上游目录的原文,未做删改

Yolfi Agent Kit: AI Agent Payment Integration

AI agent payment integration for crypto and stablecoin checkout. @yolfi/agent provides a local MCP server, a JSON CLI, a JavaScript SDK, and the Yolfi Payments Agent Skill for payment links, Checkout Sessions, payment status checks, and signed webhooks.

For AI integration, copy this message to your agent in the project you want to integrate:```text
Add Yolfi payments to this project. Follow https://docs.yolfi.com/ai


The agent inspects the project, reuses an existing connection or selects a supported connection method, reads the account settings, and implements the requested integration. The owner completes account authorization and supplies only decisions that are missing, such as a receiving wallet or product price. Connecting the account alone does not finish the integration.

## Languages

## Choose your entry point

- **AI integration:** send the message above. The agent guide owns the workflow; SKILL.md provides the packaged instructions.
- **HTTP API:** use the API guide for authentication, request bodies, checkout, and webhooks.
- **Terminal automation:** use the commands below and the CLI reference.
- **JavaScript application:** install the SDK and use the server/runtime guidance below.

## Crypto payment integration features

- Hosted checkout and one-time payment links for SaaS products, digital downloads, credits, games, and donations.
- Recurring payment links for subscription flows supported by the Yolfi account.
- Checkout Sessions for server-priced orders with a stable idempotency key for retries.
- Payment status checks and webhook signature verification for the application's existing access and subscription logic.
- Organization settings, selected settlement wallets, and independent webhook endpoints through the existing Yolfi API.

Use the integration workflow with Codex, Claude Code, Cursor, ChatGPT, Claude, OpenClaw, Hermes, or another agent with a supported MCP connector or local tools. Browser and cloud environments need a supported remote connector when they cannot run commands. See the connection reference for the available paths in each host.

## CLI installation and authorization

Node.js 18 or later is required. Run without a global install:```bash
npx -y @yolfi/agent help
npx -y @yolfi/agent auth:status

If no local credential exists, start browser authorization:```bash
npx -y @yolfi/agent setup --agent local-agent

Open the returned loginUrl and complete owner authorization.

npx -y @yolfi/agent checkin --agent local-agent
npx -y @yolfi/agent auth:status


The agent should open the URL when its environment supports a browser and resume check-in after authorization. Repeated setup reuses an unexpired pending session from the same API environment. Account access must be checked with `auth:status`; this does not verify checkout or live webhook delivery.

Credentials and pending state are saved in `~/.yolfi/config.json` using atomic writes and process locking. Directory and file permissions are `0700` and `0600` where supported. `YOLFI_CONFIG_HOME` selects an isolated configuration directory. Explicit SDK credentials take precedence over `YOLFI_API_KEY`, which takes precedence over the stored local credential. Do not set a placeholder `YOLFI_API_KEY` when using browser authorization.

For an explicitly new account, the agent can use email-confirmed signup after the owner supplies or confirms the email and project name:```bash
npx -y @yolfi/agent auth:agent-register \
  --email "owner@example.com" \
  --project-name "My product" \
  --agent-name "My coding agent" \
  --integration-intent accept_payments

The first call sends a confirmation link. After the owner opens it, the agent repeats the same command. A generated idempotency key and pending check-in token are persisted; an optional --idempotency-key must be 16-200 characters and reused on retries. The connected credential is stored without printing it. Existing emails use browser authorization instead. A lost initial signup response is recoverable; if the one-time credential response is lost after redemption, check auth:status and start browser authorization again if needed.

MCP server for crypto payments

Use an already connected Yolfi server first. Connection selection depends on the tools available in the agent's environment, not just its brand. Full host setup instructions live in the connection reference.

An authenticated MCP connection needs no additional organization API key. Continue through its tools, including Checkout Session creation; skip local CLI setup unless a separate local workflow is actually needed. Local MCP uses its stored browser-setup credential automatically. Application server credentials are a separate concern, described below.

  • Remote Streamable HTTP: https://app.yolfi.com/mcp, with OAuth managed by the MCP host.
  • Local stdio: npx -y @yolfi/agent mcp, using the protected local credential.

A single local server provides payment tools, knowledge resources, and guided prompts:```json
{
"mcpServers": {
"yolfi": {
"command": "npx",
"args": ["-y", "@yolfi/agent", "mcp"]
}
}
}


The bundled Codex and Claude plugins start the local server. Local-only tools include `yolfi_agent_setup_start`, `yolfi_agent_checkin`, `yolfi_agent_register`, and `yolfi_webhooks_verify`. Remote MCP uses host OAuth. Verify it with `yolfi_auth_status` in that host, not a separate CLI login. An environment that cannot run commands must use a supported remote connector; the agent should explain only the required owner action if the host cannot configure it automatically.

Core tools include organization read/update, settlement configuration, webhook endpoint list/create/update/rotation/removal, paylink list/get/create/disable, `yolfi_checkout_sessions_create`, `yolfi_checkout_sessions_get`, and payment create/status. Tool availability should be read from the connected server. Checkout Session tools and settlement merge require a backend that supports those endpoints; do not silently fall back to replacing organization settlement settings.

## Reuse resources before creating them```bash
npx -y @yolfi/agent organization:get
npx -y @yolfi/agent paylinks:list --page 1 --rows 10
npx -y @yolfi/agent webhooks:list

Read all relevant pages and the project's existing configuration. Reuse approved wallets, prices, matching paylinks, and webhook endpoints. settlement:configure sends PATCH /api/private/organization/settlement-accounts, updating only supplied networks and preserving other networks. Changing an existing wallet still requires an owner-approved address.

Create JSON payload files in the target project before passing them to --json; package examples are not automatically copied there. For example, after confirming these product values:```bash
cat > yolfi-paylink.json <<'JSON'
{
"name": "Premium Download",
"price": "19",
"currency": "USD",
"type": "ONE_TIME",
"collectEmail": true
}
JSON
npx -y @yolfi/agent paylinks:create --json ./yolfi-paylink.json


See examples for payload shapes. If create times out, list resources before retrying. Webhook create is not an upsert; creating the same URL twice creates independent endpoints with different secrets.

## Webhook secrets and deployment

Local CLI/MCP create and rotate operations save the endpoint signing secret in the protected local config and return redacted metadata with `signingSecretStored: true`. Lists and updates never return the secret. Use the endpoint ID for local verification:```bash
npx -y @yolfi/agent webhooks:verify \
  --endpoint-id &lt;endpointId&gt; \
  --payload ./raw-webhook.json \
  --signature &lt;signature&gt;

YOLFI_WEBHOOK_SECRET can supply a server/CI secret. Plaintext --secret flags and MCP secret arguments are not supported; use the endpoint ID or environment. An API key or an agent credential is never a webhook signing secret.

Install the SDK for application code:```bash
npm install @yolfi/agent


For a local provisioning script, `readWebhookSigningSecret(endpointId)` retrieves a stored secret. Pass it directly to the target deployment&#x27;s secret manager or an existing ignored environment file without printing it. The app should read its deployed `YOLFI_WEBHOOK_SECRET`; it should not depend on a developer machine&#x27;s `~/.yolfi`. Direct SDK create/rotate methods return the API response so trusted server code can store the secret itself.```js
import { readWebhookSigningSecret, verifyWebhookSignature } from &#x27;@yolfi/agent&#x27;;

// Provisioning script only: pass this value to your existing secret manager.
const signingSecret = readWebhookSigningSecret(endpointId);
if (!signingSecret) throw new Error(&#x27;Stored endpoint secret is missing&#x27;);

// Application webhook handler: verify the raw body with the deployed secret.
const valid = verifyWebhookSignature(rawBody, signature, process.env.YOLFI_WEBHOOK_SECRET);
if (!valid) throw new Error(&#x27;Invalid Yolfi webhook signature&#x27;);

Reuse a matching endpoint and its installed secret. If its secret is unavailable, explain the required recovery instead of silently rotating a live secret or creating a duplicate. Rotation and removal require explicit confirmation. Analytics endpoints use NONE without metadata filters; generic filters are optional flat string maps for explicit current-payment categories, never authorization or tenant routing.

JavaScript SDK and application runtime

Fixed-paylink checkout uses a public checkout URL. Public payment creation and status checks also need no organization API key. Keep the paylink ID in app configuration and verify access grants using signed webhook events or authoritative payment status.

Dynamic, server-priced orders use authenticated Checkout Session creation. The backend calculates the amount and uses its own server credential; the MCP host's OAuth session is not an application credential. A deployed service needs an intentionally provisioned secret. Never copy host OAuth tokens into the app or assume a local CLI login exists in production.```js
import { YolfiClient } from '@yolfi/agent';

if (!process.env.YOLFI_API_KEY) throw new Error('Server credential is not provisioned');
const yolfi = new YolfiClient({ apiKey: process.env.YOLFI_API_KEY });
const session = await yolfi.createCheckoutSession({
amount: '19',
currency: 'USD',
merchantOrderId: 'order-123',
clientReferenceId: 'user-123',
}, { idempotencyKey: 'checkout-order-123' });


Use `paylinkId` instead of `amount` and `currency` for a paylink-backed session. Standalone sessions require a stable idempotency key and support one-time payments. Public payment creation accepts `paylinkId` or `checkoutSessionId`, plus `network` and `symbol`; customer email must be supplied directly or already present in the session. Payment metadata and paylink `paymentMetadata` accept flat string, finite-number, or boolean values. `clientReferenceId` should be a stable app user/customer ID for subscription attribution.

Choose the payment network and token from the organization&#x27;s or paylink&#x27;s supported-token catalog. Litecoin uses `network: &quot;LTC&quot;` and `symbol: &quot;LTC&quot;`; availability depends on the deployment and organization settings.

The SDK `getApiKey()` reads the full organization API key when authorized. It is not a status check and must not be printed as diagnostic output. Use `authStatus()` for account verification.

## CLI commands```bash
npx -y @yolfi/agent organization:update --json ./organization.json
npx -y @yolfi/agent settlement:configure --json ./settlement.json
npx -y @yolfi/agent webhooks:add --name Application --url https://example.com/api/yolfi/webhook --adapter NONE
npx -y @yolfi/agent webhooks:update --id &lt;endpointId&gt; --json ./endpoint.json
npx -y @yolfi/agent webhooks:rotate-secret --id &lt;endpointId&gt; --confirm
npx -y @yolfi/agent webhooks:remove --id &lt;endpointId&gt; --confirm
npx -y @yolfi/agent paylinks:get --id &lt;paylinkId&gt;
npx -y @yolfi/agent paylinks:disable --id &lt;paylinkId&gt; --confirm
npx -y @yolfi/agent checkout-sessions:create --json ./checkout-session.json --idempotency-key &lt;stable-order-key&gt;
npx -y @yolfi/agent checkout-sessions:get --id &lt;checkoutSessionId&gt;
npx -y @yolfi/agent payments:create --json ./payment.json
npx -y @yolfi/agent payments:status --id &lt;paymentId&gt;

Operational commands print JSON. help prints usage text; mcp speaks the MCP protocol. Payload files must exist in your working directory. organization:update is a generic API update; use settlement:configure to preserve unmentioned networks.

Verification

Report account authorization, local tests, deployment configuration, and live payment/webhook verification separately. A redirect, a successful connection, or a local signature test is not proof that the full payment path works. Preserve the app's existing billing and entitlement logic, and do not create paid test activity merely to claim verification.

Package checks: npm run check. No package publication or directory approval is implied by a local version or passing tests.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Yolfi Agent Kit 怎么安装?

在客户端按下面的安装命令接入:npx -y @yolfi/agent help npx -y @yolfi/agent auth:status。装完在客户端配置里引用同一个包或端点。

Yolfi Agent Kit 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Yolfi Agent Kit 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Yolfi Agent Kit 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Yolfi Agent Kit 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Yolfi Agent Kit 能提供哪些能力?

资料显示能力标签包括 金融。具体工具清单以官方文档为准。

Yolfi Agent Kit 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Yolfi Agent Kit 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。