Ext Ops Panel
Open dashboard
Comparison

JSON Validator API vs io.github.rog0x/json

JSON Validator API is an MCP server published by Br0ski777. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rog0x/json is an MCP server published by rog0x. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceJSON Validator APIio.github.rog0x/json
Official MCP Registry Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (npm): 163
Downloads/week (npm): 35
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

JSON Validator API vs io.github.rog0x/json
FactJSON Validator APIio.github.rog0x/json
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (json-validator.api.klymax402.com/mcp)On your machine (@rog0x/mcp-json-tools)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/br0ski777/json-validator-x402github.com/rog0x/mcp-json-tools
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

JSON Validator API

In its own words, on Official MCP Registry:

JSON syntax validation, JSON Schema checking, structure stats. x402 micropayment.

io.github.rog0x/json

In its own words, on Official MCP Registry:

JSON/YAML/CSV validate, diff, transform for AI agents

How to run each

JSON Validator API As a remote MCP server

Claude Code
claude mcp add --transport sse json-validator https://json-validator.api.klymax402.com/mcp

io.github.rog0x/json As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio json -- npx -y @rog0x/mcp-json-tools

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only JSON Validator API has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: JSON Validator API · What it can do: io.github.rog0x/json · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built