Official MCP RegistryListed
VibeFix
Tests your live app like a first customer, free. One exact fix to paste in your builder, re-tested.
First seen 2 Oct 2026. Evidence as of 6 Oct 2026.
2
Tools
From an anonymous probe
1
Source listings
Each with its own history
7
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| 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 a web app they built (with an AI tool or by hand) and cannot debug themselves. Do NOT call it for code you can read and fix directly, or for a library or framework question. | Read-only |
| 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. | Read-only |
Change history
- get_fix_options: input schema changed
- get_fix_options: description changed (+"how" +"fix works," -"plans")
- get_fix_options: annotations changed
- assess_broken_app: annotations changed
- server instructions changed (+"triages problems in live, published web apps built with" +"builders." +"symptom")
- Description changed (registry)
- Description changed (registry)
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | com.vibe-fixer/vibefix | 2 Oct 2026 | 6 Oct 2026 | 3 |