Jig
REMOTE · JIG.CLAWHARD.COM
Check JSON against a JSON Schema with exact paths, and schemas for OpenAI, Claude and Gemini strict.
Available components
Last scanned (17 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1358 tokens (~339/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 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.
- 19 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 18 Nov 26 66
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 21 Nov 2026 · Probed https://jig.clawhard.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=clawhard.com | CN=WE1,O=Google Trust Services,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | a3c8286b411ef3ca0e202f677da7dcb4 |
| SANs: clawhard.com, jig.clawhard.com, *.jig.clawhard.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jig.clawhard.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| clawhard.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jig.clawhard.com/mcp | Verified | 200 | |
| http (plaintext) | http://jig.clawhard.com/mcp | Served over HTTP | 200 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
jig_check_schema Check a JSON Schema, and whether OpenAI, Claude and Gemini strict modes accept it ~573
Use when the user asks whether a JSON Schema is valid, or whether it will work with OpenAI Structured Outputs or function calling with strict: true, Claude structured outputs or strict tool use, or Gemini structured output (response_json_schema), or is writing a tool or function schema, an MCP inputSchema, a response_format, or a schema exported from Zod or Pydantic (signals: "Invalid schema for response_format", "strict mode error", "Claude returns 400 for my schema", "will this schema work with OpenAI", "Gemini ignores maxLength", "additionalProperties false", "all fields must be required"). First checks the schema against its draft: type names like "int", "required": true on a property, misspelt keywords, unresolvable $ref, invalid regex, impossible ranges. Then checks each provider's documented rules: OpenAI (every property in required, additionalProperties false on every object, root an object and not anyOf, no allOf/not/if, at most 5000 properties, 10 levels, 1000 enum values, documented formats only), Claude (additionalProperties false, no minimum/maximum/multipleOf/minLength/maxLength, minItems only 0 or 1, no recursion, at most 24 optional and 16 union-typed parameters per request, regex without lookarounds or backreferences), Gemini (minLength, maxLength, uniqueItems, minProperties and similar are dropped without an error). Returns per provider a verdict (ok, warnings, fails), each issue with its JSON Pointer path, rule, fix and the provider's doc URL, plus a converted copy the provider accepts (optional fields made required and nullable for OpenAI, unsupported constraints moved into descriptions the way the official SDK helpers do), and counts (properties, depth, optional and union-typed parameters). Example: {"schema":{"type":"object","properties":{"city":{"type":"string","maxLength":40},"days":{"type":"integer","minimum":1}},"required":["city"]},"providers":["openai","anthropic"]}. Rules are from each provider's docs, checked 2026-11-18; providers can…
| Name | Type | Req | Description |
|---|---|---|---|
| draft | string | – | Force a draft: 2020-12, 2019-09, 7, 6 or 4. Default: from $schema, else 2020-12. |
| include_converted | boolean | – | Include a converted copy for each provider that does not accept the schema as is. Default true. |
| providers | array | – | Which providers to check. Default: all three. |
| schema | object | yes | The JSON Schema to check, as a JSON object (not a string). |
No output schema declared.
No examples provided.
jig_validate_json Validate JSON against a JSON Schema (every error with its path) ~572
Use when the user asks whether some JSON matches a JSON Schema, or when JSON from a model reply, structured output, tool call, API response or file has to be checked against its schema before it is used or stored (signals: "validate this JSON", "does this match the schema", "which field is wrong", "the model returned bad JSON", "check the tool-call arguments", "why does my parser reject this"). Validates a JSON value (data), or raw model text (json_text: a ```json fence or prose around one JSON value is stripped; a syntax error comes back with line and column), against JSON Schema draft 2020-12, 2019-09, 07, 06 or 04, including $ref/$defs, anyOf/oneOf/allOf, if/then/else, unevaluatedProperties, patterns and formats (email, date-time, date, time, uuid, uri, hostname, ipv4, ipv6, duration). Returns valid true/false, every problem with its JSON Pointer path, keyword, expected and got values, and retry_message: a ready-to-send list of fixes for the model that produced the JSON. Example: {"schema":{"type":"object","properties":{"price":{"type":"number"}},"required":["price","sku"]},"data":{"price":"12.50"}}. Gives the expected answer on 6,018 of 6,227 official JSON-Schema-Test-Suite cases (ajv 8: 5,981); most misses are external $ref URLs, which are not fetched, $dynamicRef, and the idn-email, idn-hostname and iri formats, which are not checked. Not for repairing broken JSON syntax or for checking whether a schema works with OpenAI, Claude or Gemini (jig_check_schema).
| Name | Type | Req | Description |
|---|---|---|---|
| check_formats | boolean | – | Check "format" (email, date-time, uuid, uri, ...). Default true. |
| data | – | – | The JSON value to check: object, array, string, number, boolean or null. Use this or json_text. |
| draft | string | – | Force a draft: 2020-12, 2019-09, 7, 6 or 4. Default: from $schema, else 2020-12. |
| json_text | string | – | Raw text that should contain one JSON value, for example a model reply. Code fences and text around the JSON are stripped. Use this or data. |
| max_errors | integer | – | Most errors to list (default 50). error_count is always the full count. |
| schema | object | yes | The JSON Schema, as a JSON object (not a string). $schema picks the draft; default 2020-12. |
No output schema declared.
No examples provided.
How do I install the Jig MCP server?
Jig is a hosted endpoint at https://jig.clawhard.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jig.clawhard.com
claude mcp add --transport http com-clawhard-jig 'https://jig.clawhard.com/mcp'
What is the Jig MCP server?
Jig is an MCP server listed in the public MCP registry as com.clawhard/jig. Check JSON against a JSON Schema with exact paths, and schemas for OpenAI, Claude and Gemini strict. This page covers its hosted endpoint (https://jig.clawhard.com/mcp).
Is the Jig MCP server safe to use?
Jig scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jig MCP server expose?
Jig exposes 2 tools: jig_validate_json, jig_check_schema. Their descriptions and schemas cost roughly 1,145 tokens of context every time the server is loaded.
Does the Jig MCP server require authentication?
No. We connected to Jig without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jig MCP server still maintained?
Jig is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Jig MCP server?
VerifyMCP ran 14 checks on Jig, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.