
JSON Validator API
Validate JSON payloads and JSON Schema from the agent before you merge config, webhooks, or API contracts.
Overview
io.github.Br0ski777/json-validator is a MCP server for the Ship phase that validates JSON syntax, checks JSON Schema, and reports structure stats via remote SSE with x402.
What is this MCP server?
- JSON syntax validation with clear pass or fail
- JSON Schema checking against your declared schema
- Structure statistics for depth, keys, and size insight
- Remote MCP SSE at json-validator.api.klymax402.com
- x402 micropayment; server version 1.1.0
- MCP server version 1.1.0
- 3 validation capabilities: syntax, JSON Schema, structure stats
- 1 remote SSE endpoint: json-validator.api.klymax402.com/mcp
What problem does it solve?
Agent-generated or copied JSON breaks in staging because syntax errors and schema drift are hard to spot inline during fast iteration.
Who is it for?
Builders who rely on agents for API configs, webhook samples, and fixture JSON and want a quick MCP validation gate.
Skip if: Teams that already run exhaustive CI schema tests in every pipeline and do not need an extra remote validator.
What do I get? / Deliverables
Your agent can validate JSON and schemas on demand so bad payloads are caught during testing and review before you ship.
- Syntax-validated JSON with error detail
- Schema conformance result and document structure statistics
Recommended MCP Servers
Journey fit
Syntax and schema checks catch contract drift right before ship when fixtures, env files, and integration responses must be trustworthy. Testing and review workflows benefit from automated JSON validation without spinning a one-off script for every PR.
How it compares
Focused JSON and Schema MCP validator, not a full API contract testing framework.
Common Questions / FAQ
Who is io.github.Br0ski777/json-validator for?
Indie developers and agent users who need fast JSON syntax and JSON Schema checks during ship and review, without local validator scripts.
When should I use io.github.Br0ski777/json-validator?
Use it before merging or deploying when you have JSON configs, API examples, or LLM output that must match a schema.
How do I add io.github.Br0ski777/json-validator to my agent?
Add https://json-validator.api.klymax402.com/mcp as a remote SSE MCP server and set up x402 micropayment for calls.