All servers · Payments & accounting

VibeFix

com.vibe-fixer/vibefix · v1.2.0

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http vibefix https://vibe-fixer.com/mcp

{
  "mcpServers": {
    "vibefix": {
      "url": "https://vibe-fixer.com/mcp"
    }
  }
}

Tools as reported by the server

• assess_broken_app
  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
• get_fix_options
  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
• 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).
• 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.
• 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);
• get_check_result
  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 fix
• 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

Tool changes

• 2026-10-23: assess_broken_app, get_fix_options, list_projects, check_repair_status, check_live_app, get_check_result, confirm_fix
• 2026-10-21: assess_broken_app, get_fix_options, list_projects, check_repair_status, check_live_app, get_check_result, confirm_fix
• 2026-10-20: assess_broken_app, get_fix_options, list_projects, check_repair_status, check_live_app, get_check_result, confirm_fix
• 2026-10-18: assess_broken_app, get_fix_options, list_projects, check_repair_status, check_live_app, get_check_result, confirm_fix
• 2026-10-18: assess_broken_app, get_fix_options, list_projects, check_repair_status, check_live_app, get_check_result, confirm_fix
• 2026-10-16: assess_broken_app, get_fix_options, list_projects, check_repair_status

Repository · Website · JSON · Text for agents · Registry updated 2026-10-18