Is the Vybe Pay MCP down?

mcp-registry/finance.vybe/pay · registry v1.0.0 · server reports v0.5.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:46 UTC · handshake 783ms

As of 2026-11-22 16:46 UTC, the Vybe Pay MCP is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
99.9%
checks observed
895
outages (90d)
1
tools
15

Let Claude or Cursor pay for MCP tools under hard caps, with Approve or Decline on every pay.

Point your MCP client at this streamable-http endpoint: https://www.vybe.finance/api/mcp/pay

Agent-readiness: A (95/100)

A (95/100): 0 error(s), 2 warning(s) across 15 tool(s); ~4,080 tokens of tool definitions.
Scores higher than 72% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~4,080 tokens per session — more than 65% of servers.
95 → 95 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints100
Schemas87
Protocol40
Stability100
Token cost100
Reliability100
Client compatibility100

What to fix (2)

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: use_paid_offering

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Ffinance.vybe%2Fpay/fixes

use_paid_offering 1 change
{
  "name": "use_paid_offering",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "title": "UsePaidOfferingInput",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "publicId"
    ],
    "properties": {
      "body": {
        "description": "API only: JSON body for POST/PUT/PATCH.",
        "type": "string"
      },
      "path": {
        "type": "string",
        "description": "API only: path under the offering invoke base, e.g. /v1/scan."
      },
      "method": {
        "type": "string",
        "description": "API only: HTTP method, e.g. GET or POST. Defaults to GET."
      },
      "publicId": {
        "type": "string",
        "minLength": 4,
        "description": "Vybe payment request id from pay_offering or list_recent_pays."
      },
      "toolName": {
        "type": "string",
        "description": "MCP only: seller tool name from the prior tools/list response."
      },
      "toolArguments": {
        "type": "object",
        "description": "MCP only: JSON arguments for tools/call.",
        "additionalProperties": true
      }
    },
    "description": "publicId is required. For MCP, omit toolName to list tools, then pass toolName to run one. For API, pass method and path.",
    "additionalProperties": false
  },
  "annotations": {
    "title": "Use paid Collect offering",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  },
  "title": "Use paid Collect offering"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/finance.vybe/pay"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/finance.vybe/pay"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Ffinance.vybe%2Fpay.svg)](https://glimind.com/server/mcp-registry%2Ffinance.vybe%2Fpay?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Ffinance.vybe%2Fpay?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Ffinance.vybe%2Fpay.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:240183c816eec1ec…, first seen 2026-11-16, included at leaf 292503 of 384,647. Version history · verify what your client received.

Tools (15)

Compare: most reliable finance servers · most reliable payments servers · most reliable search servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Vybe Pay MCP down right now?

As of 2026-11-22 16:46 UTC, the Vybe Pay MCP is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

How many tools does Vybe Pay MCP provide?

Vybe Pay MCP advertises 15 tools, including create_invoice, fetch_paid_content, get_invoice, get_limits, get_spend_balance.

How do I install Vybe Pay MCP?

Point your MCP client at this streamable-http endpoint: https://www.vybe.finance/api/mcp/pay

Is the Vybe Pay MCP safe to connect to an AI agent?

Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vybe Pay MCP?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve