io.github.vibefix-tech/vibefix
NPM · @VIBEFIX/MCP · SCANNED AUG 3
Bug bounty platform for vibe coders. Post bugs, find fixes, run diagnostics.
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 134 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @vibefix/mcp
claude mcp add vibefix-tech-vibefix -- npx -y @vibefix/mcp
codex mcp add vibefix-tech-vibefix -- npx -y @vibefix/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vibefix-tech-vibefix": {
"type": "local",
"command": [
"npx",
"-y",
"@vibefix/mcp"
],
"enabled": true
}
}
} openclaw mcp add vibefix-tech-vibefix --command npx --arg -y --arg @vibefix/mcp
mcp_servers:
vibefix-tech-vibefix:
command: "npx"
args: ["-y", "@vibefix/mcp"] {
"mcpServers": {
"vibefix-tech-vibefix": {
"command": "npx",
"args": [
"-y",
"@vibefix/mcp"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +36
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Maintenance: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −39
- Known CVEs: partial → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- 31 Jul 26 −10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +53
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → good ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 29 Jul 26 +1
- Dependency health: unverified → partial ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 40
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@vibefix/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.