MCP tool reference · #561 of 563 by publishers
validate_json
Exposed by 9 servers from 8 publishers, read from the live servers by the Serverdex check; 33.3% of them take a input parameter; the most-starred is Developer Utilities & Validators (Tanod) (1 stars).
validate_json(input: string, …)Parameters
share = % of the 9 servers whose schema has it · required = % of those that mark it required| Parameter | Type | Share | Required | Usual description |
|---|---|---|---|---|
| input | string | 33.3% | 100% | The JSON text to validate |
| json | string | 22.2% | 100% | HyperCodeMotion JSON object or JSON-encoded string to validate. |
| schema | object | 22.2% | 100% | JSON Schema (draft from $schema; default 2020-12). Remote $ref documents are refused, never fetched. |
| composition | object | 11.1% | 0% | Optional original composition used to resolve patch references and timings. |
| content | string | 11.1% | 100% | The complete file content as text. Parse errors are reported too. |
| instance | object | array | string | number | integ | 11.1% | 100% | Any JSON value to validate. |
| json_str | string | 11.1% | 100% | JSON string to validate |
| type | string | 11.1% | 100% | Document type. A canonical name ("behavior/blocks/blocks"), a short form ("behavior/blocks") or a file path ("BP/blocks/ruby.json") are all accepted. The list o |
| version | string | 11.1% | 0% | Game version under data/, e.g. 1.26.40 or 1.26.40.5. Defaults to the newest available version. Marketing numbers (26.40) are rejected. |
Source: the input schema each server returns for validate_json, aggregated over the 9 index-tier servers; type and description are the values most servers use. Rebuilt every 6 hours.
Servers with validate_json
9 of 9 · 8 publishers · 9 answering live · most-starred first, 3 per publisher| # | Server | Publisher | Category | ★ | Live | How it describes validate_json |
|---|---|---|---|---|---|---|
| 1 | Developer Utilities & Validators (Tanod)tanod-labs · Crypto & Web3 | tanod-labs | Crypto & Web3 | 1 | yes | utilpeek: Validate JSON against a JSON Schema. To pull JSON out of prose use extract_json_with_schema; to convert formats use convert_data. Returns whether a JSON value is valid against a JSON Schema (draft from $schema, default 2020-12; 2019-09, 7, 6, 4 and 3 recognised), with up to 100 errors (instance path, schema path, message, validator) and the formats checked. Remote $ref documents are refu |
| 2 | HyperCodeMotion MCPjasp402 · Developer Tools | jasp402 | Developer Tools | 1 | yes | Check a composition (layers), design (elements), or improvement patch (add/change/remove/sfx) and return actionable errors and warnings. Rejects measurable text that cannot fit the canvas safe area, text that crosses the canvas, and line-height below 1. Warns when a code layer or component declares a name the engine already provides (RESERVED_NAME_DECLARED). This is not proof of a successful rende |
| 3 | Jsonautshoggi211 · AI & Agents | shoggi211 | AI & Agents | 1 | yes | Validate a JSON string against a JSON Schema. Free. Returns validity and a list of violations. |
| 4 | TinyFntinyfn-io · Other | tinyfn-io | Other | 1 | yes | Validate JSON syntax. |
| 5 | Jsonpipeworx-io · Other | pipeworx-io | Other | — | yes | Validate a JSON string (keyless, offline). Returns whether it is valid and, if not, the error message and the character position. |
| 6 | PrepLayer.aimaximusboomerus-afk · Other | maximusboomerus-afk | Other | — | yes | Deterministic JSON-Schema subset validator. Catches malformed JSON before it breaks a pipeline. Supports: type, required, properties, items, minLength, maxLength, pattern, enum, minimum, maximum, additionalProperties. No external dependencies. $0.003 USDC per successful call (x402, client-paid); failed calls are not charged. |
| 7 | CodeCrafttanertalas · Games & Sports | tanertalas | Games & Sports | — | yes | Validates a behavior or resource pack JSON file against the official schema and returns the JSON pointer, the violated rule and a readable message for every error. Unexpected property names and the valid enum values are included in the message. Run every JSON file you produce through this before handing it to the user. |
| 8 | Payload Validatorbwalvoord · Crypto & Web3 | bwalvoord | Crypto & Web3 | — | yes | Validates a JSON document and reports every problem with an exact line and column. Use this whenever you need to know why a JSON payload is failing, or to check a JSON document you or a user produced before sending it somewhere that will reject it. Do not do this by reading the JSON yourself. Three of the findings are invisible to inspection and to JSON.parse alike: (1) Duplicate keys. `{"port": |
| 9 | Project Gumballbwalvoord · Finance | bwalvoord | Finance | — | yes | Validates a JSON document and reports every problem in one pass with a 1-based line and column, a stable rule code and a fix hint. Reports the three things JSON.parse cannot: duplicate keys (accepted by every parser, which then disagree about which value wins), integer precision loss past 2^53-1 proved with exact BigInt arithmetic (any 64-bit ID is in the lossy range), and unpaired surrogates that |
Stars from GitHub as stored in the Serverdex index (re-read every 7 days per server); live = answered the last daily check of its hosted endpoint.