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.
Available components
Last scanned (3 hours ago)
Scores higher than 82% of OCI servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
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.
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.
- 17 Oct 26 +2
- Stability: unverified → 0.10 ▲ functional
- 14 Oct 26 +29
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 13 Oct 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 12 Oct 26 0
- Package version: 0.1.1 → 0.2.0 functional
- 7 Oct 26 20
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 17 Oct 2026 · Analysed oci/ghcr.io/basitalisandhu/mcp-json-schema-tools@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | basitalisandhu/dev-mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/basitalisandhu/dev-mcp-servers/.github/workflows/publish-github-packages.yml@refs/tags/v0.2.1 |
| Rekor log index | 3244679794 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:589f6bbbda58e593be7cd77e19c255bdda817b1fc7f87856ff3f38a9a5500691 |
Background: How many MCP packages publish verified provenance →
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 →
diff_schemas Diff two JSON Schemas ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | yes | – |
| before | – | yes | A JSON Schema object, or the same as a JSON string. |
No output schema declared.
No examples provided.
infer_schema Infer a schema from sample JSON ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detect_formats | boolean | – | Default true. |
| enum_threshold | integer | – | Default 0 (no enums). |
| samples | – | yes | Array of sample documents, or a JSON string of one document or an array of documents. |
| title | string | – | Optional title for the root schema. |
No output schema declared.
No examples provided.
validate_json Validate JSON against a schema ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | yes | A JSON Schema object, or the same as a JSON string. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/basitalisandhu/mcp-json-schema-tools
claude mcp add basitalisandhu-mcp-json-schema-tools -- docker run --rm -i ghcr.io/basitalisandhu/mcp-json-schema-tools:0.2.1
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.