verdict-qa-mcp
A read-only MCP server and release gate over Verdict's QA state — so anything that speaks MCP can consult your QA memory.
Verdict is a Claude Code QA agent that keeps a baseline and reports what broke since
yesterday: findings with stable IDs and ages, every red test classified, flaky tests
quarantined with an expiry, and a verdict of pass | pass with risks | blocked | fail
that names what was not tested.
This distribution is the part of Verdict that other tools talk to. It reads the same state files the agent writes and never writes to them — an orchestrator gating a merge, a Cursor or Codex session, or a CI step commenting on a PR can all ask what the tester last found. The agent itself is a Claude Code plugin with zero dependencies and works without this package.
Note on the name. The distribution is
verdict-qa-mcp; the console script is stillverdict-mcp, and the import package is stillverdict_mcp.verdict-mcpwas taken on PyPI by an unrelated project.
Install
claude mcp add verdict -- uvx --from verdict-qa-mcp verdict-mcp
Or pip install verdict-qa-mcp / uv pip install verdict-qa-mcp.
MCP tools
Every tool carries a read-only annotation, and the server never writes — the tester's memory is public API; the tester's pen is not.
| Tool | Returns |
|---|---|
get_verdict(project) |
last verdict, release blockers, report path, not-tested list |
get_findings(project, status) |
open (default), all, or NEW / STILL_OPEN / RESOLVED / REGRESSED — REGRESSED ranked first |
get_quarantine(project) |
the flaky ledger, each entry with a computed expired flag |
get_history(project) |
run-over-run trend parsed from the report index |
get_report(project, report?) |
full report content, path-guarded to the QA root — so CI can quote the evidence, not just link it |
get_profile(project) |
isolation rules, risk areas, real test commands, and the lessons ledger when one exists |
get_trends(project) |
trajectory, current pressure (open by severity, age, quarantine size), and hotspots — where this project's defects actually cluster |
list_projects() / get_state(project) |
everything with a baseline / the raw state |
project is a key under the solo root (~/.claude/verdict/, override with VERDICT_HOME)
or a repo path in team mode, which resolves <repo>/.qa/.
Command-line entry points
| Command | Does |
|---|---|
verdict-mcp |
the MCP server above |
verdict-gate |
exit-code release gate for CI — keeps "never ran" distinct from "said no" |
verdict-validate |
checks a state file is well-formed (--at-rest for a committed one) |
verdict-run |
runs a pass through the harness |
verdict-accept |
the maintainer's pen: record that a finding's risk is accepted, with a citation and a reason — the one status the tester cannot write |
verdict-facts / verdict-finalize |
measure-then-judge harness halves |
Documentation
Full documentation, the plugin itself, and the published eval results live on GitHub:
- Repository and plugin install
- Published eval results — including the runs that scored badly
- State schema
- Changelog
MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for verdict-qa-mcp 0.85.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| verdict_qa_mcp-0.85.0.tar.gz | 216.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| verdict_qa_mcp-0.85.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 351.5 kB
Release files / verdict_qa_mcp-0.85.0.tar.gz
| Download URL | verdict_qa_mcp-0.85.0.tar.gz |
|---|---|
| Size | 216.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c302698871c2175d72f5cb438e286f71233fb8f0d69b9fa1fde72136bc643e72
|
|
BLAKE2b-256 checksum How to use checksums |
5b1db8756a44fb5a7440bd59f26d2a7f34c1d642205b2a990f5fe615cd1106f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / verdict_qa_mcp-0.85.0-py3-none-any.whl
| Download URL | verdict_qa_mcp-0.85.0-py3-none-any.whl |
|---|---|
| Size | 134.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
743bd9373f5f227151024885704820ca22b73b36c791c548315918a8c7775115
|
|
BLAKE2b-256 checksum How to use checksums |
7f2fff2ea93323d27a908265f0163e1f0c47526c783a936ea9f4a597cb034814
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log
