A
licenseA
qualityD
maintenanceAn MCP server that integrates BugHerd bug tracking with AI assistants, providing 37 tools for complete BugHerd API v2 coverage.
37
33 npm
7
MIT
vynix-mcp-server
Officialby UseVynix
Related Servers
Alternatives to vynix-mcp-server
Related 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.57 npmMIT
- 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
- FlicenseNot gradedqualityAmaintenanceMCP server that exposes web page annotations to AI coding agents, enabling automated implementation of visual feedback and design tweaks.4 npm163-
- AlicenseAqualityCmaintenanceBug bounty platform for vibe coders. Post bugs from AI-generated code, browse bounties, apply to fix, submit solutions, and run website diagnostics from any MCP client.1221 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI coding assistants QA superpowers, enabling users to report bugs by pointing, clicking, or typing while automatically capturing diagnostic data for AI-driven test-feedback-fix loops.8 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for visual feedback, video direction, and QA assertions on web pages, enabling AI agents to read, reply, and resolve annotations in real time.6MIT
TDQS
A4.1/5.0
Scored across 17 tools
Disambiguation4/5
Most tools are clearly distinct, but get_metrics and get_activity both surface recent activity, which could lead to misselection. Other tools like list_annotations vs get_annotation or get_annotation_analysis vs diagnose_annotation are clearly differentiated by read/action semantics.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_projects, update_annotation_status, diagnose_annotation). There is no mixing of conventions or vague verbs, making the set predictable and easy to navigate.
Tool Count4/5
With 17 tools, the server is slightly above the ideal range, but each tool serves a distinct purpose in the annotation management, AI diagnosis, and GitHub integration workflow. The count feels justified rather than padded, though a few tools could potentially be consolidated.
Completeness4/5
The core lifecycle is well covered: listing and getting annotations, updating status, commenting, running/reading AI analysis, generating prompts, and creating GitHub issues. Missing operations like create/delete annotation or update/delete comments are minor gaps, likely because annotations are created externally or those actions are outside the server's scope.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive