Agent JSON Reliability

io.github.toninovo4249-ai由 GitHub 账号 toninovo4249-ai 发布v0.1.0更新于 Oct 24, 2026

Deterministic inspect, safe repair, and JSON Schema validation for agent JSON. No LLM.

已验证STDIO仅桌面开发者工具AI 与机器学习

概览

AI 生成的概览

以确定性方式检查、安全修复并验证代理生成的 JSON,不使用 LLM,遇到歧义时拒绝处理。

可以做什么
检查文本是否为 JSON,并诊断存在哪些格式错误。对结构性、无歧义的问题进行安全修复,不凭空补值。用 JSON Schema 验证修复后的结果。返回结构化诊断,包括原始是否有效、是否修复、最终是否有效、模式是否通过、是否不安全或有歧义,以及变更与错误列表。对截断或有歧义的输入明确拒绝,而非猜测。
适用场景
当 AI 代理或程序输出的 JSON 经常出现 markdown 围栏、尾逗号、单引号或 True/False/None 等格式错误,且需要在交给下游前先检查、修复并用 JSON Schema 验证时使用。适合需要可复现、不依赖 LLM 猜测的数据清理流程。
运行要求
需在本机以 Python 运行,通过 uvx 启动 PyPI 包 agent-json-reliability,或从源码以 python 模块方式启动。无需账号、API 密钥或环境变量。仅支持桌面环境。
安装前请注意
托管的 reliable 端点需以 x402 付款签名支付 0.003 USDC(Base 网络)才会响应,请勿在无意付款时发送签名。本地 MCP 与 inspect、validate、repair 免费。修复会改写输入文本,但不会自行补上缺失的语义值。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Agent JSON Reliability,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Agent JSON Reliability

Deterministic JSON repair + JSON Schema validation for AI agents.
No LLM. Safe refusal on ambiguity.

[PyPI version] [Python] [MCP] [License: MIT]

STATUS=BETA 0.1.0 · GitHub · PyPI · Official MCP Registry

Problem: agents emit malformed JSON (fences, trailing commas, single quotes). This tool inspects, safely repairs, and schema-validates that text. No LLM. No invented values.

PathCost
Local MCP (uvx agent-json-reliability)Free
Hosted POST /v1/json/inspect, /validate, /repair, /mcpFree
Hosted POST /v1/json/reliable0.003 USDC on Base via x402

Machine catalog: https://agent-json-reliability.onrender.com/v1/catalog
Skill: https://agent-json-reliability.onrender.com/skill.md

Quick start

bash
uvx agent-json-reliability

MCP client config (stdio, published package):

json
{  "mcpServers": {    "agent-json-reliability": {      "command": "uvx",      "args": ["agent-json-reliability"]    }  }}

AI agents and software frequently emit malformed JSON: markdown fences, trailing commas, single quotes, True/False/None, and extra prose around one object.

Agent JSON Reliability is a deterministic pipeline for that failure mode:

  1. inspect — diagnose whether the text is JSON and which failures are present
  2. safe repair — apply only structural, unambiguous fixes
  3. validate — optional JSON Schema check on the result
  4. structured diagnostics — valid_original, repaired, valid_final, schema_valid, unsafe_or_ambiguous, changes, errors

This is not a generic jsonschema wrapper. Missing semantic values are never invented. Ambiguous input is refused.

Primary HTTP endpoint (local/self-hosted): POST /v1/json/reliable

MCP tools (same core functions): reliable_json, validate_json, repair_json, inspect_json

Before / after (safe repair)

Malformed agent output:

json
{  "text": "```json\n{\"name\":\"alice\",\"age\":30,}\n```"}

Expected result (semantically equivalent valid JSON):

  • valid_original=false
  • repaired=true
  • valid_final=true
  • unsafe_or_ambiguous=false
  • json → {"name":"alice","age":30}

If a schema is supplied and satisfied: schema_valid=true.

Safe refusal (ambiguous)

Truncated input such as {"user": is JSON-intended but not deterministically repairable without inventing keys or values.

Expected:

  • HTTP 200 (documented safe response)
  • valid_final=false
  • unsafe_or_ambiguous=true or repaired=false

Do not treat a correct refusal as a product failure.

Run locally (no Hunter)

bash
python -m pip install -r requirements.txtpython serve.py

Binds 127.0.0.1:8770 by default. Set PUBLIC_BASE_URL to an HTTPS origin only when you expose the process yourself. Do not commit a temporary tunnel hostname as the canonical URL.

Hosted API (x402)

Public origin: https://agent-json-reliability.onrender.com

Inspect / validate / repair / MCP stay free. POST /v1/json/reliable returns HTTP 402 until an x402 PAYMENT-SIGNATURE settles 3000 atomic USDC (0.003) on Base (eip155:8453) via PayAI.

bash
curl -s -D - -o /tmp/ajr.json -X POST https://agent-json-reliability.onrender.com/v1/json/reliable \  -H "content-type: application/json" \  -d '{"text":"{'\''a'\'': 1}"}'# Expect: HTTP/1.1 402  and a PAYMENT-REQUIRED header. Do not send a signature unless you intend to pay.

HTTP examples

See examples/curl.md, examples/python.py, examples/javascript.js.

Remote examples use https://agent-json-reliability.onrender.com. Local default is http://127.0.0.1:8770.

Share URLs (optional, unverified telemetry tags):

  • /?source=github
  • /?source=mcp-registry
  • /?source=api-directory

MCP (stdio — durable)

Package transport does not depend on a temporary public URL. Prefer uvx (above). From a checkout:

json
{  "mcpServers": {    "agent-json-reliability": {      "command": "python",      "args": ["-m", "products.gateway.mcp_stdio"]    }  }}

Remote HTTP MCP (POST /mcp) is for a running instance.

Machine discovery

  • Hosted origin: https://agent-json-reliability.onrender.com
  • GET /.well-known/agent-services.json
  • GET /.well-known/agent.json
  • GET /.well-known/x402
  • GET /openapi.json
  • GET /llms.txt · GET /llms-full.txt · GET /AGENTS.md · GET /sitemap.xml · GET /robots.txt
  • POST /mcp JSON-RPC (tools/list, tools/call)

What this package does not include

No Hunter market database, no private reports, no Windows user paths, no collectors, no wallets in this package. Hosted /v1/json/reliable is x402-paid; local MCP and inspect/validate/repair are free.

来源:README.md,提交 85cb45c

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.0最新Sep 21, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。