vibefix
Provides website diagnostics by running Lighthouse audits and JavaScript error scans on URLs to return reports on performance, SEO, and potential bugs.
Allows browsing and filtering bug bounties specifically associated with the Replit platform, enabling users to find and resolve development issues within that environment.
@vibefix/mcp
Your AI built it. It broke. Post the bug, a real developer fixes it.
VibeFix is a bug bounty platform for vibe coders. This MCP server lets you browse bounties, post bugs, submit fixes, and run website diagnostics directly from Claude Code, Cursor, Windsurf, or any MCP-compatible client. Free to post.
Setup
1. Get an API key
Sign in to VibeFix as a developer → Dashboard → MCP / API → Generate Key.
2. Add to your MCP client
Claude Code (~/.claude.json):
{
"mcpServers": {
"vibefix": {
"command": "npx",
"args": ["@vibefix/mcp"],
"env": {
"VIBEFIX_API_KEY": "vf_your_key_here"
}
}
}
}Claude Desktop (claude_desktop_config.json) — same config above.
Cursor / Windsurf — go to Settings → MCP Servers and paste the same JSON.
3. Start using it
Ask your AI assistant:
"List open VibeFix bounties for deployment bugs" "Show me the full details for job j57..." "Submit my fix for job j57... — here's what I changed: ..."
Related MCP server: Mushi-Mushi
Available tools
For developers
Tool | Description |
| Browse open bounties — filter by |
| Full bounty details: description, expected vs actual behavior, stack |
| Your XP, level, wallet balance, and approval status |
| Your submitted fixes with acceptance status |
| Your applications to private bounties with approval status |
| Apply to a private bounty with an intro message |
| Submit your fix with a description and repo link |
For customers
Tool | Description |
| Post a new bounty — free goes live instantly, paid returns checkout URL |
| List your posted bounties with status and submission counts |
| See all submissions received for one of your bounties |
| Accept a winning fix — awards payout and XP to the developer |
Diagnostics
Tool | Description |
| Run a Lighthouse audit + JS error scan on any URL — returns performance, SEO, and bug report |
Filters for vibefix_list_bounties
category:
deploymentauthpaymentsbug_fixperformanceotherplatform:
cursorboltlovablereplitv0otherdifficulty:
easymediumhard
Environment variables
Variable | Required | Default | Description |
| Yes | — | Your API key from vibefix.co/dashboard/mcp |
| No |
| Override for self-hosted instances |
How it works
The MCP server connects to the VibeFix API at vibefix.co/api/mcp/v1. Your API key authenticates write operations (apply, submit). Browsing open jobs requires no key.
License
MIT
Available Tools
12 toolsvibefix_accept_submissionA
Accept a winning submission for your bounty. This marks the job complete, awards XP and bounty payout to the developer, and rejects all other pending submissions. Requires VIBEFIX_API_KEY on a customer account.
Inputs: submissionId (required).
vibefix_apply_to_bountyA
Apply to a private VibeFix bounty. The owner will review your application and grant access if approved. Only needed for private bounties — public ones can be submitted to directly. Requires VIBEFIX_API_KEY.
Inputs: bountyId (required), message.
vibefix_diagnoseA
Run a free diagnostic scan on any public URL. Returns performance, accessibility, SEO, and best practices scores plus a list of issues found — each with a ready-made bounty pre-fill so the user can post a fix request in one click. No API key required.
Inputs: url (required).
vibefix_get_bountyA
Get full details of a specific VibeFix bug bounty by ID, including description, expected vs actual behavior, steps to reproduce, and tech stack.
Inputs: bountyId (required).
vibefix_list_bountiesA
Browse open bug bounties on VibeFix. Filter by category, platform, or difficulty.
Inputs: category, platform, difficulty, limit.
vibefix_list_submissionsA
List all submissions received for one of your bounties, with developer info and fix descriptions. Use vibefix_my_bounties to find bounty IDs. Requires VIBEFIX_API_KEY on a customer account.
Inputs: bountyId (required).
vibefix_my_applicationsA
List your applications to private VibeFix bounties, with approval status and job details. Requires VIBEFIX_API_KEY on a developer account.
Inputs: no named parameters.
vibefix_my_bountiesA
List all bounties you have posted on VibeFix as a customer, with their status and submission counts. Requires VIBEFIX_API_KEY on a customer account.
Inputs: no named parameters.
vibefix_my_profileA
Get your VibeFix developer profile: XP, level, wallet balance, jobs completed, and approval status. Requires VIBEFIX_API_KEY.
Inputs: no named parameters.
vibefix_my_submissionsA
List all your submitted solutions on VibeFix, with their acceptance status and linked job details. Requires VIBEFIX_API_KEY.
Inputs: no named parameters.
vibefix_post_bountyA
Post a new bug bounty on VibeFix. Free bounties go live immediately. Paid bounties return a checkout URL to complete payment in the browser. Requires VIBEFIX_API_KEY on a customer account.
Inputs: title (required), description (required), category (required), platform (required), +7 more.
vibefix_submit_solutionA
Submit your fix for a VibeFix bounty. Include a clear description of what you changed and a link to the repo/branch with your fix. Requires VIBEFIX_API_KEY.
Inputs: bountyId (required), description (required), repoLink.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool serves a distinct role: diagnosis, posting/listing bounties, applying, submitting, managing submissions, and profile viewing. No two tools overlap in purpose, and the descriptions clearly differentiate customer vs. developer actions.
All tools follow a consistent pattern: 'vibefix_' prefix with lowercase snake_case and a verb_noun structure (e.g., list_bounties, accept_submission). Naming is predictable and logically organized.
With 12 tools, the server covers both customer and developer workflows without being bloated. Each tool serves a necessary function, and the count is well-scoped for a bounty platform.
The tool surface covers the core lifecycle: diagnose, post, list, get, apply, submit, review submissions, accept, and profile. Minor gaps like editing bounties or withdrawing applications exist but do not hinder the primary flow.
Maintenance
Related MCP Connectors
Build, deploy, and operate hosted web apps on VibeKit (vibekit.bot) from any MCP client.
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
ArcAgent MCP server for bounty discovery, workspace execution, and verified coding submissions.
Security, SEO and AI-visibility scanner for web apps · free scans and focused checks via MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for VibeCheck bug reports. Gives AI assistants direct access to screen recordings, console logs, network requests, user actions, and web vitals — right inside your editor.511 npmMIT
- AlicenseAqualityAmaintenanceBug-report triage and fix-dispatch MCP for vibe coders. Ask your AI coding agent for a plain-English diagnosis of any user-reported bug — with evidence, blast radius, and a paste-ready fix prompt — then dispatch an automated GitHub fix PR without a second LLM key. 71 tools, Supabase-backed, MIT SDK. npx @mushi-mushi/mcp86263 npm3MIT

vynix-mcp-serverofficial
AlicenseAqualityDmaintenanceAI-powered website feedback and visual bug reporting MCP server that lets AI coding assistants access Vynix projects, annotations, and create GitHub issues with rich debugging context.1760 npm11MIT- AlicenseAqualityBmaintenanceVoice-powered bug reporting MCP server with 13 tools. Captures console logs, network errors, DOM traces, and developer voice descriptions. AI reads structured reports to find and fix bugs automatically. Chrome Extension + Python CLI.8MIT