Robin Saige we check the tools AI agents call

JSONlify

io.github.irmasemma/jsonlify

Validate and convert JSONL fine-tuning data across 11 AI providers. 13 tools.

— the operator's own registry description reported

Publisher io.github.irmasemma · first seen 2026-08-12 · endpoint https://www.jsonlify.com/api/mcp

warn
verdict
alive-toolless
cluster
ok
answers
tools served

Dependency rating derived

warn
warn — alive, no tools · computational ○ · V n/a
warn — because answers ●, no confirmed drift in 2 probes ●; not yet checked: harness, truth (0 runs)

Cluster alive-toolless · distinctiveness 0.124 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_no_tools
latency147 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
capabilities2
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_53a4cad8c93fff02cf066930 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive, no tools — 2 probes ●evidence ↓
Q2What is it?computational ○ evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?truth not yet run · no drift ●evidence ↓
Q5What company does it keep?alive-toolless · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
computational1deterministic transformsself-checkable by re-computation and known-answer tests

Tools last seen observed

no tool inventory served

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
0.1.0
server version mcp-typescript server on vercel

Capabilities: resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:37Zok2001472025-06-18
2026-08-12T05:34:50Zok2002452025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.irmasemma/jsonlify.svg)](https://robinsaige.com/s/io.github.irmasemma/jsonlify)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview