io.github.shoggi211/jsonaut
REMOTE · JSONAUT.JSONAUT-SHAURYA.WORKERS.DEV · SCANNED AUG 3
Repair malformed JSON from LLM/agent output; optional JSON Schema coercion. Free + x402 paid.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 463 tokens (~115/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · jsonaut.jsonaut-shaurya.workers.dev
claude mcp add --transport http shoggi211-jsonaut https://jsonaut.jsonaut-shaurya.workers.dev/mcp
[mcp_servers.shoggi211-jsonaut] url = "https://jsonaut.jsonaut-shaurya.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shoggi211-jsonaut": {
"type": "remote",
"url": "https://jsonaut.jsonaut-shaurya.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add shoggi211-jsonaut --url https://jsonaut.jsonaut-shaurya.workers.dev/mcp --transport streamable-http
mcp_servers:
shoggi211-jsonaut:
url: "https://jsonaut.jsonaut-shaurya.workers.dev/mcp" {
"mcpServers": {
"shoggi211-jsonaut": {
"type": "http",
"url": "https://jsonaut.jsonaut-shaurya.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://jsonaut.jsonaut-shaurya.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jsonaut-shaurya.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Jul 2026 | 30 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | c987d1332e4bbcda130cbdd9e5eeef96 |
| SANs: jsonaut-shaurya.workers.dev, *.jsonaut-shaurya.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of jsonaut.jsonaut-shaurya.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jsonaut.jsonaut-shaurya.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://jsonaut.jsonaut-shaurya.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
extract_json ~129
Extract JSON embedded in arbitrary text — LLM prose, chat messages, logs, emails — then repair and validate it. Deterministic extraction is free. If no JSON can be located and allow_llm_fallback is true, a paid LLM extracts structured data from the text (requires x402 payment; charged only on success). Pass a JSON Schema to shape the output.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_llm_fallback | boolean | — | Permit the paid LLM extraction tier |
| input | string | yes | Text that may contain JSON |
| schema | object | — | Optional JSON Schema the output must conform to |
No output schema declared.
No examples provided.
infer_schema ~104
Infer a JSON Schema (draft 2020-12) from an example JSON value. Free and deterministic. Set as_samples=true when the input is an array of example objects of the same shape to merge them into one schema. Turns sample agent/tool output into a reusable schema.
| Name | Type | Req | Description |
|---|---|---|---|
| as_samples | boolean | — | Treat a top-level array as multiple samples of one shape |
| input | string | yes | A JSON value (or array of samples) to infer a schema from |
No output schema declared.
No examples provided.
repair_json ~124
Repair malformed JSON (trailing commas, single quotes, truncation, markdown fences, comments, python literals) and optionally validate/coerce it against a JSON Schema. Deterministic repair is free. If it fails and allow_llm_fallback is true, a paid LLM repair is attempted (requires x402 payment; charged only on success).
| Name | Type | Req | Description |
|---|---|---|---|
| allow_llm_fallback | boolean | — | Permit the paid LLM repair tier |
| input | string | yes | The possibly-malformed JSON text |
| schema | object | — | Optional JSON Schema the output must conform to |
No output schema declared.
No examples provided.
validate_json ~52
Validate a JSON string against a JSON Schema. Free. Returns validity and a list of violations.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The JSON text to validate |
| schema | object | yes | The JSON Schema to validate against |
No output schema declared.
No examples provided.