Connect-MCP

VibeFix

com.vibe-fixer/vibefix · v1.1.3

Tests your live app like a first customer, free. One exact fix to paste in your builder, re-tested.

MCPremoteno credentialsEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 7 tools · 5 read, 2 write · Email, Developer tools, Finance

Test call list_projects: needs a key: rpc error: Sign in to VibeFix to see your projects and repairs. (988 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://vibe-fixer.com/mcp

Tools

7 tools listed at last check
  • 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 apps connected to the signed-in person's VibeFix account, with the status of each. Call this when they ask what VibeFix is working on, which of their apps are connected, or before checking on a specific repair.
  • check_repair_status Report the current state of one project on the signed-in VibeFix account: whether a repair is running, waiting for their approval, or finished. Use the project id from list_projects.
  • 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,
  • 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.
  • 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

Badge

Connect-MCP badge for com.vibe-fixer/vibefix

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/com.vibe-fixer/vibefix.svg)](https://clawy.uk/mcp/s/com.vibe-fixer/vibefix)

Repository · Website