All MCP Servers
Design & MediaMCP Registryremote7 toolsB · 73

VibeFix MCP server

com.vibe-fixer · Updated

Our AI agent signs up to your live app like a new user and shows, with a screenshot, what breaks.

At a glance

VibeFix is an MCP server in the Design & Media category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 7 tools, including assess_broken_app, get_fix_options and list_projects. It scores B (73/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install VibeFix in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install VibeFix in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add --transport http vibefix https://vibe-fixer.com/mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. assess_broken_app, get_fix_options, list_projects). It discovers them automatically.

What tools does VibeFix expose? (7)

Read from the live server. Click any tool for its input schema.

  • assess_broken_appAn AI agent confirms a problem in a live web app for free, then fixes it in the code: $79 for one bug, paid up front. Works with apps built with Lovable, Base44, Bolt, Replit, v0 or similar. The most common problem: new people can't sign up. The confirmation email never arrives, its link opens localhost or the preview, sign-up loops back or shows an error, or Google sign-in fails. It also covers b
  • get_fix_optionsReturns the link to a sign-up check of a live app on vibe-fixer.com. An AI agent signs up as a brand-new person with a real inbox, on a phone and a computer, and reports whether a new person can finish signing up, plus anything else a first customer would hit. It also says how the fix works and what the person provides. Read-only: it starts nothing, charges nothing and does not contact the app. Ca
  • list_projectsList the signed-in person's VibeFix checks (one per app checked), with the status of each. Call this when they ask which of their apps VibeFix has checked. To read a check's result, call get_check_result with its check_id (the id listed here).
  • check_repair_statusReport whether one check on the signed-in VibeFix account is still running or finished. For what the check found, call get_check_result instead. Use the id from list_projects.
  • check_live_appUse this when the person asks you to check, test or try their app ("check my app", "is my app working?", "can new users sign up?", "test my site"), or gives you the address of their live app. If you do not have the address, ask for it (the published web address, e.g. https://their-app.lovable.app); if it is not clear that it is their own app, ask them that one yes/no question first. Asking you to
  • get_check_resultWait for a check (or a confirm_fix re-check) and read its result: how many problems a new user would hit, the title of each and how serious it is (blocking, serious or minor), and how to have it fixed ($79, paid up front); for an app already paid for, what a new user saw, where, the likely cause, the fix prompt and how to know it is fixed. Answers within about 20 seconds: the result, or that the c
  • confirm_fixCall this only once the fix is done AND published (or the setting saved): it re-runs exactly the problems get_check_result reported, on the live app. This is the way to re-check an app that was already checked: never start a new check_live_app for it. A fix made in a setting (for example the backend's auth settings), with nothing new to publish, counts too: if this answers that nothing new is publ

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Third-party hosted service — Your requests and any data in them are sent to vibe-fixer.com.
  • No local execution — Nothing is installed or run on your machine.
  • Last commit today — Actively maintained.
  • Repository created 1 month ago — Very new project with little track record yet.
  • 0 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 73

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%100%

    Last commit 0 days ago.

  • Adoption20%0%

    0 stars.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%75%

    Remote endpoint; authentication requirements not declared.

Documentation

Full README

VibeFix: an AI agent that finds what is breaking your live app and fixes it in your code

VibeFix is an AI agent. A free check signs up to your live, published app like a brand-new person, with a real inbox, on a phone and a computer, and confirms what is broken. A paid fix is available on vibe-fixer.com.

Every app gets one free check. This repository is the MCP connection for it: add the server to your AI tool, then ask it to check your live app.

  • Endpoint: https://vibe-fixer.com/mcp
  • Transport: Streamable HTTP
  • Authentication: two tools need no sign-in; five use OAuth sign-in to your VibeFix account (the client is prompted when you call one)
  • Website: vibe-fixer.com
  • Server card: `/.well-known/mcp.json`
  • Registry name: com.vibe-fixer/vibefix

What it does

  1. Check. check_live_app starts a check of your published app. It signs up as a brand-new person with a real inbox, follows the confirmation email, and uses the app on a phone and a computer. Every app gets one free check (one new app a day per account).
  2. Read. get_check_result returns what it found, with evidence.
  3. Re-check. confirm_fix re-checks those problems on your live app and marks each one fixed or not.

The free check never changes your app. A full check runs only when you confirm the app is yours; otherwise the check is look-only and does not sign up. Today the fix is for apps built with Lovable, or any app whose code is on GitHub.

Free check, paid fix

The check is free: every app gets one free check. A paid fix is available on vibe-fixer.com.

Details: vibe-fixer.com

Tools

| Tool | Sign-in | What it does | |---|---|---| | assess_broken_app | none | Describe a symptom in plain words; get the likely cause, the evidence that would confirm it, and what a fix involves. Reads the description only: no code, no access to your app. | | get_fix_options | none | Returns the link to a sign-up check of your live app and how it works. Read-only: starts nothing, charges nothing. | | list_projects | OAuth | Lists the checks on your VibeFix account. Read-only. | | check_repair_status | OAuth | Says whether one check is still running. Read-only. | | check_live_app | OAuth | Starts a check of your live app. Every app gets one free check. | | get_check_result | OAuth | Reads what a check (or a re-check) found. Read-only. | | confirm_fix | OAuth | Re-checks the reported problems on your live app after a fix. |

Connect

Claude Code

Maintain VibeFix? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![VibeFix on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-vibe-fixer-vibefix)](https://mcp-skills-hub.vercel.app/mcps/com-vibe-fixer-vibefix)

Catalog data refreshed . Something wrong? Report it.