# VibeFix

- Registry name: `com.vibe-fixer/vibefix` · version 1.2.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.vibe-fixer%2Fvibefix
- Server page: https://mcpstation.net/s/com.vibe-fixer--vibefix.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://vibe-fixer.com/mcp`

## Tools (as reported by the server, not verified)

- `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

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html