ZTL Judge

Zero-trust logic judge: your AI writes a claim as a ZFL table, the ZTL core judges it.

Should I use this

Quality & Safety

B
Description quality
90%
Schema completeness
40%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'language' description lacks action verbin language

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~429Tokens (tool definitions)
~528 BTypical response size
Minimal attention impact (0.34% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "ztl-judge": {
      "url": "https://api.vitalyreznik.com/mcp"
    }
  }
}

Remote endpoints

https://api.vitalyreznik.com/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪language

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

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "languageArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "languageDictOutput"
}
⚪examples

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

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "examplesArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "examplesDictOutput"
}
🟢judge(document)

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 Schema

{
  "type": "object",
  "properties": {
    "document": {
      "anyOf": [
        {
          "additionalProperties": true,
          "type": "object"
        },
        {
          "type": "string"
        }
      ],
      "title": "Document"
    }
  },
  "required": [
    "document"
  ],
  "title": "judgeArguments"
}

Output Schema

{
  "type": "object",
  "additionalProperties": true,
  "title": "judgeDictOutput"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools