World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Offline JPS validator, conformance tester, and experimental evaluator over stdio MCP; keyless.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 18/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Judgment Pack. Follow https://mcp.popnx.com/i/judgment-pack.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Docker on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Judgment Pack for Claude on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "judgment-pack": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/judgment-pack/judgment-pack:0.46.0" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Judgment Pack tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
SettingsDeveloperEdit Config
{
"mcpServers": {
"judgment-pack": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}Use Judgment Pack and tell me what you can do for me, then show me one thing✓ If Claude says it is using Judgment Pack or shows a Judgment Pack tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
JPACK_CONFIG 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 d…Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Judgment Pack yet
Judgment Pack runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Judgment Pack
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Docker on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Judgment Pack for Claude Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user judgment-pack -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Judgment Pack tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user judgment-pack -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0You should see Judgment Pack listed as connected
Use Judgment Pack and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Judgment Pack or shows a Judgment Pack tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
JPACK_CONFIG 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 d…Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Docker on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Judgment Pack for Cursor on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "judgment-pack": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/judgment-pack/judgment-pack:0.46.0" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Judgment Pack tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Use Judgment Pack and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Judgment Pack or shows a Judgment Pack tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
JPACK_CONFIG 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 d…Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Docker on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Judgment Pack for VS Code on this computer, in this order: 1) Check Docker with docker --version. If it is missing, tell me to install it from https://www.docker.com/products/docker-desktop/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "judgment-pack": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/judgment-pack/judgment-pack:0.46.0" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Judgment Pack tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
docker --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Install Docker Desktop: on Mac open Docker.dmg and drag the icon to Applications (pick Apple silicon or Intel to match your Mac) · on Windows double-click Docker Desktop Installer.exe · then open the Docker Desktop app and leave it running. No curl command needed
Open the Docker download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: docker --version
Install once; it works for everything that needs Docker
Use Judgment Pack and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Judgment Pack or shows a Judgment Pack tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
JPACK_CONFIG 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 d…Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user judgment-pack -- docker run -i --rm ghcr.io/judgment-pack/judgment-pack:0.46.0Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"judgment-pack": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"judgment-pack": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"judgment-pack": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/judgment-pack/judgment-pack:0.46.0"
]
}
}
}JPACK_CONFIG envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 17, 2026
The registry name was verified with the GitHub account Judgment-Pack, which owns the repo
Code last changed 2 days ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/judgment-pack)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.46.0) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Judgment Pack | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Status: pre-1.0
Tagged binaries are official only when they appear on this repository's GitHub Releases page
with
checksums.txt. Development checkouts may temporarily embed unreleased JPS snapshots, but
the release workflow rejects them.
judgment-pack is the vendor-neutral reference runtime for the Judgment Pack Specification (JPS). It is a reference implementation, not the only valid one: the normative specification, schemas, and conformance corpus are owned by the separate judgment-pack-spec repository, and an independent implementation is judged against the complete normative requirements of the conformance class it claims — not against this runtime. Results from the corpus published for the exact version it names are required evidence for such a claim and are not exhaustive evidence of it (§3.4.1).
The runtime validates documents. It does not fetch a source, authorize an action, or establish truth, organizational authority, safety, or operational fitness. It bundles 0.1.0-draft, 0.2.0-draft, and Core 0.3.0, and validates a document against its exact declaration. Core 0.3.0 resources are imported from the published Spec tag v0.3.0, commit 27cb29bf13e4a2d58d69fe19c7ebfeb762b014fc. Core 0.3.0 support is base-only. Runtime discovery reports evaluatorCapabilities separately from document supportedSpecVersions, with supportedProfiles: ["base"] scoped to the Core 0.3.0 evaluator entry. This says nothing about Policy or Dialect profile support.
For the version covered by the claim in CONFORMANCE.md, one shared evaluator applies the specification's §§7–8 resolution model per ADR-0007, and ten surfaces reach it: jpack experimental evaluate and evaluate-corpus, the project walk jpack packs test, the graph verbs jpack experimental graph evaluate and graph test, the version comparison jpack experimental compare, and the experimental_evaluate, experimental_test_packs, experimental_test_cases and experimental_test_graphs MCP tools. The experimental namespace is a stability statement: such a surface may change or be removed without compatibility promise. It is not a statement about conformance. That evaluator implements the evaluator conformance class Core 0.2.0-draft adds — the §8.2 input preflight, the §8.3 portable disposition with its RFC 8785 byte agreement, the §8.4 error classes and their fixed precedence, and the §10 limits — per ADR-0010 and ADR-0011.
Pack-aware operations select the evaluator contract from the exact pack's specVersion: 0.2.0-draft or 0.3.0. Internal legacy entry points and standalone authoring tools retain their 0.2.0-draft default; standalone tools accept explicit spec_version: "0.3.0". Selection never infers a version from a routes member. See ADR-0063 for the compatibility decisions.
This runtime's conformance claim is stated, in full and only, in [CONFORMANCE.md](CONFORMANCE.md). JPS §3.4.1 fixes the entire form such a claim may take — the class, one exact specVersion, the corpus version, the results obtained, and in the claim's own words that every row of that corpus version passed — so this README states no part of it and neither does any other surface: a partial restatement would be the partial claim §3.4.1 forbids. Read that file for the claim, its version scope, its evidence, and everything it does not assert, which includes anything at all about a pack, its facts, or the wisdom of acting on a disposition (§3.5). jpack experimental evaluate-corpus runs the bundled evaluation corpus and reports its rows — the evidence §3.4.1 requires of a claim of this class, and explicitly not exhaustive evidence of one; see CONFORMANCE.md.
That command carries one further opt-in, --rfc0008-quantifiers, which is a draft-RFC prototype per ADR-0009: it admits the collection quantifiers exists, every, and uniform proposed by the specification's RFC 0008 (Draft). Those operators belong to no published JPS version. A pack using one is not valid under JPS 0.1.0-draft, spec validate rejects it, the evaluator without the flag refuses it, and every successful evaluation payload produced under the flag says so in band through a draftPrototype member — a refusal is an operational error and carries none. The flag is CLI only; the MCP tool does not expose it.
A second opt-in, --rfc0016-outcome-values, is a draft-RFC prototype on the same terms, per ADR-0039. It admits the value declarations proposed by the specification's RFC 0016 (Draft): an outcome declares named values under org.judgmentpack.outcome-values, each a constant or a copy of one fact, and the disposition of that outcome carries them in a value member. That member is the draft's and no member of §8.3. A declared value that does not resolve withholds the outcome, and the result is unresolved with reason unknown. The name is reserved, so a pack carrying a declaration is not valid under any published JPS version, spec validate rejects it, and the evaluator without the flag refuses it. A value drawn from a fact is a copy of that fact and is not verified. The two flags are mutually exclusive, and this one is CLI only too.
The command binary is jpack. The project, repository, and release archives keep the judgment-pack name; the executable they carry is jpack.
jpack version
jpack artifact version --base [--candidate ] jpack dialect contract jpack dialect init [--dialect-version 2|3] jpack dialect canonicalize jpack dialect digest jpack dialect validate jpack dialect schema [--dialect-version 2|3] jpack dialect reference jpack dialect check --pack jpack spec validate jpack spec test-conformance [suite] [--strict] jpack spec schema jpack spec examples [name] [--spec-version V] jpack packs list (jpack.json project convention; ADR-0012, not part of the spec) jpack packs validate [--id X] jpack packs test [--id X] [--require-matrix] (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md) jpack packs suggest [--id X] [--base ROW] [--write F|-] [--max N] [--include-hugs] (candidate row INPUTS, never rows; ADR-0024) jpack packs lock (declare the current documents as the project's reviewed set; ADR-0019) jpack packs verify (check the project against that reviewed set) jpack packs lint [--producers M] (every consulted pointer has a producer; ADR-0022) jpack packs schema jpack mcp jpack experimental evaluate (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md) jpack experimental evaluate --pack-id X (EXPERIMENTAL SURFACE; resolves one decision id through jpack.json) jpack experimental evaluate --rfc0008-quantifiers (DRAFT-RFC PROTOTYPE; not an input the class defines) jpack experimental evaluate --rfc0016-outcome-values (DRAFT-RFC PROTOTYPE; a pack that declares values is not an input the class defines) jpack experimental evaluate-corpus (EXPERIMENTAL SURFACE; corpus results, the evidence §3.4.1 requires) jpack experimental compare --inputs (EXPERIMENTAL SURFACE; the inputs two versions decide differently; ADR-0045) jpack experimental graph list (EXPERIMENTAL: the configured graphs, resolved; ADR-0029) jpack experimental graph validate (EXPERIMENTAL composition prototype; spec RFC 0002, Draft; ADR-0015) jpack experimental graph evaluate [--inputs ] [--rehearsal] (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md) jpack experimental graph explain (the evaluation plan; nothing is evaluated) jpack experimental graph test --rows (EXPERIMENTAL SURFACE; claim: CONFORMANCE.md) jpack experimental graph schema jpack experimental policy contract jpack experimental policy init --kind policy --format-version 0.0.2 --id --version jpack experimental policy schema --kind policy --format-version 0.0.2 jpack experimental policy canonicalize jpack experimental policy digest jpack experimental policy validate jpack experimental policy check --materials
The pack argument and --pack-id are mutually exclusive: one pack, one source, and supplying both or neither is an invocation error rather than a precedence rule. --pack-id honors --config and JPACK_CONFIG like every other command that reads a configuration.
The namespace is jpack spec, not jpack jps. JPS remains the name of the specification and the prefix of its provisional diagnostic codes.
The mcp command serves the same offline operations to a Model Context Protocol client over stdio, so an agent can validate documents as a tool call; see docs/mcp-clients.md for per-client setup and docs/agent-testing.md for the agent-driven testing protocol.
Download the archive for your operating system and architecture from GitHub Releases. Each archive includes the jpack binary, README, the CONFORMANCE.md claim the source it was built from carries, Apache-2.0 license, attribution notice, and third-party notices.
Asset names follow this pattern:
judgment-pack_<version>_<os>_<arch>.tar.gz
judgment-pack_ _windows_ .zip
For example, release v0.1.0 uses judgment-pack_0.1.0_linux_amd64.tar.gz. Linux and macOS users can extract an archive and install the binary into a user-owned directory already on PATH:
tar -xzf judgment-pack_0.1.0_linux_amd64.tar.gz
install -m 0755 jpack "$HOME/.local/bin/jpack" jpack version
On Windows, expand the .zip, move jpack.exe into a directory on your user PATH, and run:
jpack version
Verify the archive before extracting it. On Linux:
grep ' judgment-pack_0.1.0_linux_amd64.tar.gz$' checksums.txt | sha256sum --check
On macOS:
grep ' judgment-pack_0.1.0_darwin_arm64.tar.gz$' checksums.txt | shasum -a 256 --check
On Windows PowerShell:
(Get-FileHash .\judgment-pack_0.1.0_windows_amd64.zip -Algorithm SHA256).Hash
Select-String -Path .\checksums.txt -Pattern ' judgment-pack_0.1.0_windows_amd64.zip$'
The two Windows hashes must match. Release archives also carry GitHub build-provenance attestations, which a current GitHub CLI can verify:
gh attestation verify judgment-pack_0.1.0_linux_amd64.tar.gz --repo Judgment-Pack/judgment-pack-runtime
Packages for Homebrew, Scoop, apt, and go install are not published yet. In particular, source installation with go install does not receive the release linker metadata, so use a release archive when you need an accurately reported runtime version.
With jpack on your PATH, this is the whole loop: a pack, a facts document, and a disposition. Save a pack that approves an expense unless its amount is over 5000:
cat > pack.json <<'EOF'
{ "specVersion": "0.2.0-draft", "id": "https://example.invalid/judgment-packs/expense-approval", "version": "0.1.0", "title": "Expense approval", "decision": { "intent": "Approve ordinary expenses without review.", "question": "May this expense be approved?" }, "outcomes": [ { "id": "approve", "label": "Approve" }, { "id": "decline", "label": "Decline" } ], "rules": [ { "id": "over-limit",