Git QA runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 6 Nov 2026.
Open-source human-in-the-loop QA runner: an AI agent works the test sheet, a person signs off.
What the code does
We read the source, 20 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(command, [...args], { stdio: ['ignore', 'pipe', 'pipe'] });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Git QA
same job, measured the same wayRun, write and test the API requests saved in a Kurlo workspace, the open source API client.
Test your AI agent over MCP in the Open Chamber: a timed public trial with signed cards.
Test AI agent workflows against service twins with injected faults. Runs locally; no source upload.
Test the idea before you build it. Rapidly works inside your AI agent.
Tests an AI agent's purchase against the task it was given. Paid per call in USDC via x402.
Marks the lines in your test suite that current pytest no longer runs — and the config keys it silen
Catches your AI coding agent when it games the tests - locked-test hashes, tamper detection.
Penetration Testing Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Git QA — questions
Answers built from our own checks of this server.