# Vybe Pay MCP server

Source: https://glimind.com/server/mcp-registry%2Ffinance.vybe%2Fpay
Registry id: `mcp-registry/finance.vybe/pay`
Status: live (checked 2026-11-22T17:00:38.543Z)

## Measurements (30 days)

- Uptime: 99.89%
- Checks: 895
- Outages (90 days): 1

## Install

```json
{
  "mcpServers": {
    "vybe-pay-mcp-server": {
      "type": "http",
      "url": "https://www.vybe.finance/api/mcp/pay"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http vybe-pay-mcp-server https://www.vybe.finance/api/mcp/pay
```

## Tools (15)

- `create_invoice`: Create a get-paid invoice for the spend-key owner. Returns a /r/{publicId} URL. Another agent can call pay_invoice with that URL; a human opening the link sees 
- `fetch_paid_content`: Unlock research/file offerings only. For MCP or API offerings, call use_paid_offering with the same publicId instead. Related: use_paid_offering, pay_offering.
- `get_invoice`: Check whether an invoice you created is still pending or already paid. Pass the publicId or /r/ url from create_invoice. Use this before taking a follow-up acti
- `get_limits`: Return the bound spend key’s hard limits: label, per-transaction max in USD, daily cap, optional seller allowlist, expiry, and authMode (oauth or vapt). Use thi
- `get_spend_balance`: Return the bound spend key’s policy headroom for the last 24 hours: daily remaining, pending, and paid. This is not the on-chain USDC wallet balance — use get_w
- `get_tool`: Full details for one marketplace tool: actions with their inputs, an example, price, seller and health, plus the exact next step. For a paid tool the next step 
- `get_wallet_balance`: Read-only on-chain USDC/USDT balances for the spend key owner’s Vybe wallet (Base, Ethereum, BNB). Use this to tell the user how much they can spend. Separate f
- `list_invoices`: List invoices the spend-key owner created (open, paid, etc.). Use to find a publicId, then get_invoice for details. Related: create_invoice, get_invoice.
- `list_recent_pays`: List recent Collect pays, friend sends, and invoice pays started by the bound spend key, newest first. Filter by status: pending (waiting on Approve), paid (set
- `pay_invoice`: Pay a Vybe invoice by /r/ URL or publicId under the owner’s spend key. Creates awaiting_approval — money does not move until Approve in Vybe. Only vybe.finance/
- `pay_offering`: Start a Vybe Collect payment under the owner's connected spend key (OAuth Sign in or Bearer VAPT). Creates a pending pay and returns awaiting_approval — money d
- `run_free_tool`: Run a free tool from the Vybe Marketplace and get its answer. No sign-in or spend key needed, and nothing is charged. Get the slug, action names and inputs from
- `search_tools`: Search the Vybe Marketplace for MCP tools the user can use: free tools (run with run_free_tool, no sign-in) and paid tools (pay per use with pay_offering). Use 
- `send_to_user`: Send USDC/USDT to a mutual friend. Pass username (@handle) when known, or name (first, last, or full name). Lookup is limited to mutual friends — never invent w
- `use_paid_offering`: After a Collect pay is settled (status paid or trial), use this tool with the publicId from pay_offering. It branches by offering type: research/asset returns t

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
