Vibefix

io.github.vibefix-techPublished by GitHub account vibefix-techv0.3.2Updated Oct 24, 2026

Bug bounty platform for vibe coders. Post bugs, find fixes, run diagnostics.

VerifiedSTDIODesktop onlyDeveloper Tools Business & Commerce

Server details

Identifier: io.github.vibefix-tech/vibefix
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account vibefix-tech for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.vibefix-tech%2Fvibefix.svg)](https://sourceweft.com/mcp/io.github.vibefix-tech%2Fvibefix?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Vibefix is a local MCP server for a bug bounty platform aimed at vibe coders, letting an assistant post bugs, find fixes and run diagnostics.

What you can do: Post bugs to the Vibefix bug bounty platform and find fixes for them, per the registry description. Run diagnostics as part of that workflow. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it: Worth considering if you use the Vibefix bug bounty platform and want an assistant to file bugs, look for fixes, or run diagnostics from within a coding session.
Requirements: Runs as a local process via the npm package @vibefix/mcp over stdio, so Node.js is needed. Requires a VibeFix API key supplied in the VIBEFIX_API_KEY environment variable, obtained from the provider's dashboard. Desktop only.

Before you install

Requires a secret API key in VIBEFIX_API_KEY; keep it out of shared logs and configuration. Posting bugs sends data to the Vibefix platform, a third party, so avoid including private code or credentials in submissions.

Installation

In SourceWeft

Open Vibefix in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.