# yolfinance/yolfi-agent [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/yolfinance/yolfi-agent  
**GitHub Stars:** 177  
**npm Downloads (last month):** 254  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/yolfinance-yolfi-agent

## Description
Yolfi Payments MCP lets AI coding agents register Yolfi workspaces, create crypto checkout payment links, configure webhooks, verify webhook signatures, and check payment status. Install with npx -y @yolfi/agent mcp.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "yolfi-agent": {
    "command": "npx",
    "args": ["-y","@yolfi/agent"],
    "env": {
      "YOLFI_API_KEY": "",
      "YOLFI_CONFIG_HOME": "",
      "YOLFI_REGISTRATION_IDEMPOTENCY_KEY": ""
    }
  }
}
```

**Requires environment variables:** `YOLFI_API_KEY`, `YOLFI_CONFIG_HOME`, `YOLFI_REGISTRATION_IDEMPOTENCY_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What yolfinance/yolfi-agent MCP server does

yolfinance/yolfi-agent provides an MCP interface to Yolfi payment operations for AI coding agents. It is intended for applications that need crypto checkout, one-time or recurring-style payment links, donation pages, paid downloads, credits, game items, or access controlled by confirmed payment events.

The package combines an MCP server with a CLI, JavaScript SDK, and agent instructions. The payment infrastructure remains in Yolfi, while the agent is responsible for inspecting the target project, asking the user for decisions such as wallet addresses and prices, making code changes, and wiring the application to Yolfi.

## How it works

The server runs locally over MCP stdio. An MCP host starts the package with `npx -y @yolfi/agent mcp`, after which the agent can work with Yolfi operations from the host’s tool interface. The supported workflow includes registering or reusing a workspace, checking authentication, configuring settlement wallets, creating or reusing paylinks, and adding checkout integration.

Webhook workflows can configure endpoints, retain delivery settings, and verify the `X-Yolfi-Signature` header. Applications can then use confirmed webhook events for entitlement logic. Payment status can also be checked through Yolfi’s public payment endpoints.

The included Yolfi Payments Skill defines confirmation boundaries for agents. Agents must not invent wallet addresses, prices, plans, currencies, credential locations, or destructive paylink operations.

## Setup and configuration

Install the package into a project with `npm install @yolfi/agent`, or run it without installation using `npx -y @yolfi/agent mcp`. Node.js 18 or later is supported. The repository also provides a local CLI entry point for development.

The preferred setup opens browser authorization and stores a credential in `~/.yolfi/config.json`. Run `setup` with an agent name, complete the returned login flow, then use `checkin` and `auth:status`. `YOLFI_CONFIG_HOME` can move this configuration into an isolated directory for development or CI. An explicit `YOLFI_API_KEY` takes precedence over stored credentials.

New users can use the email-confirmed registration flow. The registration command requires user confirmation of the email and project name, and may use `YOLFI_REGISTRATION_IDEMPOTENCY_KEY` to safely repeat a pending registration.

## Tools and capabilities

The yolfinance/yolfi-agent MCP server covers these operations:

- Registering an agent or Yolfi workspace.
- Checking authentication and workspace status.
- Configuring settlement wallets.
- Listing and creating payment links.
- Creating public payment invoices from paylinks.
- Checking payment status.
- Adding, listing, updating, and removing webhook endpoints.
- Verifying webhook signatures and supporting webhook-based access logic.

Webhook metadata filters are flat key-value maps with documented size limits. Removing an endpoint requires confirmation, and endpoints with delivery history are disabled rather than detached from their audit relationship.

## Limitations and notes

This package does not replace Yolfi’s payment infrastructure or decide application-specific prices, wallets, plans, or secret-storage locations. Those choices must come from the user. Full API keys should not be logged, committed, or written into the target project’s documentation.

The registration flow is for signup only. Existing Yolfi users should use browser authorization or local setup instead. Recurring or subscription-style links depend on account support. The provided MCP command is a local stdio server; the material does not document a hosted MCP endpoint.

_Full upstream README: https://allmcps.com/mcp/yolfinance-yolfi-agent/readme_