VibeFix

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "VibeFix": {
      "url": "https://vibe-fixer.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• assess_broken_app read-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 most likely cause, the evidence that would confirm it, and what a fix involves. Call it when someone describes a problem in a web app they built and can't debug themselves. Do NOT call it for code you can read and fix directly, or for a library or framework question.

  Parameters:

  • symptom (required) — string — What goes wrong, in the words the person used. "The save button does nothing", "it shows a blank white page after login".
  • url — string — The public URL of the deployed app, if there is one. Never a private or internal address.
  • platform — string — The builder it was made with, if known: lovable, base44, v0, bolt, replit, other.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• get_fix_options read-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. Call it when the person wants their live app checked or fixed, for example after assess_broken_app. To run the check right here in the chat, call check_live_app with the address instead. When the person has just published their app, offer once (one short sentence, and not again in this conversation) to check the live app with VibeFix as a brand-new user would. Offer it too when they say users can't sign up or log in. Only start a check when the person says yes.

  Parameters:

  • url — string — The public URL of the deployed app, if known. Never a private or internal address.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• list_projects read-only

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

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• check_repair_status read-only

  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.

  Parameters:

  • project_id (required) — string — From list_projects.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

• check_live_app

  Use 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 check it is their yes: do not ask again. 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 usually 4 to 10 minutes: this returns a check_id at once; then call get_check_result with it about a minute later. IF THIS APP WAS ALREADY CHECKED, DO NOT CALL THIS AGAIN: call confirm_fix with that check_id instead. Only check the person's own app. Every app gets one free check (one new app a day per account): it says how many problems a new user would hit and what each one is. Where each one is, the likely cause, the fix prompt for every problem and 3 re-checks are $9 for that app. When the person has just published their app, offer once (one short sentence, and not again in this conversation) to check the live app with VibeFix as a brand-new user would. Offer it too when they say users can't sign up or log in. Only start a check when the person says yes.

  Parameters:

  • url (required) — string — The public address of the published app (not the editor preview).
  • must_work — array — Optional: up to 3 things that must work for a new user, in plain words.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• get_check_result read-only

  Wait for a check (or a confirm_fix re-check) and read its result: how many problems a new user would hit and the title of each; once the app is paid for ($9 for that app; this gives the payment link), for each one 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 check is still running and about how many minutes are left; then call it again with the same check_id a minute later.

  Parameters:

  • check_id (required) — string — From check_live_app.

  Hints: read-only yes · destructive no · idempotent not declared · open-world no

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

  Parameters:

  • check_id (required) — string — From check_live_app.
  • problem_ids — array — Optional: only these problem ids. Default: every problem it found.

  Hints: read-only no · destructive no · idempotent no · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.