# x402 JSON Repair (remote · x402.agentfund.net)

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

- Trust score: 54/100 (low)
- Change this week: −10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `x402.agentfund.net`: 54/100 (this document), [markdown](https://verifymcp.io/servers/ktcod-x402-json-repair-mcp/x402.md), [page](https://verifymcp.io/servers/ktcod-x402-json-repair-mcp/x402)

## Channel facts

- Endpoint: `https://x402.agentfund.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 985 tokens (~492/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ktcod-x402-json-repair-mcp https://x402.agentfund.net/mcp
```

### Codex

```toml
[mcp_servers.ktcod-x402-json-repair-mcp]
url = "https://x402.agentfund.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ktcod-x402-json-repair-mcp": {
      "type": "remote",
      "url": "https://x402.agentfund.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ktcod-x402-json-repair-mcp --url https://x402.agentfund.net/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ktcod-x402-json-repair-mcp:
    url: "https://x402.agentfund.net/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ktcod-x402-json-repair-mcp": {
      "type": "http",
      "url": "https://x402.agentfund.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 53, −17)

- [security regression] Authorization: partial → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Transport: pass → fail

### 2026-08-01 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +15)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Transport: fail → pass

### 2026-07-28 (score 51, −13)

- [security regression] Authorization: partial → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Transport: pass → fail

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (2)

### `structured_json_repair` (~436 tokens)

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
  }

Input parameters:

- `coerce` (boolean): When true (default), coerce primitives to satisfy the schema before validating (e.g. "36" -> 36).
- `input` (string, required): Raw or malformed JSON text to repair. Examples: "{name: 'Ada', age: '36',}", a ```json fenced block, or a truncated '{"items":[1,2,3'.
- `schema` (object): Optional JSON Schema (draft 2020-12) object to validate and coerce the repaired JSON against.

Output parameters:

- `changed` (boolean): True if any repair or coercion changed the input.
- `data`: The repaired/validated JSON value (object, array, or primitive). null when repair failed.
- `errors` (array): Actionable error messages when ok is false (empty when ok is true).
- `ok` (boolean): True if the result is valid JSON (and schema-valid when a schema was provided).
- `repairs` (array): Human-readable description of each repair or coercion applied.

### `tabular_to_json` (~549 tokens)

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
  }

Input parameters:

- `format` (string): Force a parser or auto-detect (default 'auto').
- `hasHeader` (string): Whether the first row is a header. 'auto' uses a heuristic.
- `inferTypes` (boolean): When true (default), infer cell types (number/integer/boolean/null); else keep strings.
- `input` (string, required): Raw tabular text: a CSV/TSV block or a Markdown table.
- `schema` (object): Optional JSON Schema (draft 2020-12) to validate/coerce each row object against.

Output parameters:

- `changed` (boolean): True if any normalization or coercion changed the input.
- `columns` (array): Inferred column names and types.
- `errors` (array): Actionable error messages when ok is false (empty when ok is true).
- `format` (string): The detected/used format.
- `ok` (boolean): True if the input parsed as a table (and every row is schema-valid when a schema was given).
- `repairs` (array): Human-readable description of each normalization applied.
- `rowCount` (number): Number of data rows returned.
- `rows` (array): One JSON object per data row, keyed by column name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ktcod-x402-json-repair-mcp/x402#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 53
- 2026-08-01: 70
- 2026-07-31: 69
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 51
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://x402.agentfund.net/mcp
- Repository: https://github.com/ktcod/x402-json-repair-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ktcod-x402-json-repair-mcp/x402/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ktcod-x402-json-repair-mcp/x402/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ktcod-x402-json-repair-mcp/x402