VibeFix
REMOTE · VIBE-FIXER.COM · SCANNED SEP 24
Free triage for broken apps built with Lovable, Base44, v0, Bolt or Replit, then a live AI repair.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 300 tokens (~150/item across 2 items; 1 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the VibeFix MCP server?
VibeFix is a hosted endpoint at https://vibe-fixer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vibe-fixer.com
claude mcp add --transport http com-vibe-fixer-vibefix 'https://vibe-fixer.com/mcp'
{
"mcpServers": {
"com-vibe-fixer-vibefix": {
"url": "https://vibe-fixer.com/mcp"
}
}
} {
"servers": {
"com-vibe-fixer-vibefix": {
"type": "http",
"url": "https://vibe-fixer.com/mcp"
}
}
} [mcp_servers.com-vibe-fixer-vibefix] url = "https://vibe-fixer.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-vibe-fixer-vibefix": {
"type": "remote",
"url": "https://vibe-fixer.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-vibe-fixer-vibefix --url 'https://vibe-fixer.com/mcp' --transport streamable-http
mcp_servers:
com-vibe-fixer-vibefix:
url: "https://vibe-fixer.com/mcp" {
"McpServers": {
"com-vibe-fixer-vibefix": {
"Transport": "http",
"Url": "https://vibe-fixer.com/mcp"
}
}
} assistant mcp add com-vibe-fixer-vibefix -t streamable-http -u 'https://vibe-fixer.com/mcp'
{
"mcpServers": {
"com-vibe-fixer-vibefix": {
"type": "http",
"url": "https://vibe-fixer.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://vibe-fixer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vibe-fixer.com | CN=YE1,O=Let's Encrypt,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5b645f7a8b0d3200da871dff7aadc2eaa0b |
| SANs: vibe-fixer.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vibe-fixer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| vibe-fixer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vibe-fixer.com/mcp | Verified | 200 | |
| http (plaintext) | http://vibe-fixer.com/mcp | HTTPS enforced | 301 | https://vibe-fixer.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_broken_app Assess a broken AI-built app ~230
Triage a problem in an app built with Lovable, Base44, v0, Bolt, Replit or a similar AI app builder — a button that does nothing, a blank page, a login that fails, data that will not save, a deploy that broke a working app. Returns the most likely cause for that symptom, the evidence that would confirm it, and what a fix would involve. Call this when someone describes an app they built with an AI tool and cannot debug themselves. Do NOT call it for code you can read and fix directly, for a library or framework question, or for an app the person built by hand.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | The builder it was made with, if known: lovable, base44, v0, bolt, replit, other. |
| 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". |
| url | string | – | The public URL of the deployed app, if there is one. Never a private or internal address. |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | yes | – |
| evidence_to_confirm | array | yes | – |
| likely_cause | string | yes | – |
| next_step | string | yes | – |
| platform | string | – | – |
| what_a_fix_involves | string | – | – |
| what_this_assessment_cannot_know | string | – | – |
No examples provided.
What is the VibeFix MCP server?
VibeFix is an MCP server listed in the public MCP registry as com.vibe-fixer/vibefix. Free triage for broken apps built with Lovable, Base44, v0, Bolt or Replit, then a live AI repair. This page covers its hosted endpoint (https://vibe-fixer.com/mcp).
Is the VibeFix MCP server safe to use?
VibeFix scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VibeFix MCP server expose?
VibeFix exposes 1 tool: assess_broken_app. Their descriptions and schemas cost roughly 230 tokens of context every time the server is loaded.
Does the VibeFix MCP server require authentication?
No. We connected to VibeFix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the VibeFix MCP server still maintained?
VibeFix is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.