JSON Repair MCP Server

by robertoyanguas-ops Your server? Claim it

answering

JSON Repair MCP is answering right now. Last checked 13 min ago. It exposes 2 tools.

Repairs truncated or malformed LLM JSON outputs (trailing commas, markdown fences, unquoted keys).

Uptime history 68 hours of history

68 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

222 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 12

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

16 Oct 2 tools changed the parameters they ask for4 times that day get_agent_wallet_status, repair_malformed_json

16 Oct 2 tool descriptions were rewritten get_agent_wallet_status, repair_malformed_json

16 Oct a tool changed version

15 Oct 2 tool descriptions were rewritten get_agent_wallet_status, repair_malformed_json

15 Oct 2 tools changed the parameters they ask for get_agent_wallet_status, repair_malformed_json

14 Oct a tool description was rewritten repair_malformed_json

and 2 more, back to 14 October 2026

Nothing serious here today

Today is the operative word: we check JSON Repair MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add json-repair-mcp --transport http https://json-repair-72343955726.us-central1.run.app/mcp/json-repair

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "json-repair-mcp": {
      "url": "https://json-repair-72343955726.us-central1.run.app/mcp/json-repair"
    }
  }
}

~/.codex/config.toml

[mcp_servers.json-repair-mcp]
url = "https://json-repair-72343955726.us-central1.run.app/mcp/json-repair"

.cursor/mcp.json

{
  "mcpServers": {
    "json-repair-mcp": {
      "url": "https://json-repair-72343955726.us-central1.run.app/mcp/json-repair"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "json-repair-mcp": {
      "url": "https://json-repair-72343955726.us-central1.run.app/mcp/json-repair"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent

get_agent_wallet_status

Show an agent's account: free calls used (of 5), prepaid USD balance, total spent, total calls and tokens saved. Free: it never charges or uses a free call. Call it before a batch of paid calls, or after a top-up to confirm the credit arrived. It does not process content or take payments; use the other tools on this server for that. Returns JSON with free_calls_used, balance_usd, total_spent_usd, total_tokens_saved.

repair

repair_malformed_json

Repairs truncated or malformed LLM JSON outputs (trailing commas, markdown fences, single quotes) so multi-agent pipelines never crash. Use it when your task needs this for one raw_json; this endpoint offers only this tool and get_agent_wallet_status. Read-only; results are cached for 1 hour. $0.002 per call. Returns JSON with the result under data. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After that the tool returns a payment-required message (not an error) with a Stripe top-up link (from $2) and Base/Solana USDC addresses; pay, then repeat the same call with the same agent_id, or add tx_hash after a USDC transfer.

Endpoints

URL	Transport	State	Latency	Checked
https://json-repair-72343955726.us-central1.run.app/mcp/json-repair	streamable-http	answering	198 ms	13 min ago

Alternatives to JSON Repair MCP

same job, measured the same way

Json5 MCP

by mukundakatta

Parse JSON5 (comments, trailing commas, unquoted keys) and emit strict JSON.

32 installs/wk local only

LLMKit

by olsols4

Token counting, RAG chunking, truncation, HTML to Markdown and JSON repair

answering

JSON Repair MCP

by grupoanesthy-spec

Repairs malformed JSON from LLM output, validated against a schema. Paid per call via Stripe.

22 installs/wk local only

Jsonaut

by shoggi211

Repair malformed JSON from LLM/agent output; optional JSON Schema coercion. Free + x402 paid.

4 tools answering

Streamparse

by mukundakatta

Parse partial / truncated / messy JSON for LLM tool calls and structured outputs.

38 installs/wk local only

Scrapiq

by scrapiq

Any URL to clean text, markdown, or JSON for LLM/RAG pipelines.

1 tools answering

JSON Contracts

by json-contracts

JSON contract registry and validator for structured LLM and agent outputs.

51 installs/wk local only

Html Vers Markdown

by dawaxwx

HTML to clean Markdown for LLM and RAG pipelines: headings, lists, tables, links, code fences. Pr...

1 tools answering

JSON Repair MCP — questions

Answers built from our own checks of this server.

What can JSON Repair MCP do?

It exposes 2 tools, read directly from the server on our last check. Among them: get_agent_wallet_status, repair_malformed_json. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is JSON Repair MCP working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 222 ms. The bar chart above shows every period we have measured.

How do I connect JSON Repair MCP?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does JSON Repair MCP need an API key?

No. JSON Repair MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is JSON Repair MCP?

It answers our handshake in 222 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.