io.github.vibefix-tech/vibefix
NPM · @VIBEFIX/MCP
Bug bounty platform for vibe coders. Post bugs, find fixes, run diagnostics.
Available components
Last scanned (7 hours ago)
Scores higher than 65% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 228 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1180 tokens (~98/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.93 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Stability: pass → 0.80 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 5 Nov 2026 · Analysed npm/@vibefix/mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
vibefix_accept_submission ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| submissionId | string | yes | The submission ID to accept (from vibefix_list_submissions) |
No output schema declared.
No examples provided.
vibefix_apply_to_bounty ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | The private bounty ID to apply to |
| message | string | – | Short intro message to the bounty owner (why you're a good fit) |
No output schema declared.
No examples provided.
vibefix_diagnose ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The public URL to scan (e.g. "https://example.com") |
No output schema declared.
No examples provided.
vibefix_get_bounty ~62
Get full details of a specific VibeFix bug bounty by ID, including description, expected vs actual behavior, steps to reproduce, and tech stack.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | The bounty ID (from vibefix_list_bounties) |
No output schema declared.
No examples provided.
vibefix_list_bounties ~85
Browse open bug bounties on VibeFix. Filter by category, platform, or difficulty.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by bug category |
| difficulty | string | – | Filter by difficulty |
| limit | number | – | Max results to return (default 20, max 50) |
| platform | string | – | Filter by vibe coding platform |
No output schema declared.
No examples provided.
vibefix_list_submissions ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | The bounty ID to list submissions for |
No output schema declared.
No examples provided.
vibefix_my_applications ~43
List your applications to private VibeFix bounties, with approval status and job details. Requires VIBEFIX_API_KEY on a developer account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibefix_my_bounties ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibefix_my_profile ~41
Get your VibeFix developer profile: XP, level, wallet balance, jobs completed, and approval status. Requires VIBEFIX_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibefix_my_submissions ~39
List all your submitted solutions on VibeFix, with their acceptance status and linked job details. Requires VIBEFIX_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibefix_post_bounty ~249
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actualBehavior | string | – | What actually happens |
| bountyUsd | number | – | Cash bounty in USD (e.g. 25 for $25). Omit or set to 0 for a free bounty. |
| category | string | yes | – |
| chipsStaked | number | – | VF Chips to stake as difficulty signal (default 1, min 1) |
| codeLink | string | – | Link to the repo or relevant code |
| description | string | yes | Full description of the bug or issue |
| expectedBehavior | string | – | What should happen |
| platform | string | yes | The vibe coding platform the app was built with |
| stack | string | – | Tech stack (e.g. "Next.js, Supabase, Stripe") |
| stepsToReproduce | string | – | Step-by-step instructions to reproduce the bug |
| title | string | yes | Short title describing the bug (e.g. "Login broken on Safari mobile") |
No output schema declared.
No examples provided.
vibefix_submit_solution ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bountyId | string | yes | The bounty ID you're submitting a fix for |
| description | string | yes | Describe what you fixed and how. Be specific — the customer needs to verify your fix. |
| repoLink | string | – | Link to your branch, PR, or repo with the fix (optional but strongly recommended) |
No output schema declared.
No examples provided.
How do I install the io.github.vibefix-tech/vibefix MCP server?
io.github.vibefix-tech/vibefix runs locally as an npm package, launched with npx -y @vibefix/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @vibefix/mcp
claude mcp add vibefix-tech-vibefix -- npx -y @vibefix/mcp
What is the io.github.vibefix-tech/vibefix MCP server?
io.github.vibefix-tech/vibefix is an MCP server listed in the public MCP registry as io.github.vibefix-tech/vibefix. Bug bounty platform for vibe coders. Post bugs, find fixes, run diagnostics. This page covers its npm package (@vibefix/mcp).
Is the io.github.vibefix-tech/vibefix MCP server safe to use?
io.github.vibefix-tech/vibefix scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.vibefix-tech/vibefix MCP server expose?
io.github.vibefix-tech/vibefix exposes 12 tools: vibefix_list_bounties, vibefix_get_bounty, vibefix_my_profile, vibefix_my_submissions, vibefix_post_bounty, and 7 more. Their descriptions and schemas cost roughly 1,005 tokens of context every time the server is loaded.
Is the io.github.vibefix-tech/vibefix MCP server still maintained?
io.github.vibefix-tech/vibefix is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.vibefix-tech/vibefix MCP server under?
io.github.vibefix-tech/vibefix declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.