x402 JSON Repair
REMOTE · X402.AGENTFUND.NET · SCANNED AUG 3
Pay-per-call JSON repair + JSON Schema validation for AI agents (USDC on Base, x402).
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · x402.agentfund.net
claude mcp add --transport http ktcod-x402-json-repair-mcp https://x402.agentfund.net/mcp
[mcp_servers.ktcod-x402-json-repair-mcp] url = "https://x402.agentfund.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ktcod-x402-json-repair-mcp": {
"type": "remote",
"url": "https://x402.agentfund.net/mcp",
"enabled": true
}
}
} openclaw mcp add ktcod-x402-json-repair-mcp --url https://x402.agentfund.net/mcp --transport streamable-http
mcp_servers:
ktcod-x402-json-repair-mcp:
url: "https://x402.agentfund.net/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 2 Aug 26 −17
- Authorization: partial → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- 1 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +15
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- 28 Jul 26 −13
- Authorization: partial → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://x402.agentfund.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402.agentfund.net | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 14 Jun 2026 | 14 Dec 2026 | RSA 2048 | SHA256-RSA | 277b09632198e5f8a38253ea2c7a9ff |
| SANs: x402.agentfund.net | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
DNSSEC insecure
Validation of x402.agentfund.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| agentfund.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402.agentfund.net/mcp | Unreachable | ||
| http (plaintext) | http://x402.agentfund.net/mcp | HTTPS enforced | 301 | https://x402.agentfund.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
structured_json_repair Structured JSON Repair ~436
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 }
| Name | Type | Req | Description |
|---|---|---|---|
| coerce | boolean | — | When true (default), coerce primitives to satisfy the schema before validating (e.g. "36" -> 36). |
| input | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | yes | 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 | yes | Actionable error messages when ok is false (empty when ok is true). |
| ok | boolean | yes | True if the result is valid JSON (and schema-valid when a schema was provided). |
| repairs | array | yes | Human-readable description of each repair or coercion applied. |
No examples provided.
tabular_to_json Tabular to JSON ~549
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 }
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| changed | boolean | yes | True if any normalization or coercion changed the input. |
| columns | array | yes | Inferred column names and types. |
| errors | array | yes | Actionable error messages when ok is false (empty when ok is true). |
| format | string | yes | The detected/used format. |
| ok | boolean | yes | True if the input parsed as a table (and every row is schema-valid when a schema was given). |
| repairs | array | yes | Human-readable description of each normalization applied. |
| rowCount | number | yes | Number of data rows returned. |
| rows | array | yes | One JSON object per data row, keyed by column name. |
No examples provided.