vibefix
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBEFIX_URL | No | Override for self-hosted instances | https://vibefix.co |
| VIBEFIX_API_KEY | Yes | Your API key from vibefix.co/dashboard/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vibefix_list_bountiesA | Browse open bug bounties on VibeFix. Filter by category, platform, or difficulty. |
| 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. |
| vibefix_my_profileA | Get your VibeFix developer profile: XP, level, wallet balance, jobs completed, and approval status. Requires VIBEFIX_API_KEY. |
| vibefix_my_submissionsA | List all your submitted solutions on VibeFix, with their acceptance status and linked job details. Requires VIBEFIX_API_KEY. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| vibefix_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. |
| vibefix_my_applicationsA | List your applications to private VibeFix bounties, with approval status and job details. Requires VIBEFIX_API_KEY on a developer account. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.