is-json-safe

shallow

io.github.why-see/agent-tools-mcp · Verify this server

Parse JSON with bounded depth, key counts and input size. Use to screen JSON without execution; use optimize-dataset for JSONL or CSV cleanup. Returns {ok, issues, bytes, depth, keys, value?}; parsed value is included only when valid.

100.0/100

1 trials · measured 1 day ago

is-json-safe scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against io.github.why-see/agent-tools-mcp, measured 20 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-20100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: is-json-safe
[![Vouch score](https://vouch.tools/api/tools/93f68c57-95be-47d8-83f2-f6140f0242db/badge.svg)](https://vouch.tools/tools/93f68c57-95be-47d8-83f2-f6140f0242db)
is-json-safe — Vouch