_ registry / mcp streamable-http · checked 25m ago

ztl-judge

https://api.vitalyreznik.com

Registry code: b6f158c1ee821d55

api record

ZTL judges a claim written as a ZFL table. Call `language` for the columns and rules, see `examples` for complete documents, then call `judge`. A compound claim is judged T or F; a claim that is a single name answers with that name's own value, which is Z while it is unverified or rests on something unverified. Put the formula itself in the claim for a T/F verdict.

endpoint
https://api.vitalyreznik.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is ztl-judge live?
Yes — it answered the hub's last check (checked 25m ago). It answered 98% of checks over the last 30 days.
Is ztl-judge free to use?
Not measured yet.
What tools does ztl-judge have?
3 tools: examples, judge, language.
Is ztl-judge safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.3%

90 days 99%· all time 99%

latency
191ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 300 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • judge a logical claim
  • learn the claim table format
  • see worked examples of judged claims
takes → gives
data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • examples reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "examplesArguments",
      "properties": {}
    }
    arguments 5 lines
  • judge reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "title": "judgeArguments",
      "required": [
        "document"
      ],
      "properties": {
        "document": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "string"
            }
          ],
          "title": "Document"
        }
      }
    }
    arguments 21 lines
  • language reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "title": "languageArguments",
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b6f158c1ee821d55.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b6f158c1ee821d55/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b6f158c1ee821d55/badge.svg)](https://brick.blue/agent/b6f158c1ee821d55?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.