Skip to content

VibeFix MCP server

com.vibe-fixer/vibefixvibe-fixer.comstreamable-httpv1.6.0Scanned

Free check by an AI agent on your live app. On request: independent code review, fix, live re-check.

7 tools: 3 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 3 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the VibeFix MCP server can do

The VibeFix MCP server is published by vibe-fixer.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (3 tools: assess_broken_app, check_live_app and confirm_fix), but cannot delete data. 4 tools only read.

3 tools bring in text other people can write (get_fix_options, check_live_app and confirm_fix); 3 tools can send data out of your system (assess_broken_app, get_fix_options and check_live_app).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.6.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 3Claude Code: ask
  • 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.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    An 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. The free check works with published apps, including apps built in Lovable, Base44, Bolt, Replit and v0. The $79 fix works with apps built in Lovable and any app whose code is on GitHub. The most common problem: 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 most likely cause, the evidence that would confirm it, and the next step: a free check on the live app. Call it when someone describes a problem in a web app they built and can't debug themselves. Do NOT call it for code you can read and fix directly, or for a library or framework question.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • 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 thei…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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 (the published web address, e.g. https://their-app.lovable.app); if it is not clear that it is their own app, ask them that one yes/no question first. Asking you to check it is their yes: do not ask again. 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 after any change to sign-up, log-in, onboarding or payments, ONCE THE CHANGE IS PUBLISHED (it checks the public address, not the preview). It takes usually 4 to 10 minutes: this returns a check_id at once; then call get_check_result with it about a minute later. IF THIS APP WAS ALREADY CHECKED, DO NOT CALL THIS AGAIN: call confirm_fix with that check_id instead. Only check the person's own app. Every app gets one free check (one new app a day per account): it says how many problems a new user would hit, what each one is and how serious it is. It never says the cause, where it is or how to fix it. To have it fixed: Our AI agent finds the cause, fixes it in the code and re-checks the live app: $79, paid up front. If we can't complete your re-check, you get your money back. The person asks for it from their result page. When the person has just published their app, offer once (one short sentence, and not again in this conversation) to check the live app with VibeFix as a brand-new user would. Offer it too when they say users can't sign up or log in. Only start a check when the person says yes.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "call": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 published, call it once more and it re-checks. Then call get_check_result with the same check_id to see each problem marked fixed or not. Do not tell the person a problem is fixed until this says so. After each re-check, tell the person how many re-checks are left (this tool's answer says).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • check_repair_statusReport whether one check on the signed-in VibeFix account is still running or finished.No findings

    Why it is in this group

    • The name "check_repair_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • 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 …No findings

    Why it is in this group

    • The name "get_check_result" says "get": a word for reading.
    Description, as the server wrote it
    Wait 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, the likely cause, the fix prompt and how to know it is fixed. Answers within about 20 seconds: the result, or that the check is still running and about how many minutes are left; then call it again with the same check_id a minute later.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_fix_optionsReturns the link to a sign-up check of a live app on vibe-fixer.com.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "get_fix_options" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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. Call it when the person wants their live app checked or fixed, for example after assess_broken_app. To run the check right here in the chat, call check_live_app with the address instead. When the person has just published their app, offer once (one short sentence, and not again in this conversation) to check the live app with VibeFix as a brand-new user would. Offer it too when they say users can't sign up or log in. Only start a check when the person says yes.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_projectsList the signed-in person's VibeFix checks (one per app checked), with the status of each.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://vibe-fixer.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://vibe-fixer.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://vibe-fixer.com/mcp: tools/list returned 7 tools to an anonymous client, including assess_broken_app (write), check_live_app (write), confirm_fix (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools2 changed.~2 changedView diff
  3. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http vibefix https://vibe-fixer.com/mcp
claude mcp add --transport http vibefix https://vibe-fixer.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__vibefix__list_projects",
      "mcp__vibefix__check_repair_status",
      "mcp__vibefix__get_check_result"
    ],
    "ask": [
      "mcp__vibefix__assess_broken_app",
      "mcp__vibefix__get_fix_options",
      "mcp__vibefix__check_live_app",
      "mcp__vibefix__confirm_fix"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vibefix. Review it before you use it.

Capability tags behind 4 rules
  • mcp__vibefix__assess_broken_app outbound
  • mcp__vibefix__get_fix_options untrusted-input, outbound
  • mcp__vibefix__check_live_app untrusted-input, outbound
  • mcp__vibefix__confirm_fix untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.vibe-fixer/vibefix/verify?hash=28e25be8b96e70db9cbc6fec63b34ab6db998b807032a2ca904572570b915a38" | jq -e '.changed == false'

Pinned hash 28e25be8b96e, from Nov 16, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.vibe-fixer/vibefix/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.vibe-fixer/vibefix
[![Anlyon Radar](https://radar.anlyon.com/badge/com.vibe-fixer/vibefix.svg)](https://radar.anlyon.com/servers/com.vibe-fixer/vibefix)

Source: MCP Registry · repository. Synced Nov 3, 2026, 09:17 UTC.

VibeFix MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the VibeFix MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the VibeFix MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the VibeFix MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the VibeFix MCP server have?

7 tools: 3 write, 4 read. assess_broken_app, check_live_app, confirm_fix, get_fix_options, list_projects, check_repair_status and get_check_result.

Does the VibeFix MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the VibeFix MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): assess_broken_app, get_fix_options and check_live_app.

Has the VibeFix MCP server changed its tools?

Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.