fine-tune-prep vs JSONlify
fine-tune-prep is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
fine-tune-prep is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. JSONlify is an MCP server published by irmasemma. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  JSONlify | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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
| Fact | fine-tune-prepno longer listed · | JSONlify |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (www.jsonlify.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/irmasemma/jsonlspageneral |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 11 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of fine-tune-prep
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Corpus-to-dataset pipeline for AI training data curation. Ingests sources, synthesizes examples, generates DPO/KTO preference pairs, applies decontamination, and exports to…
-
data-processing
Data curation and processing at scale including NeMo Curator and Ray Data. Use when preparing training datasets or processing large-scale data.
-
Create evaluation datasets in JSON, CSV, or JSONL format for Dokimos
-
LLM Fine-tuning Engineer — LLM fine-tuning — PEFT/LoRA, RLHF, instruction tuning, prompt optimization
-
Model Training Engineer — Model training — algorithm selection, hyperparameter tuning, training infrastructure
-
Skills for fine-tuning language models with the Tinker API — research, debugging, and more.
What each says it does
fine-tune-prep
Generate dataset preparation for model fine-tuning
JSONlify
Validate and convert JSONL fine-tuning data across 11 AI providers. 13 tools.
How to run each
fine-tune-prep
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
JSONlify As a remote MCP server
claude mcp add --transport http jsonlify https://www.jsonlify.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only JSONlify 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: fine-tune-prep · What it can do: JSONlify · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.