Verdict QA MCP server
Read-only MCP server over Verdict QA state: verdicts, findings, flaky quarantine, history.
1 stars
Reviews
Write oneNobody has reviewed Verdict QA yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Verdict QA tools (10, 2 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
get_findingsFindings for a project. status: 'open' (default), 'all', 'accepted' (the maintainer's accepted risks), or one of NEW / STILL_OPEN / RESOLVED / REGRESSED / ACCEPTED. REGRESSED sort first, then by severity, then by age (oldest first shown last run's pressure).
get_historywrite actionRun history, oldest first. Machine-native from runs.jsonl where it exists; the INDEX.md markdown parse remains as the legacy fallback for history that predates the file.
get_profileThe project's QA profile — isolation rules, risk areas, real test commands — plus the lessons ledger (judgment corrections) when one exists.
get_quarantineThe flaky-test quarantine ledger, with an expired flag per entry.
get_questionsThe questions the tester parked for a person — parked ones with their age, and answers no run has read yet. Answer with `verdict-answer`.
get_reportContent of a QA report. Default: the last run's report; pass `report` (a path relative to the QA root, as returned by get_verdict/get_history) for an earlier one. Reports over 512KB are truncated with a flag.
get_stateThe full raw state.json for a project (escape hatch; schema in docs/state-schema.md).
get_trendswrite actionRun-over-run trajectory: per-run test counts and verdicts parsed from the INDEX, plus the current pressure picture — open findings by severity, age distribution, quarantine size. Direction is the signal; cells the INDEX writes as prose come back raw with parsed numbers where possible.
get_verdictThe last recorded verdict, release blockers, and report path for a project.
list_projectsList every project with a Verdict baseline in the solo state root.
Public scan report
scanner v0.1.8 · 2026-09-19 · same rubric, same numbers if you re-run it
- Code scan22 source files scanned20/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- mediumsubprocess with shell=True
exec.shell-trueverdict_qa_mcp-0.90.1/src/verdict_mcp/harness.py: …roc = subprocess.run(cmd, cwd=str(cwd), shell=True, capture_output=True, text=True, …
Grade history
- 2026-09-19restoreC → Ascore 85: subprocess with shell=True
- 2026-09-19downgradeB → Cscore 66: Whole environment serialized (possible credential exfil); subprocess with shell=True
Install directly
claude mcp add verdict -- uvx verdict-qa-mcp
Verdict QA: common questions
- Is Verdict QA MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the Verdict QA safety report
- How do I install Verdict QA?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Verdict QA need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Verdict QA maintained?
- The last commit was 2 days ago (2026-09-19). The latest release is v0.90.1.