GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Beschreibung vom Entwickler (englisches Original)
Free check by an AI agent on your live app. On request: independent code review, fix, live re-check.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://vibe-fixer.com/mcpFühre das in deinem Terminal aus
claude mcp add --transport http vibefix https://vibe-fixer.com/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"vibefix": {
"url": "https://vibe-fixer.com/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"vibefix": {
"type": "http",
"url": "https://vibe-fixer.com/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://vibe-fixer.com/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.
assess_broken_appAn AI agent confirms a problem in a live web app for free, then fixes it in the code: $79 for one bug, paid up front. If we can't complete your re-check, you get your money back. Works with apps built with Lovable, Base44, Bolt, Replit, v0 or similar. The most common problem: new
get_fix_optionsReturns 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 th
list_projectsList 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_statusReport 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_appUse 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://thei
get_check_resultWait for a check (or a confirm_fix re-check) and read its result: how many problems a new user would hit, the title of each and how serious it is (blocking, serious or minor), and how to have it fixed ($79, paid up front); for an app already paid for, what a new user saw, where,
confirm_fixCall 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
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026
Der Herausgeber (vibe-fixer.com) ist nicht der Repo-Inhaber (yos88da); vielleicht hat jemand anderes ihn eingetragen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 217 ms (HTTP 200)
Keine Anmeldung nötig
Wir haben 7 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 2 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.6.0) kam vor 4 Tagen in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: GitHub, Desktop Commander, Cloudflare MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
App broke after you published it? Our AI agent fixes it in your code, then tests your live app again so you see the result yourself. The first check is free.
You built the app with an AI tool, published it, and then something stopped working. Maybe new users can't finish signing up. Maybe the confirmation email never arrives, or checkout throws an error. Maybe you asked your builder's AI to fix it, it said it had, and the problem is still there for your users.
VibeFix starts where your users start. Paste the link to your live app and our AI agent signs up as a brand-new user. It walks through your pages the way a stranger would and sends you a screenshot of the problem it hits. The free check never changes your app.
If you want the problem fixed, the agent goes into your code. It looks for the cause, makes the change in your code, and then opens your live app again to test that the problem is gone. You see the re-check, so you're not taking anyone's word that it's fixed.
What it can work on: sign-up and login, emails that don't arrive or link to the wrong place, payments, API, integration and Supabase errors, and front-end bugs, as long as the cause is in the code.
Today the fix is for apps built with Lovable, or any app whose code is on GitHub.
A paid fix is available on vibe-fixer.com.
Every app gets one free check. This repository is the MCP connection for it: add the server to your AI tool, then ask it to check your live app.
https://vibe-fixer.com/mcp/.well-known/mcp.jsoncom.vibe-fixer/vibefixcheck_live_app starts a check of your published app. It signs up as a brand-new person with a real inbox, follows the confirmation email, and uses the app on a phone and a computer. Every app gets one free check (one new app a day per account).get_check_result returns what it found, with evidence.confirm_fix re-checks those problems on your live app and marks each one fixed or not.The free check never changes your app. A full check runs only when you confirm the app is yours; otherwise the check is look-only and does not sign up. Today the fix is for apps built with Lovable, or any app whose code is on GitHub.
The check is free: every app gets one free check. A paid fix is available on vibe-fixer.com.
Details: vibe-fixer.com
| Tool | Sign-in | What it does |
|---|---|---|
assess_broken_app | none | Describe a symptom in plain words; get the likely cause, the evidence that would confirm it, and what a fix involves. Reads the description only: no code, no access to your app. |
get_fix_options | none | Returns the link to a sign-up check of your live app and how it works. Read-only: starts nothing, charges nothing. |
list_projects | OAuth | Lists the checks on your VibeFix account. Read-only. |
check_repair_status | OAuth | Says whether one check is still running. Read-only. |
check_live_app | OAuth | Starts a check of your live app. Every app gets one free check. |
get_check_result | OAuth | Reads what a check (or a re-check) found. Read-only. |
confirm_fix | OAuth | Re-checks the reported problems on your live app after a fix. |
claude mcp add --transport http vibefix https://vibe-fixer.com/mcp
Add to ~/.cursor/mcp.json:
{ "mcpServers": { "vibefix": { "url": "https://vibe-fixer.com/mcp" } } }
Or use the one-click link on vibe-fixer.com/tools.
Add to .vscode/mcp.json:
{ "servers": { "vibefix": { "type": "http", "url": "https://vibe-fixer.com/mcp" } } }
Go to Customize, Connectors, press +, then Add custom connector. Paste https://vibe-fixer.com/mcp and press Add.
See vibe-fixer.com/tools. Any tool that takes a remote MCP server works with the address above. VibeFix is independent. Product names belong to their owners and are used only to say VibeFix works with them; VibeFix is not affiliated with or endorsed by them.
claude plugin marketplace add yos88da/vibefix-mcp claude plugin install vibefix@vibefix
This repository is also an Agent Plugins package (plugin.json, mcp.json).
The skill tells a coding agent when to call VibeFix (tested in Claude Code; install lines for Cursor and Codex are not yet tested end to end): when you say your deployed app is broken (log-in, emails, payments, an API or Supabase error, a blank page), or right after you publish a change. It only checks your own app, and only when you say yes.
| Agent | One-line install |
|---|---|
| Claude Code (skill + server) | claude plugin marketplace add yos88da/vibefix-mcp && claude plugin install vibefix@vibefix |
| Any agent with skills | npx skills add yos88da/vibefix-mcp |
| Cursor (project rule; not yet tested end to end) | curl -fsSL https://raw.githubusercontent.com/yos88da/vibefix-mcp/main/agent-rules/cursor/vibefix.mdc --create-dirs -o .cursor/rules/vibefix.mdc |
| Codex (AGENTS.md; not yet tested end to end) | curl -fsSL https://raw.githubusercontent.com/yos88da/vibefix-mcp/main/agent-rules/AGENTS.md >> AGENTS.md |
The skill is skills/vibefix-live-check/SKILL.md. The Cursor rule and the AGENTS.md section say the same thing in short. Cursor and Codex also need the server connected (see Connect above).
codex mcp add vibefix --url https://vibe-fixer.com/mcp codex mcp login vibefix
VibeFix sign-up check on the GitHub Marketplace (source) runs the free check after each deploy and reports on the pull request whether a new user can get in. No API key: it proves which repo it runs in with GitHub's own token.
See its README for the workflow, the permissions and which addresses it checks.
assess_broken_app works from a description alone and says so in its answer.Privacy: vibe-fixer.com/privacy. Terms: vibe-fixer.com/terms. Support: help@vibe-fixer.com.
This repository contains documentation, plugin metadata and the agent skill only. The service itself is at vibe-fixer.com.