Search / io.github.inventor1975/ztl-judge
protogridR0· no sign-inZero-trust logic judge: your AI writes a claim as a ZFL table, the ZTL core judges it.
v1.0.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"ztl-judge": {
"type": "http",
"url": "https://api.vitalyreznik.com/mcp"
}
}
}claude mcp add --transport http ztl-judge https://api.vitalyreznik.com/mcp[mcp_servers.ztl-judge]
url = "https://api.vitalyreznik.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ztl-judge": {
"type": "remote",
"url": "https://api.vitalyreznik.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"ztl-judge": {
"type": "http",
"url": "https://api.vitalyreznik.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=ztl-judge&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXBpLnZpdGFseXJlem5pay5jb20vbWNwIn0%3D"
}{
"servers": {
"ztl-judge": {
"type": "http",
"url": "https://api.vitalyreznik.com/mcp"
}
}
}{
"mcpServers": {
"ztl-judge": {
"httpUrl": "https://api.vitalyreznik.com/mcp"
}
}
}extensions:
"ztl-judge":
enabled: true
name: "ztl-judge"
type: streamable_http
uri: "https://api.vitalyreznik.com/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky onestools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: language (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); examples (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); judge (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)tools.token_costabout 343 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes1 tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagejudgechangeddescriptionJudge a ZFL document with ZTL, a two-valued zero-trust logic. Args: document: The ZFL document, as an object or as JSON text: {"rows": [{"name": ..., "means": ..., "status": ..., "ground": ...}], "claim": ...}. Returns: The verdict (T or F) with its disposition and grade, the receipt, the instruments that applied, the issues found, and what the core read.
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.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-100% +updated-20d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://api.vitalyreznik.com/mcp streamable-http | none | yes | 100% | 440 ms | 2026-07-28 | 2026-10-19 |
examples | Worked examples: questions already written as ZFL documents, ready to judge. |
judge | 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. |
language | The ZFL language: the columns of a row, the document fields, their meaning and rules. |
Schemas: list_tools.
{
"name": "io.github.inventor1975/ztl-judge",
"title": "ZTL Judge",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://api.vitalyreznik.com/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"repository": {
"url": "https://github.com/inventor1975/ztlstudio",
"source": "github"
},
"websiteUrl": "https://ztl.vitalyreznik.com",
"description": "Zero-trust logic judge: your AI writes a claim as a ZFL table, the ZTL core judges it."
}