com.vibe-fixer/vibefix

Tools

• assess_broken_app

  Triage a problem in an app built with Lovable, Base44, v0, Bolt, Replit or a similar AI app builder — a button that does nothing, a blank page, a login that fails, data that will not save, a deploy that broke a working app. Returns the most likely cause for that symptom, the evidence that would confirm it, and what a fix would involve. Call this when someone describes an app they built with an AI tool and cannot debug themselves. Do NOT call it for code you can read and fix directly, for a library or framework question, or for an app the person built by hand.

  shallow
• 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 after any change to sign-up, log-in, onboarding or payments, ONCE THE CHANGE IS PUBLISHED (it checks the public address, not the preview). It takes a few minutes: this returns a check_id at once; then call get_check_result with it. IF THIS APP WAS ALREADY CHECKED, DO NOT CALL THIS AGAIN: call confirm_fix with that check_id instead. Every app gets one free check (one new app a day per account); re-checks after a fix are paid.

  shallow
• check_repair_status

  Report 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.

  shallow
• 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 published, call it once more and it re-checks. Then call get_check_result with the same check_id to see each problem marked fixed or not. Do not tell the person a problem is fixed until this says so. After each re-check, tell the person how many re-checks are left (this tool's answer says).

  shallow
• get_check_result

  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.

  shallow
• get_fix_options

  Returns how to get a broken web app tested and fixed with VibeFix: the link that starts a live test of the app by an AI agent (with the app's address filled in when given), how the fix works, and what the person needs to provide. Read-only: it starts nothing, charges nothing and does not contact the app. Call it when the person wants the problem fixed, not only explained — for example after assess_broken_app.

  shallow
• list_projects

  List 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).

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/2033279a-482b-47e9-91d6-43699ba56097/badge.svg)](https://vouch.tools/servers/2033279a-482b-47e9-91d6-43699ba56097)