Autonomous QA Engineer MCP (GolffyCoding/Auto-QA-Engineer-MCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.
Provides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.
Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
GolffyCoding
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
QA_MCP_INSTRUCTIONS_FILEPath to a text/markdown file of your team's conventions, appended to what the LLM is told on connect — see [Customizing for your company](#customizing-for-your-company)QA_MCP_K6_BINapi.load_test (load testing) [k6](https://github.com/grafana/k6) — k6 binary (or set )QA_MCP_STATE_DBPersistence file path (default ./qa-mcp-state.json) — point your whole team at the same path to share stateGITHUB_TOKENFor ci.run/ci.get_status with GitHub Actions (needs actions:write)GITLAB_TRIGGER_TOKEN/ GITLAB_API_TOKEN For ci.run (trigger) / ci.get_status (API) with GitLab CIGITLAB_API_TOKENGITLAB_TRIGGER_TOKEN / For ci.run (trigger) / ci.get_status (API) with GitLab CIQA_MCP_ALLOW_AUTO_APPLYMust be 1 for fix_loop.apply_patch to write to disk — see [Built for a team, not a demo](#built-for-a-team-not-a-demo)Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
1/1 tools missing one or more hints — fn (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tool test coverage
Only 0/1 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/golffycoding-auto-qa-engineer-mcp-3p00lc)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check