assess_broken_app — VibeFix MCP Tool
assess_broken_app
(assess broken app) is one of 1 tool on the
VibeFix
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call assess_broken_app from your client
- Claude Code VibeFix assess_broken_app run in your project directory
- Claude Desktop VibeFix assess_broken_app ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VibeFix assess_broken_app ~/.cursor/mcp.json
- VS Code VibeFix assess_broken_app .vscode/mcp.json
- Zed VibeFix assess_broken_app ~/.config/zed/settings.json
- Windsurf VibeFix assess_broken_app ~/.codeium/windsurf/mcp_config.json
- Cline VibeFix assess_broken_app ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VibeFix assess_broken_app ~/.gemini/settings.json
- Grok VibeFix assess_broken_app .mcp.json (in your project root)
- ChatGPT VibeFix assess_broken_app Settings → Connectors → Advanced → Developer mode
- Claude.ai VibeFix assess_broken_app Settings → Connectors → Add custom connector
- LangChain VibeFix assess_broken_app pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vibefix https://vibe-fixer.com/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.