Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Vibefix is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Free live-app check by an AI agent. On request it fixes the code and tests the app again.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http vibe-fixer-vibefix-mcp https://vibe-fixer.com/mcp
# 2 — ask your agent for something these tools do
# assess_broken_app, get_fix_options, list_projects and 4 more
Vibefix costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VFAll 1 server
vibe-fixer1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http vibe-fixer-vibefix-mcp https://vibe-fixer.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 also covers blank pages, buttons that do nothing, payments and data that won't save. Returns the mos
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symptom | string | yes | What goes wrong, in the words the person used. "The save button does nothing", "it shows a blank white page after login". |
| platform | string | no | The builder it was made with, if known: lovable, base44, v0, bolt, replit, other. |
| url | string | no | The public URL of the deployed app, if there is one. Never a private or internal address. |
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 the person provides. Read-only: it starts nothing, charges nothing and does not contact the app. Ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | The public URL of the deployed app, if known. Never a private or internal address. |
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).
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | From list_projects. |
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, confirmation links that open the wrong site, buttons covered on a phone, dead first steps. Call it
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The public address of the published app (not the editor preview). |
| must_work | array | no | Optional: up to 3 things that must work for a new user, in plain words. |
Wait for a check (or a confirm_fix re-check) and read its result: how many problems a new user would hit; 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 fixed. Waits up to about 4 minutes; if it says the check is still running, call it again with the same check_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | From check_live_app. |
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's auth settings), with nothing new to publish, counts too: if this answers that nothing new is publ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| check_id | string | yes | From check_live_app. |
| problem_ids | array | no | Optional: only these problem ids. Default: every problem it found. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Vibefix or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.5.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest9a21e505fea564c9d56c9c769b7096bcfcb59cc10ed383d5a36b84570f54cb9c
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| assess_broken_app | no tags | |
| get_fix_options | no tags | |
| list_projects | no tags | |
| check_repair_status | no tags | |
| check_live_app | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_check_result | no tags | |
| confirm_fix | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9a21e505fea564c9
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.5.0.
1.5.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Vibefix can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.