VI

VibeFix

com.vibe-fixer/vibefix

Signs up to your live app like a new person and shows what breaks. Every app gets one free check.

Yes, your AI can use this right now.Answered a live MCP handshake in 432 ms with no sign-in needed and exposes 7 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://vibe-fixer.com/mcp

7 tools, verified live

Pulled straight from the server with tools/list on 2026-10-18.
assess_broken_appread-only

Triage a problem in a live app built with an AI app builder (Lovable, Base44, Bolt, Replit, v0 or similar). The most common one: 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 blank pages, buttons that do nothing, payments and data that won't save. Returns the mos

get_fix_optionsread-only

Returns 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_projectsread-only

List the apps connected to the signed-in person's VibeFix account, with the status of each. Call this when they ask what VibeFix is working on, which of their apps are connected, or before checking on a specific repair.

check_repair_statusread-only

Report the current state of one project on the signed-in VibeFix account: whether a repair is running, waiting for their approval, or finished. Use the project id from list_projects.

check_live_app

Start a VibeFix check of the LIVE, published app: a real browser opens it as a brand-new person, signs up with a real inbox, follows the confirmation email, and uses the app on a phone and a computer. It finds what a coding assistant cannot see from the code or the preview: emails that never arrive, confirmation links that open the wrong site, buttons covered on a phone, dead first steps. Call it

get_check_resultread-only

Wait for a check (or a confirm_fix re-check) and read its result: how many problems, how severe, and for each one what a new user saw, where, the likely cause and how to know it is fixed. Waits up to about 4 minutes; if it says the check is still running, call it again with the same check_id.

confirm_fix

Call 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

Alternatives in Other

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”