Remote MCP · Endpoint

Vybe Pay MCP MCP server

No. Vybe Pay MCP answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
finance.vybe/pay
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
288 ms
Tools exposed
15 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Let Claude or Cursor pay for MCP tools under hard caps, with Approve or Decline on every pay.
Listing
From the official MCP registry (active).
Recent checks of Vybe Pay MCP
CheckedResultHandshake
7 hours agoHandshake completed288 ms
4 days agoHandshake completed285 ms
7 days agoHandshake completed284 ms

The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Vybe Pay MCP and makes no claim about it beyond what these checks measured.