Offline JPS validator, conformance tester, and experimental evaluator over stdio MCP; keyless.
Connect Runs on your machine
claude mcp add judgment-pack -e JPACK_CONFIG=<JPACK_CONFIG> -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.45.0{
"mcpServers": {
"judgment-pack": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.45.0"
],
"env": {
"JPACK_CONFIG": "<JPACK_CONFIG>"
}
}
}
}{
"mcpServers": {
"judgment-pack": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.45.0"
],
"env": {
"JPACK_CONFIG": "<JPACK_CONFIG>"
}
}
}
}{
"servers": {
"judgment-pack": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.45.0"
],
"env": {
"JPACK_CONFIG": "<JPACK_CONFIG>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
JPACK_CONFIGOptional | Path to a jpack.json project configuration (ADR-0012). Optional: without it the server reads jpack.json from its launch directory (/project in this image; mount a project there), and a project that does not use the convention still validates and evaluates pack documents passed over the wire. |
Details
| Package | ghcr.io/judgment-pack/judgment-pack:0.45.0 (OCI, stdio) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | io.github.Judgment-Pack/judgment-pack |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.