**Vybe Pay** ``` Agents(Claude, Cursor etc) pays, Vybe Collect under your caps. You Approve every payment in Vybe. ``` ### Tagline Empower Your AI Agents to pay, while You approve every payment. ### Short description Give Cursor or Claude a Vybe spend key with hard limits. When the agent wants to buy a Collect offering, you get Approve or Decline in Vybe — same balance you already use. ### Long description (directories, mcp.so) Vybe Pay lets an AI agent request a payment without holding your whole wallet. 1. You issue a **VAPT** in Vybe (Settings → Agent spend) with a per-payment max, daily cap, optional seller allowlist, and expiry. 2. You paste `vapt_…` into Cursor, Claude, or any MCP client as the Vybe Pay server. 3. The agent calls `pay_offering`. Vybe creates a pending Collect pay and returns `awaiting_approval`. 4. You Approve on web or mobile. USDC moves on Base. Decline cancels it. Nothing leaves until you say yes. **Tools:** `pay_offering`, `get_limits`, `get_spend_balance`, `list_recent_pays`. **Not included:** silent spend, paying merchants outside Vybe Collect, or reading your on-chain balance. Homepage: https://www.vybe.finance/pay-mcp Setup: https://www.vybe.finance/developer#vybe-pay-mcp ### Categories / tags `payments` · `finance` · `crypto` · `usdc` · `agents` · `authorization` · `remote` · `http` Pick **Finance** or **Payments** as the primary category when the form allows one. ### Keywords (search) Vybe, VAPT, Collect, USDC, Base, agent payments, MCP, Cursor, Claude, approve, spend key --- ## Client install snippets (for store “How to connect” fields) ### Cursor (`~/.cursor/mcp.json` or project `.cursor/mcp.json`) ```json { "mcpServers": { "vybe-pay": { "url": "https://www.vybe.finance/api/mcp/pay", "headers": { "Authorization": "Bearer vapt_YOUR_TOKEN" } } } } ``` ### Claude Code ```json { "mcpServers": { "vybe-pay": { "type": "http", "url": "https://www.vybe.finance/api/mcp/pay", "headers": { "Authorization": "Bearer vapt_YOUR_TOKEN" } } } } ```

MCP readiness

B · 80/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 71.6/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1897 ms).
Protocol revision	5/10	Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 15 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1897 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 45% of peers; This listing 80 · peer median 81
Latency: Faster than 18% of peers; This listing 680 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Protocol revision −5 — Support the current protocol revision.
Now: Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-17 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/vybe/vybe_pay/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/vybe/vybe_pay/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.vybe.finance/pay-mcp

Listed at (smithery)

https://www.vybe.finance/pay-mcp