Developer · Remote MCP server
VibeFix
Tests your live published app like a first customer, whatever built it. Free test; fixes on a plan.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.vibe-fixer/vibefix- Version
- 1.1.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.vibe-fixer
- Namespace
- Namespace verified by the MCP Registry via the domain vibe-fixer.com · how
- Website
- vibe-fixer.com
- Repository
- github.com/yos88da/vibefix-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://vibe-fixer.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- vibefix 1.1.3 · protocol 2025-06-18
- Tools discovered
- 2:
assess_broken_app,get_fix_options - Checked on
- 2026-10-05
How to connect VibeFix
VibeFix is a remote MCP server: there is nothing to install. Its endpoint is https://vibe-fixer.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Vibe MCPSocial layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers. | Local · stdio |
| Vibe MCP - Real Chrome, RemotelyDrive your real, logged-in Chrome from any MCP client - even from a remote machine, no inbound port. | Remote & Local · HTTP, stdio |
| Vibecheck MCPAI Code Firewall - MCP Server for hallucination prevention in AI development. | Local · stdio |
| VibedeployDeploy and host AI-built websites on EU infrastructure, straight from your AI agent. | Remote · HTTPLive check: ✓ handshake |
| VibeHackerProduct Hunt for AI tools. Search, submit, upvote from Claude Code or Cursor. | Remote · HTTPLive check: ✓ handshake |
| VibeKitBuild, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client. | Remote · HTTPLive check: ✓ handshake |
| Vibelens MCPVibeLens MCP tool for AI to visualize code changes with inline annotations in VS Code/Cursor. | Local · stdio |
| VibeliveMultiplayer for agentic coding terminals: live cursors, presence, chat. | Local · stdio |