# ZTL Judge (remote · api.ztljudge.com)

Zero-trust logic judge: ZFL claims, algebra derivation steps, sets defined by a property.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.ztljudge.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/inventor1975-ztl-judge/api-2.md), [page](https://verifymcp.io/servers/inventor1975-ztl-judge/api-2)

## Channel facts

- Endpoint: `https://api.ztljudge.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1106 tokens (~184/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ZTL Judge MCP server?

ZTL Judge is a hosted endpoint at https://api.ztljudge.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http inventor1975-ztl-judge 'https://api.ztljudge.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "inventor1975-ztl-judge": {
      "url": "https://api.ztljudge.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "inventor1975-ztl-judge": {
      "type": "http",
      "url": "https://api.ztljudge.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.inventor1975-ztl-judge]
url = "https://api.ztljudge.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inventor1975-ztl-judge": {
      "type": "remote",
      "url": "https://api.ztljudge.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add inventor1975-ztl-judge --url 'https://api.ztljudge.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  inventor1975-ztl-judge:
    url: "https://api.ztljudge.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "inventor1975-ztl-judge": {
      "Transport": "http",
      "Url": "https://api.ztljudge.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add inventor1975-ztl-judge -t streamable-http -u 'https://api.ztljudge.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "inventor1975-ztl-judge": {
      "type": "http",
      "url": "https://api.ztljudge.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-05 (score 64, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 519 → 1106
- [functional regression] Schema quality: 519 → 1054
- [functional] Server version: eafe892 → d0287ad
- [functional] Server version: eaf5659 → eafe892
- [functional] New tool “judge_naive”
- [functional] New tool “checker_examples”
- [functional] New tool “check_steps”

### 2026-11-03 (score 64, +1)

- [functional] Server version: 2a723b2 → eaf5659

### 2026-11-01 (score 63, +1)

- [functional] Server version: 5886c32 → 2a723b2

### 2026-10-31 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 62)

First indexed and scored.

## MCP tools (6)

### `language` (~27 tokens)

The ZFL language: the columns of a row, the document fields, their meaning and rules.

### `examples` (~22 tokens)

Worked examples: questions already written as ZFL documents, ready to judge.

### `judge` (~226 tokens)

Judge a ZFL document with ZTL, a zero-trust logic: three values, two-valued connectives.

    Args:
        document: The ZFL document, as an object or as JSON text:
            {"rows": [{"name": ..., "means": ..., "status": ..., "ground": ...}], "claim": ...}.

    Returns:
        The verdict with its disposition and grade, the receipt, the
        instruments that applied, the issues found, and what the core read.
        Read the verdict WITH its disposition: T EARNED = established; F REFUTED = false; F OPEN or Z OPEN = NOT ESTABLISHED, it could still turn either way (do not report it as false) — `why` and `unverified` say what to check; ON CREDIT = holds only on an unverified ground. A compound claim gets T or F; a claim that is a single name gets that name's own value, Z while unverified.
        The full report is returned whatever `ask` says.

Input parameters:

- `document` (required)

### `check_steps` (~222 tokens)

Check an algebra derivation step by step: does each step keep exactly the same solutions?

    Args:
        request: {"equations": ["x^2 = x", "x = 1"], "var": "x", "domain": [lo, hi] or null,
            "domain_verified": true}. Each equation is the next step; one unknown; + - * / ^ with whole powers.

    Returns:
        The chain's verdict (its weakest step) and each step's: EARNED = same solutions on the domain;
        ON CREDIT = the same, on an unverified domain; REFUTED = a solution is lost (e.g. cancelling a factor that
        can be 0) or gained (e.g. clearing a denominator where the original was undefined), with the witness and
        the cause; E = the step divides by an expression that is 0 for every value. A request above the public
        limits is refused with the reason (ok: false, refused).

Input parameters:

- `request` (required)

### `judge_naive` (~289 tokens)

Judge sets defined by a property, self-reference allowed (Russell's set, a web of trust, a policy rule).

    Args:
        universe: {"sets": {name: {"list": [...]} | {"data": {name: "T"|"F"|"Z"}} | {"abs": formula}},
            "claims": [formula, ...]}. Formulas: ["in", a, S], ["not", f], ["and"|"or"|"imp"|"iff", f, g],
            ["all"|"ex", "y", f], ["eq", S, T]; an abs set's own variable is "x". Every name is also an object.

    Returns:
        Per set: the members and non-members the definitions ground, and a passport for each membership they
        leave undecided — PARADOX (no stipulation can repair it), UNDERDETERMINED (consistent; a decision is
        owed), INTRINSIC, INPUT (verify the given cell), DOWNSTREAM (inherits a quarantine). Per claim: EARNED /
        REFUTED / EARNED IF STABLE / REFUTED IF STABLE / OPEN, the cells it rests on with their passports, and for
        a universal claim the instances left undecided. Oversized requests are refused with the reason.

Input parameters:

- `universe` (required)

### `checker_examples` (~24 tokens)

Ready requests for check_steps and judge_naive (the kernels' own examples).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/inventor1975-ztl-judge/api-2#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 62
- 2026-10-30: 62

## Common questions

### What is the ZTL Judge MCP server?

ZTL Judge is an MCP server listed in the public MCP registry as io.github.inventor1975/ztl-judge. Zero-trust logic judge: ZFL claims, algebra derivation steps, sets defined by a property. This page covers its hosted endpoint (https://api.ztljudge.com/mcp).

### Is the ZTL Judge MCP server safe to use?

ZTL Judge scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ZTL Judge MCP server expose?

ZTL Judge exposes 6 tools: language, examples, judge, check_steps, judge_naive, checker_examples. Their descriptions and schemas cost roughly 810 tokens of context every time the server is loaded.

### Does the ZTL Judge MCP server require authentication?

No. We connected to ZTL Judge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ZTL Judge MCP server still maintained?

ZTL Judge is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.ztljudge.com/mcp
- Repository: https://github.com/inventor1975/ztlstudio
- Website: https://studio.ztljudge.com/
- Changelog RSS feed: https://verifymcp.io/servers/inventor1975-ztl-judge/api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/inventor1975-ztl-judge/api-2.json
- HTML version of this page: https://verifymcp.io/servers/inventor1975-ztl-judge/api-2