Skip to content
Vibe-Code Rescue logo

Vibe-Code Rescue MCP server

Which MCP servers are Vibe-Code Rescue's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Vibe-Code Rescue

Whose server it is
  • Registry namecom.vibecodefixes/fixesverified in the MCP registry

The registry name sits under vibecodefixes.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools1
  • Server calls itselfvibecodefixes-mcp
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 129 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 of the 7 days it takes to judge reliability.

Once connected

  • For "look up the fix for a deploy error", the likely first call is diagnose_app_problem.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-30
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer325 ms
  • Space in an agent's context≈ 291 tokensthe definitions of all its tools (1), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 1 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · look up the fix for a deploy error
  • not sure · repair Supabase login redirects after deployment
  • not sure · fix Stripe webhook signature failures

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers1 tools · read 2026-10-29
  • diagnose_app_problem

    Match an error message or symptom from an app built with an AI app builder or deployed to a common host (Lovable, Bolt, v0, Cursor, Replit, Base44, Supabase, Firebase, Stripe, Vercel, Netlify, Next.js, Clerk, Prisma…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "fixes": {
      "type": "http",
      "url": "https://vibecodefixes.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vibecodefixes https://vibecodefixes.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://vibecodefixes.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.