LLM Text vs io.github.robertoyanguas-ops/json-repair-mcp
LLM Text is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.robertoyanguas-ops/json-repair-mcp is an MCP server published by robertoyanguas-ops. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.1 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 | LLM Text | io.github.robertoyanguas-ops/json-repair-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (mcp.llmtxt.dev/sse) | Remote server (json-repair-72343955726.us-central1.run.app/mcp/json-repair) |
| Transport (differs) | SSE | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository | Not stated | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
| Endpoint at the last check (differs) | No HTTP response at the last check (11 h ago) | Responded 15 h ago |
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
LLM Text
Discovers and retrieves llms.txt from websites.
io.github.robertoyanguas-ops/json-repair-mcp
Repairs truncated or malformed LLM JSON outputs (trailing commas, markdown fences, unquoted keys).
How to run each
LLM Text As a remote MCP server
claude mcp add --transport sse llmtxt https://mcp.llmtxt.dev/sseio.github.robertoyanguas-ops/json-repair-mcp As a remote MCP server
claude mcp add --transport http json-repair-mcp https://json-repair-72343955726.us-central1.run.app/mcp/json-repairCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of io.github.robertoyanguas-ops/json-repair-mcp responded at the last daily check. How we check endpoints
Tools each declares
Only LLM Text has
get_domain_llms_txt_as_docsgit
Only io.github.robertoyanguas-ops/json-repair-mcp has
get_agent_wallet_statusrepair_malformed_json
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (io.github.robertoyanguas-ops/json-repair-mcp as of 2026-10-18). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: LLM Text · What it can do: io.github.robertoyanguas-ops/json-repair-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.