mcp server
Vynix
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.
Description as published by the maintainer. Source
- version 0.1.4
- active
active — Most recent push to the repository was 2026-08-06.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 6 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.4 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-28 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-28 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.dundas/thinkrun
— last commit 2026-07-17, shares bug-reporting
Browser control + session recording MCP for AI coding agents (Claude Code, Cursor) — real Chrome.
-
ai.canaryusers/canaryusers
— last commit 2026-06-13, shares qa
A flock of AI users tests your deployed app and reports where real people get stuck, with fixes.
-
ai.testiv/mcp
— last commit 2026-08-04, shares qa
Local-first visual regression for AI agents: verdicts, diff images, explain_snapshot. No API key.
-
com.clauxel.agentichtmlexportqa/agentichtmlexportqa-mcp
— last commit 2026-05-20, shares qa
Paid remote MCP for agentic HTML export QA MCP, structured receipts, audit logs, and reviewer-ready
-
io.github.aarwitz/tapp
— last commit 2026-07-30, shares qa
Autonomous QA for iOS + web — agents get a deterministic ship/no-ship verdict, no test code
-
io.github.Aboudjem/sniff
— last commit 2026-05-30, shares qa
QA + a11y scanner: walks your running app's real user flows and reports what's broken.
-
Vibe Test — Browser Testing Agent
— last commit 2026-06-08, shares qa
Code-aware browser testing agent — 13 Playwright tools for AI code editors via MCP
-
Before Users Do
— last commit 2026-08-04, shares qa
Browser-backed QA with evidence and fix-ready reports for coding agents.
-
Argus Testing — Autonomous QA MCP
— last commit 2026-07-23, shares qa
Autonomous QA MCP for web and macOS that tests like a real engineer, finds bugs, and verifies them.
-
io.github.cyanheads/stackexchange-mcp-server
— last commit 2026-07-17, shares qa
Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles.
These share tags the maintainers applied themselves, such as bug-reporting, qa. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-agents, ai-diagnosis, bug-reporting, claude, copilot, developer-tools, feedback-tool, mcp, mcp-server, model-context-protocol, qa, visual-feedback, vynix, website-annotation.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab