VibeFix MCP server

• Registry namecom.vibe-fixer/vibefixverified in the MCP registry

The registry name sits under vibe-fixer.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-25
• Tools7
• Server calls itselfvibefix
• Server version1.2.0
• Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 33 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer119 ms
• Space in an agent's context≈ 1,748 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results4 of 7 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…