Vybe Pay MCP server
finance.vybe/payvybe.financestreamable-httpv1.0.0Scanned
Let Claude or Cursor pay for MCP tools under hard caps, with Approve or Decline on every pay.
15 tools: 3 do something that can't be undone, 4 change things and 8 only read.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 4
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Vybe Pay MCP server can do
The Vybe Pay MCP server is published by vybe.finance, a domain the MCP Registry verified. It has 15 tools. It can do things that cannot be undone, such as sending, paying or publishing (pay_invoice, send_to_user and pay_offering) and create or change data (4 tools: create_invoice, run_free_tool, use_paid_offering and fetch_paid_content), but cannot delete data. 8 tools only read.
1 tool reads private data (fetch_paid_content); 5 tools bring in text other people can write (get_invoice, get_tool, run_free_tool and 2 more); 4 tools can send data out of your system (get_invoice, pay_invoice, send_to_user and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Can't be undone 3Claude Code: ask
pay_invoicePay a Vybe invoice by /r/ URL or publicId under the owner’s spend key.Can send data outNo findings
Why it is in this group
- The name "pay_invoice" says "pay": a word that usually means money moves, which cannot be taken back.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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/r/… links are allowed (not arbitrary URLs). Friendship is not required. Related: create_invoice, get_invoice, get_limits, get_spend_balance, list_recent_pays.
Annotations the server declares
- title: Pay invoice
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
pay_offeringStart a Vybe Collect payment under the owner's connected spend key (OAuth Sign in or Bearer VAPT).Reads text others writeNo findings
Why it is in this group
- The name "pay_offering" says "pay": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 does not move until the wallet owner taps Approve in Vybe (web or mobile). After paid (or trial), call use_paid_offering with the returned publicId — that unlocks research files, lists/runs seller MCP tools, or proxies paid API calls. Do not scrape the marketplace page. Pass username plus offeringId, or a Collect / marketplace offeringUrl. Related: use_paid_offering, fetch_paid_content, get_limits, get_spend_balance, list_recent_pays.
Annotations the server declares
- title: Pay Collect offering
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
send_to_userSend USDC/USDT to a mutual friend.Can send data outNo findings
Why it is in this group
- The name "send_to_user" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "send_to_user" says "send": it sends or publishes something to other people.
Description, as the server wrote it 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 wallet addresses. If several friends match the name, the tool returns candidates; ask the owner which @username, then retry. Creates a pending pay — money does not move until Approve in Vybe. Trusted mutual friends still Approve once but notify quietly. Related: get_limits, get_spend_balance, get_wallet_balance, list_recent_pays.
Annotations the server declares
- title: Send to mutual friend
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
create_invoiceCreate a get-paid invoice for the spend-key owner.No findings
Why it is in this group
- The name "create_invoice" says "create": a word for a change.
Description, as the server wrote it 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 Vybe crypto checkout. Does not move money and does not require Approve. After sharing, call get_invoice with the publicId to check if it was paid before taking a follow-up action. Related: get_invoice, list_invoices, pay_invoice.
Annotations the server declares
- title: Create invoice
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
fetch_paid_contentUnlock research/file offerings only.Reads private data1 finding
Why it is in this group
- The name "fetch_paid_content" says "fetch": a word for reading.
- The description's first verb is "unlock": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Findings
- Warn
The server marks "fetch_paid_content" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fetch_paid_content" says "fetch": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Fetch paid Collect content
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
run_free_toolRun a free tool from the Vybe Marketplace and get its answer.Reads text others writeNo findings
Why it is in this group
- The name "run_free_tool" says "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 or get_tool first. Free tools have fair-use limits per caller; if you hit one, tell the user when it resets. Paid tools can't run here: use pay_offering and use_paid_offering. Related: search_tools, get_tool.
Annotations the server declares
- title: Run free marketplace tool
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
use_paid_offeringAfter a Collect pay is settled (status paid or trial), use this tool with the publicId from pay_offering.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 the file; MCP lists seller tools (omit toolName) or runs one (pass toolName + toolArguments); API proxies method+path(+body) through Vybe. Prefer this over inventing HTTP calls or scraping marketplace HTML. Related: pay_offering, list_recent_pays, fetch_paid_content.
Annotations the server declares
- title: Use paid Collect offering
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 8Show 8 read-only tools
get_invoiceCheck whether an invoice you created is still pending or already paid.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_invoice" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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 action that should only run after payment. Only works for invoices owned by this spend key’s owner. Related: create_invoice, list_invoices.
Annotations the server declares
- title: Get invoice status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_limitsReturn the bound spend key’s hard limits: label, per-transaction max in USD, daily cap, optional seller allowlist, expiry, and authMode (oauth or vapt).No findings
Why it is in this group
- The name "get_limits" says "get": a word for reading.
Description, as the server wrote it 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 this to tell the user what the agent is allowed to request before calling pay_offering. Related: get_spend_balance, get_wallet_balance.
Annotations the server declares
- title: Get spend limits
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_spend_balanceReturn the bound spend key’s policy headroom for the last 24 hours: daily remaining, pending, and paid.No findings
Why it is in this group
- The name "get_spend_balance" says "get": a word for reading.
Description, as the server wrote it 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_wallet_balance for that. Call this before pay_offering to check whether a pay would hit the daily cap. Related: get_wallet_balance, get_limits.
Annotations the server declares
- title: Get spend headroom
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_toolFull details for one marketplace tool: actions with their inputs, an example, price, seller and health, plus the exact next step.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_tool" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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 is pay_offering with its offeringUrl, then use_paid_offering with toolName and toolArguments. For a free tool it is run_free_tool, which needs no sign-in. Pass slug or the tool page URL. Related: search_tools, run_free_tool, pay_offering, use_paid_offering.
Annotations the server declares
- title: Get marketplace tool
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_wallet_balanceRead-only on-chain USDC/USDT balances for the spend key owner’s Vybe wallet (Base, Ethereum, BNB).No findings
Why it is in this group
- The name "get_wallet_balance" says "get": a word for reading.
Description, as the server wrote it 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 from get_spend_balance (VAPT caps). Does not move funds. Related: get_spend_balance, get_limits, pay_offering.
Annotations the server declares
- title: Get wallet balance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_invoicesList invoices the spend-key owner created (open, paid, etc.).No findings
Why it is in this group
- The name "list_invoices" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List my invoices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_recent_paysList recent Collect pays, friend sends, and invoice pays started by the bound spend key, newest first.No findings
Why it is in this group
- The name "list_recent_pays" says "list": a word for reading.
Description, as the server wrote it 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 (settled), or all. For paid Collect rows, call use_paid_offering with publicId. Related: pay_offering, pay_invoice, send_to_user, use_paid_offering.
Annotations the server declares
- title: List recent pays
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_toolsSearch 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).No findings
Why it is in this group
- The name "search_tools" says "search": a word for reading.
Description, as the server wrote it 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 this when the user asks for a capability you do not have, e.g. reading a PDF, looking up a postcode or checking a crypto transaction. Returns name, one-line summary, price, actions and offeringUrl. Never invent tools; if nothing fits, say so. Related: get_tool, pay_offering.
Annotations the server declares
- title: Search marketplace tools
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
20 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out4
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__pay__fetch_paid_content"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:21 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.vybe.finance/.well-known/oauth-protected-resource
- Authorization servers
- https://www.vybe.finance
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (3 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.vybe.finance/api/mcp/pay: tools/list returned 15 tools to an anonymous client, including pay_invoice (irreversible), send_to_user (irreversible), pay_offering (irreversible), create_invoice (write), run_free_tool (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "fetch_paid_content" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "fetch_paid_content" says "fetch": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pay https://www.vybe.finance/api/mcp/payclaude mcp add --transport http pay https://www.vybe.finance/api/mcp/payRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pay__list_invoices",
"mcp__pay__search_tools",
"mcp__pay__get_spend_balance",
"mcp__pay__get_wallet_balance",
"mcp__pay__get_limits",
"mcp__pay__list_recent_pays"
],
"ask": [
"mcp__pay__create_invoice",
"mcp__pay__get_invoice",
"mcp__pay__pay_invoice",
"mcp__pay__send_to_user",
"mcp__pay__get_tool",
"mcp__pay__run_free_tool",
"mcp__pay__pay_offering",
"mcp__pay__use_paid_offering",
"mcp__pay__fetch_paid_content"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pay. Review it before you use it.
Capability tags behind 8 rules
- mcp__pay__get_invoice untrusted-input, outbound
- mcp__pay__pay_invoice outbound
- mcp__pay__send_to_user outbound
- mcp__pay__get_tool untrusted-input, outbound
- mcp__pay__run_free_tool untrusted-input
- mcp__pay__pay_offering untrusted-input
- mcp__pay__use_paid_offering untrusted-input
- mcp__pay__fetch_paid_content private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/finance.vybe/pay/verify?hash=86055f49ddb679786619c384a5f9527a76e126d5c127620bd4f93598d4a1359c" | jq -e '.changed == false'Pinned hash 86055f49ddb6, from Nov 12, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/finance.vybe/pay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/finance.vybe/pay)Source: MCP Registry. Synced Nov 12, 2026, 16:17 UTC.
Vybe Pay MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Vybe Pay MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Vybe Pay MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Vybe Pay MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: pay_invoice, send_to_user and pay_offering.
What tools does the Vybe Pay MCP server have?
- 15 tools: 3 irreversible, 4 write, 8 read. pay_invoice, send_to_user, pay_offering, create_invoice, run_free_tool, use_paid_offering, fetch_paid_content, get_invoice and 7 more.
Does the Vybe Pay MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Vybe Pay MCP server send data to outside services?
- 4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_invoice, pay_invoice, send_to_user and get_tool.
Has the Vybe Pay MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.