# JSON Schema Tools (oci · ghcr.io/basitalisandhu/mcp-json-schema-tools)

Validate JSON against a schema with Ajv, infer a schema from samples and diff two schemas.

- Trust score: 51/100 (low)
- Change this week: +31
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- oci · `ghcr.io/basitalisandhu/mcp-json-schema-tools`: 51/100 (this document), [markdown](https://verifymcp.io/servers/basitalisandhu-mcp-json-schema-tools/ghcr-io-basitalisandhu-mcp-json-schema-tools.md), [page](https://verifymcp.io/servers/basitalisandhu-mcp-json-schema-tools/ghcr-io-basitalisandhu-mcp-json-schema-tools)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/basitalisandhu/mcp-json-schema-tools`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 651 tokens (~217/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the JSON Schema Tools MCP server?

JSON Schema Tools runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add basitalisandhu-mcp-json-schema-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1
```

### Cursor

```json
{
  "mcpServers": {
    "basitalisandhu-mcp-json-schema-tools": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "basitalisandhu-mcp-json-schema-tools": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add basitalisandhu-mcp-json-schema-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "basitalisandhu-mcp-json-schema-tools": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  basitalisandhu-mcp-json-schema-tools:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1"]
```

### Netclaw

```json
{
  "McpServers": {
    "basitalisandhu-mcp-json-schema-tools": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "basitalisandhu-mcp-json-schema-tools": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 51, +2)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-14 (score 49, +29)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 89
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good

### 2026-10-13 (score 20, 0)

- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-12 (score 20, 0)

- [functional] Package version: 0.1.1 → 0.2.0

### 2026-10-07 (score 20)

First indexed and scored.

## MCP tools (3)

### `validate_json` (~176 tokens)

Validate JSON against a schema

Validate a JSON document against a JSON Schema. The draft is read from $schema (draft-07 when absent) unless draft is given. Formats such as email, uri, date-time and uuid are checked. Returns valid, the draft used, the total error count and up to 200 errors with instance path (JSON Pointer), schema path, keyword, message and params. Unknown keywords are ignored (Ajv strict mode is off). Draft-04 and draft-06 schemas are rejected.

Input parameters:

- `data`: The document to validate: any JSON value, or a JSON string (strings are parsed; to validate a literal string, pass it JSON-encoded, for example "\"text\"").
- `draft` (string): Force a draft. Default auto.
- `schema` (required): A JSON Schema object, or the same as a JSON string.

### `infer_schema` (~194 tokens)

Infer a schema from sample JSON

Build a JSON Schema (draft 2020-12) that describes the given samples: a single document or an array of documents (each sample is one document; wrap one array document as [[...]]). Properties present in every sample become required; types seen across samples are unioned; nested objects and array items are inferred recursively; strings that all look like a date-time, date, time, email, uuid, uri or ipv4 get a format. With enum_threshold above 0, string properties with few distinct values across at least three samples become enums. The result is a starting point to edit, not a complete contract.

Input parameters:

- `detect_formats` (boolean): Default true.
- `enum_threshold` (integer): Default 0 (no enums).
- `samples` (required): Array of sample documents, or a JSON string of one document or an array of documents.
- `title` (string): Optional title for the root schema.

### `diff_schemas` (~153 tokens)

Diff two JSON Schemas

Compare two JSON Schemas structurally and list every change with its path, the before and after values, and an impact: breaking (a document valid under the old schema can now be rejected: required added, property removed with additionalProperties false, type narrowed, enum value removed, tighter min/max), compatible (every old document stays valid), or review (composition keywords, changed patterns or formats). Walks properties, required, additionalProperties, items, enum, numeric and length bounds, pattern, format, $ref and annotations. oneOf/anyOf/allOf and conditionals are compared as a whole.

Input parameters:

- `after` (required)
- `before` (required): A JSON Schema object, or the same as a JSON string.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/basitalisandhu-mcp-json-schema-tools/ghcr-io-basitalisandhu-mcp-json-schema-tools#diagnostics

## Score history

- 2026-10-17: 51
- 2026-10-16: 49
- 2026-10-15: 49
- 2026-10-14: 49
- 2026-10-13: 20
- 2026-10-12: 20
- 2026-10-07: 20

## Common questions

### What is the JSON Schema Tools MCP server?

JSON Schema Tools is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-json-schema-tools. Validate JSON against a schema with Ajv, infer a schema from samples and diff two schemas. This page covers its container image (ghcr.io/basitalisandhu/mcp-json-schema-tools).

### Is the JSON Schema Tools MCP server safe to use?

JSON Schema Tools scores 51 out of 100 on VerifyMCP. Its build provenance is signed and verified. 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 JSON Schema Tools MCP server expose?

JSON Schema Tools exposes 3 tools: validate_json, infer_schema, diff_schemas. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.

### Is the JSON Schema Tools MCP server still maintained?

JSON Schema Tools is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the JSON Schema Tools MCP server under?

JSON Schema Tools declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/basitalisandhu/mcp-json-schema-tools
- Repository: https://github.com/basitalisandhu/dev-mcp-servers
- Website: https://basitalisandhu.github.io/dev-mcp-servers/
- Changelog RSS feed: https://verifymcp.io/servers/basitalisandhu-mcp-json-schema-tools/ghcr-io-basitalisandhu-mcp-json-schema-tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/basitalisandhu-mcp-json-schema-tools/ghcr-io-basitalisandhu-mcp-json-schema-tools.json
- HTML version of this page: https://verifymcp.io/servers/basitalisandhu-mcp-json-schema-tools/ghcr-io-basitalisandhu-mcp-json-schema-tools