Ext Ops Panel
Open dashboard
Comparison

fhir-format vs JSON Validator API

fhir-format is a plugin bundle for AI coding tools published by dnlbox. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). JSON Validator API is an MCP server published by Br0ski777. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacefhir-formatJSON Validator API
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
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

fhir-format vs JSON Validator API
Factfhir-formatJSON Validator API
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (json-validator.api.klymax402.com/mcp)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/dnlbox/fhir-format-skillgithub.com/br0ski777/json-validator-x402
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-13

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

fhir-format

In its own words, on Claude Code: claude-plugins-community:

Accuracy-first FHIR R4/R4B/R5 skill for JSON formatting and reasoning. It labels claims as normative/version-delta/profile-dependent/practice, requires source-backed normative statements, avoids guessed terminology codes, and clearly separates structural validation from full profile conformance.

JSON Validator API

In its own words, on Official MCP Registry:

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

How to run each

fhir-format As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install fhir-format@claude-community

JSON Validator API As a remote MCP server

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

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: fhir-format · What it can do: JSON Validator API · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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