Agent JSON Reliability MCP server
io.github.toninovo4249-ai/agent-json-reliability·v0.1.0Deterministic inspect, safe repair, and JSON Schema validation for agent JSON. No LLM.
0 stars73 downloads/wk
Reviews
Write oneNobody has reviewed Agent JSON Reliability yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Agent JSON Reliability tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 40 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Agent JSON Reliability compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 80% of 4,460 AI and agents servers
- Downloads a week
- 73
- more than 55% of 1,538 AI and agents servers with a package
Install Agent JSON Reliability in Claude Code, Cursor or VS Code
claude mcp add agent-json-reliability -- uvx agent-json-reliability
What the publisher says
From the Agent JSON Reliability repository's README, as published. We do not edit it. Read it on GitHub
Agent JSON Reliability
Deterministic JSON repair + JSON Schema validation for AI agents. No LLM. Safe refusal on ambiguity.
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.
Machine catalog: https://agent-json-reliability.onrender.com/v1/catalog Skill: https://agent-json-reliability.onrender.com/skill.md
Quick start
uvx agent-json-reliabilityMCP client config (stdio, published package):
{
"mcpServers": {
"agent-json-reliability": {
"command": "uvx",
"args": ["agent-json-reliability"]
}
}
}<!-- mcp-name: io.github.toninovo4249-ai/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:
- inspect — diagnose whether the text is JSON and which failures are present
- safe repair — apply only structural, unambiguous fixes
- validate — optional JSON Schema check on the result
- structured diagnostics — validoriginal, repaired, validfinal, schemavalid, unsafeor_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): reliablejson, validatejson, repairjson, inspectjson
Before / after (safe repair)
Malformed agent output:
{
"text": "```json\n{\"name\":\"alice\",\"age\":30,}\n```"
}Expected result (semantically equivalent valid JSON):
- valid_original=false
- repaired=true
- valid_final=true
- unsafeorambiguous=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
- unsafeorambiguous=true or repaired=false
Do not treat a correct refusal as a product failure.
Run locally (no Hunter)
python -m pip install -r requirements.txt
python serve.pyBinds 127.0.0.1:8770 by default. Set PUBLICBASEURL 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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Agent JSON Reliability: common questions
- Is Agent JSON Reliability MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Agent JSON Reliability safety report
- How do I install Agent JSON Reliability?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Agent JSON Reliability need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Agent JSON Reliability maintained?
- The last commit was 43 days ago (2026-09-22). The latest release is v0.1.0.
- What can I use instead of Agent JSON Reliability?
- Servers from other publishers that do the same job: agent-device MCP server, FireCMS Cloud MCP server and Butterbase AI MCP server.
- How does Agent JSON Reliability compare with other AI and agents MCP servers?
- safety score 88/100 (higher than 80% of 4,460 AI and agents servers); downloads a week 73 (more than 55% of 1,538 AI and agents servers with a package). Full comparison.
Alternatives to Agent JSON Reliability
Same job from other publishers: the closest match first, then the best rated.
- agent-deviceLet AI agents inspect, control, and debug real iOS, Android, desktop, and TV appsnot reviewedWidely usedA
- FireCMS CloudManage FireCMS Cloud from an AI agent: Firestore data, collections, schemas and users.not reviewedEstablishedA
- Butterbase AIButterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.not reviewedEstablishedA
- AKShareLet a model explore AKShare's 1000+ China market data functions on its own — search, inspect, callnot reviewedEstablishedA