Ext Ops Panel
Open dashboard
Comparison

Payload Validator vs io.github.machinegrade/validate

Payload Validator is an MCP server published by gumballtools.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.machinegrade/validate is an MCP server published by machinegrade. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplacePayload Validatorio.github.machinegrade/validate
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 167
Downloads/week (npm): 33
Forks (GitHub): 0
Stars (GitHub): 1
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

Payload Validator vs io.github.machinegrade/validate
FactPayload Validatorio.github.machinegrade/validate
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (payload-validator.gumballtools.com/api/mcp)Remote server (api.machinegrade.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/bwalvoord/gumballgithub.com/machinegrade/validate
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last checknot checked yetnot checked yet

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

Payload Validator

In its own words, on Official MCP Registry:

Validate JSON, YAML, XML and CSV with exact line/column errors and silent-corruption warnings.

io.github.machinegrade/validate

In its own words, on Official MCP Registry:

Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.

How to run each

Payload Validator As a remote MCP server

Claude Code
claude mcp add --transport http payload-validator https://payload-validator.gumballtools.com/api/mcp

io.github.machinegrade/validate As a remote MCP server

Claude Code
claude mcp add --transport http validate https://api.machinegrade.dev/mcp

Requires: SANDBOX_API_KEY (secret)

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

Tools each declares

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

Settings each asks for

The marketplaces of Payload Validator publish no settings it asks for, so we do not compare settings.

What it can do: Payload Validator · What it can do: io.github.machinegrade/validate · 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