# io.github.Judgment-Pack/judgment-pack (oci · ghcr.io/judgment-pack/judgment-pack:0.13.0)

Offline JPS validator, conformance tester, and experimental evaluator over stdio MCP; keyless.

- Trust score: 9/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- oci · `ghcr.io/judgment-pack/judgment-pack:0.13.0`: 9/100 (this document), [markdown](https://verifymcp.io/servers/judgment-pack-judgment-pack/ghcr-io-judgment-pack-judgment-pack-0-13-0.md), [page](https://verifymcp.io/servers/judgment-pack-judgment-pack/ghcr-io-judgment-pack-judgment-pack-0-13-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/judgment-pack/judgment-pack:0.13.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - CVE data not yet available for this package.
  - Install-script risk not yet assessed.
  - Dependency-health data not yet available.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- **Capabilities**: 0/100
  - Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add judgment-pack-judgment-pack -- docker run --rm -i ghcr.io/judgment-pack/judgment-pack:0.13.0
```

### Codex

```bash
codex mcp add judgment-pack-judgment-pack -- docker run --rm -i ghcr.io/judgment-pack/judgment-pack:0.13.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "judgment-pack-judgment-pack": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/judgment-pack/judgment-pack:0.13.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  judgment-pack-judgment-pack:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/judgment-pack/judgment-pack:0.13.0"]
```

### Other

```json
{
  "mcpServers": {
    "judgment-pack-judgment-pack": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/judgment-pack/judgment-pack:0.13.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 9)

First indexed and scored.

## MCP tools (9)

### `validate` (~69 tokens)

Validate one JPS document for carrier, structural, and semantic conformance. It does not evaluate rules, choose an outcome, or authorize anything.

Input parameters:

- `document` (string, required): The JPS document to validate, as JSON text.
- `through` (string): Last validation layer to run; defaults to semantic.

### `test_conformance` (~68 tokens)

Run a version-pinned JPS conformance corpus; the bundled corpus by default.

Input parameters:

- `spec_version` (string): Optional exact JPS version; defaults to the bundled draft.
- `suite` (string): Optional path to a local suite directory or manifest.json; omit for the bundled corpus.

### `get_schema` (~47 tokens)

Return the exact bundled JPS JSON Schema for a specification version, with its digest and byte size.

Input parameters:

- `spec_version` (string): Optional exact JPS version; defaults to the bundled draft.

### `describe_runtime` (~28 tokens)

Report this runtime's version, the specification versions it supports, and the provenance of its bundled artifacts.

### `list_examples` (~56 tokens)

List the bundled valid JPS example documents: version-pinned conformance fixtures the runtime embeds and digest-locks, offered read-only as starting points for authoring. They are not authored templates. Use get_example to fetch one by name.

### `get_example` (~92 tokens)

Return one bundled valid JPS example document by name, as JSON text, with its digest and byte size. These are version-pinned conformance fixtures, not authored templates; copy one into a document of your own to start authoring, then validate. Call list_examples for the available names.

Input parameters:

- `name` (string, required): The example name, as reported by list_examples (for example, minimal-expense-approval).

### `list_packs` (~231 tokens)

List the packs this project declares in its jpack.json, resolved: the project's decision id, the pack document's own id and version, the description, the ids of the evidence the pack requires, whether an instance matrix exists, and the project's non-normative hints about where each fact and each piece of evidence is held. The convention is this runtime's (ADR-0012) and is not part of the Judgment Pack Specification. Reading it is how you learn what a project can decide without fetching a pack; call get_pack for one document. The configuration is the JPACK_CONFIG file if that variable is set, otherwise jpack.json in the directory this server was launched in, and an absent configuration is an empty answer with an explanation rather than an error. The hints are the project's own words about where to look: this server holds no credential, opens no network connection, and never reads a source one names. Gathering those values is yours to do with your own access -- and a value you cannot source is reported unknown rather than guessed, so the pack can escalate instead of deciding on an invention.

### `get_pack` (~148 tokens)

Return one pack document this project declares in its jpack.json, by its decision id, as JSON text, with the document's own id and version, its declared specVersion, its digest, and its byte size. The document is the project's own file, served unaltered and read-only; this tool stores nothing and returns nothing you did not already have on disk. Call list_packs for the available decision ids. The file is read through a reader rooted at the configuration's own directory, so a configured path that leaves that directory is refused rather than followed.

Input parameters:

- `pack_id` (string, required): The project's decision id, as reported by list_packs (for example, expense-approval).

### `experimental_evaluate` (~703 tokens)

EXPERIMENTAL SURFACE (ADR-0007): apply the JPS Core §§7-8 resolution model to one conformant pack and one facts document, returning the §8.3 portable disposition (kind, outcomeId, reasons, handoff) and a trace. The disposition is serialized in its RFC 8785 canonical form; a refused evaluation reports its §8.4 error class and no disposition. Only a pack declaring specVersion 0.2.0-draft is evaluated: JPS §11 makes the value exact and requires an unedited 0.1.0-draft pack to be re-declared -- one edit, the specVersion string -- before an implementation claiming this draft evaluates it, so any other version is refused as pack-not-conformant in the preflight phase. The pack arrives either as text in "pack" or as a project decision id in "pack_id", which resolves through the jpack.json convention (ADR-0012); exactly one of the two is supplied, and supplying both is refused rather than given a precedence rule. Every payload echoes the evaluated pack's own id and version as packId and packVersion, read off the document that was evaluated. This is the one tool here that can write, and only where the project told it to (ADR-0018): in a project whose jpack.json declares an audit directory, each completed call appends one record to it -- the pack's identity and digest, the documents evaluated, and the disposition -- and in a project that declares none, nothing is written at all. This runtime's conformance claim is stated, in full and only, in the repository's CONFORMANCE.md; this description states no claim, and the payload carries a conformanceClaimReference member pointing at that file. Whatever that claim says, it is about this implementation and NOT about the pack you pass, the facts you supply, or whether acting on the returned disposition is correct, permitted, or safe (§3.5). It authorizes nothing, executes nothing, and this surface may change or be removed without compatibility promise.

Input parameters:

- `evidence` (string): Optional tri-state evidence availability, as JSON text: an object mapping declared evidence-requirement ids to "present", "absent", or "unknown". An omitted id is unknown. Omit this key entirely to s…
- `facts` (string, required): One JSON facts document, as JSON text; fact.path pointers resolve against it. It is the NESTED document those pointers descend into: for the pointer /request/type write {"request":{"type":"data-acces…
- `pack` (string): The JPS document to evaluate, as JSON text. It must have full document conformance; a non-conformant pack is refused. Mutually exclusive with pack_id.
- `pack_id` (string): A decision id declared in the project's jpack.json, resolved to that pack's document. Mutually exclusive with pack; call list_packs for the available ids.
- `supported_extensions` (array): Extension names this consumer supports.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/judgment-pack-judgment-pack/ghcr-io-judgment-pack-judgment-pack-0-13-0#diagnostics

## Score history

- 2026-08-03: 9

## Links

- Repository: https://github.com/Judgment-Pack/judgment-pack-runtime
- Changelog RSS feed: https://verifymcp.io/servers/judgment-pack-judgment-pack/ghcr-io-judgment-pack-judgment-pack-0-13-0/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/judgment-pack-judgment-pack/ghcr-io-judgment-pack-judgment-pack-0-13-0/changelog.json
- HTML version of this page: https://verifymcp.io/servers/judgment-pack-judgment-pack/ghcr-io-judgment-pack-judgment-pack-0-13-0