Ext Ops Panel
Open dashboard
Comparison

JsonMend vs datoon

JsonMend is an MCP server published by jsonmend.mike-tusa.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). datoon is an MCP server published by andrii-su. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
MarketplaceJsonMenddatoon
Official MCP Registry Listed
Version: 0.1.3
No figure published
Not marked · First seen
Listed
Version: 1.9.1
Downloads/month (PyPI): 154
Downloads/week (PyPI): 39
Forks (GitHub): 0
Stars (GitHub): 2
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

JsonMend vs datoon
FactJsonMenddatoon
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (jsonmend.mike-tusa.workers.dev/mcp)On your machine (datoon)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/andrii-su/datoon
Changes in the last 7 days00
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)Responded 3 days agono 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

JsonMend

In its own words, on Official MCP Registry:

Repair broken JSON from LLM output and validate it against a JSON Schema.

datoon

In its own words, on Official MCP Registry:

Smart structured-data to TOON gateway: converts to TOON only when it saves LLM tokens.

How to run each

JsonMend As a remote MCP server

Claude Code
claude mcp add --transport http jsonmend https://jsonmend.mike-tusa.workers.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

datoon As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio datoon -- uvx --from "datoon[mcp]" datoon mcp

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

Only JsonMend 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: JsonMend · What it can do: datoon · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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