mcpbeat

x402 JSON Repair MCP Server

io.github.ktcod/x402-json-repair-mcp
answering

x402 JSON Repair is answering right now. Last checked 3 min ago. It exposes 2 tools. Last commit 15 Jun 2026.

Pay-per-call JSON repair + JSON Schema validation for AI agents (USDC on Base, x402).

Uptime history 40 hours of history · worst hour 0%
40 hours agonow
64.8%
Uptime 24h
59 of 91 checks
2
Tools
read from the server
3300 ms
Response time
average over 24h
0
Stars
last commit 15 Jun 2026

Connect this server

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

run in your terminal
claude mcp add x402-json-repair-mcp --transport http https://x402.agentfund.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "x402-json-repair-mcp": {
      "url": "https://x402.agentfund.net/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.x402-json-repair-mcp]
url = "https://x402.agentfund.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "x402-json-repair-mcp": {
      "url": "https://x402.agentfund.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "x402-json-repair-mcp": {
      "url": "https://x402.agentfund.net/mcp"
    }
  }
}

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.

structured
structured_json_repair
Repair messy or invalid JSON (the kind LLMs and tools often emit) into clean, valid JSON, and optionally validate/coerce it against a JSON Schema. Pure deterministic compute — no network or model calls. What it fixes: trailing commas, single-quoted strings, unquoted keys, Python literals (None/True/False), NaN/Infinity, Markdown code-fence wrappers, and truncated/garbled tails. When to use: you received text that should be JSON but JSON.parse fails, or you have JSON that must conform to a specific schema and want types coerced (e.g. "36" -> 36, "true" -> true). When NOT to use: the input is already known-valid JSON and no schema check is needed. Args: - input (string, required): the raw/malformed JSON text. - schema (object, optional): a JSON Schema (draft 2020-12) to validate and coerce against. - coerce (boolean, optional, default true): coerce primitive types to satisfy the schema before validating. Returns structuredContent: { "ok": boolean, // true if valid JSON (and schema-valid when a schema was given) "data": any, // the repaired/validated JSON value; null if unfixable "changed": boolean, // true if any repair or coercion modified the input "errors": string[], // actionable messages when ok is false "repairs": string[] // description of each fix applied }
tabular
tabular_to_json
Convert messy tabular text into clean, typed JSON rows. Auto-detects CSV, TSV, or a Markdown table and returns one JSON object per row plus an inferred column/type summary. Pure deterministic compute — no network or model calls. What it handles: delimiter sniffing (comma/semicolon/tab/pipe), quoted fields with embedded commas and newlines, BOM, ragged rows (padded/truncated), Markdown separator rows and escaped pipes, header auto-detection, and per-column type inference (integer/number/boolean/null/string). When to use: you have CSV/TSV/Markdown-table text (often emitted by tools or LLMs) and want structured, typed rows — optionally validated/coerced against a JSON Schema. When NOT to use: the data is already clean JSON, or it is HTML/xlsx/binary (not supported). Args: - input (string, required): raw tabular text. - format ("auto"|"csv"|"tsv"|"markdown", default "auto"): force a format or auto-detect. - hasHeader ("auto"|"true"|"false", default "auto"): whether the first row is a header. - inferTypes (boolean, default true): coerce cells to number/integer/boolean/null; else keep strings. - schema (object, optional): JSON Schema (draft 2020-12) to validate/coerce each row object against. Returns structuredContent: { "ok": boolean, // false if the input cannot be parsed as a table "format": "csv"|"tsv"|"markdown", "columns": [{ "name": string, "type": string }], "rows": [{ ... }], // one object per row, keyed by column name "rowCount": number, "changed": boolean, // true if any normalization/coercion happened "errors": string[], // actionable messages when ok is false "repairs": string[] // description of each normalization applied }

Endpoints

URLTransportStateLatencyChecked
https://x402.agentfund.net/mcp streamable-http answering 700 ms 3 min ago

x402 JSON Repair — questions

Answers built from our own checks of this server.

What can x402 JSON Repair do?
It exposes 2 tools, read directly from the server on our last check. Among them: structured_json_repair, tabular_to_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 x402 JSON Repair working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 59 of 91 checks got a reply (64.8%), average response time 3300 ms. The bar chart above shows every period we have measured.
How do I connect x402 JSON Repair?
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 x402 JSON Repair need an API key?
No. x402 JSON Repair 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.
Is x402 JSON Repair open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.