Skip to content

Jig MCP server

com.clawhard/jigclawhard.comstreamable-httpv1.0.0Scanned

Check JSON against a JSON Schema with exact paths, and schemas for OpenAI, Claude and Gemini strict.

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Jig MCP server can do

The Jig MCP server is published by clawhard.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: jig_check_schema), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • jig_check_schemaUse 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 st…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,073 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...rs can change them, and very large schemas can still hit unpublished size limits."

      What this check looks for
    Description, as the server wrote it
    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 change them, and very large schemas can still hit unpublished size limits.

    Annotations the server declares

    • title: Check a JSON Schema, and whether OpenAI, Claude and Gemini strict modes accept it
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • jig_validate_jsonUse 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 sc…No findings

    Why it is in this group

    • The name "jig_validate_json" says "validate": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Validate JSON against a JSON Schema (every error with its path)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:18 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://jig.clawhard.com/mcp: tools/list returned 2 tools to an anonymous client, including jig_check_schema (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,073 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...rs can change them, and very large schemas can still hit unpublished size limits."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http jig https://jig.clawhard.com/mcp
claude mcp add --transport http jig https://jig.clawhard.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jig__jig_validate_json"
    ],
    "ask": [
      "mcp__jig__jig_check_schema"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jig. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.clawhard/jig/verify?hash=efb7f339b73f0c85e3fa5e58c5e19c4e42947a9ffe881507fad1e90b0e486382" | jq -e '.changed == false'

Pinned hash efb7f339b73f, from Nov 18, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.clawhard/jig/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.clawhard/jig
[![Anlyon Radar](https://radar.anlyon.com/badge/com.clawhard/jig.svg)](https://radar.anlyon.com/servers/com.clawhard/jig)

Source: MCP Registry. Synced Nov 18, 2026, 15:17 UTC.

Jig MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Jig MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Jig MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Jig MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Jig MCP server have?

2 tools: 1 write, 1 read. jig_check_schema and jig_validate_json.

Does the Jig MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Jig MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Jig MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.