Json Mender MCP server
Local MCP server: JSON repair, regex testing, JSON-Schema validation for AI agents.
0 stars187 downloads/wk
Reviews
Write oneNobody has reviewed Json Mender yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Json Mender tools (3)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
repair_jsonRepair malformed JSON (trailing commas, unescaped quotes, missing brackets) and return the parsed result.
validate_against_schemaValidate data against a real JSON-Schema (draft 2020-12) and report all errors.
validate_regexTest a regex pattern against one or more strings deterministically and return match details.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
- Code scan3 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 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Json Mender compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 80% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 187
- more than 74% of 12,191 servers with a package
What its tools let an agent do: 3 read
Install Json Mender in Claude Code, Cursor or VS Code
Runs npx -y json-mender-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add json-mender-mcp -- npx -y json-mender-mcp
What the publisher says
From the Json Mender repository's README, as published. We do not edit it. Read it on GitHub
JSON Mender MCP — Fix Malformed JSON, Validate JSON Schema, Test Regex for AI Agents
A free, local MCP server that fixes broken JSON output from LLMs, validates data against a real JSON Schema, and tests regex patterns deterministically — no API keys, no network calls, no telemetry.
If you're building an AI agent and keep hitting JSONDecodeError, unterminated strings, trailing commas, or unquoted keys in model output, this is the MCP server for that exact problem.
Same local-first, deterministic philosophy as polymath-megablaster-mcp, applied specifically to the "model wrote JSON that doesn't parse" problem.
The problem this solves
LLMs — especially smaller or local models (Llama, Qwen, Mistral) — routinely produce JSON that looks right but fails to parse: trailing commas, single quotes instead of double, unescaped inner quotes, missing commas, truncated output. Asking the model to "fix the JSON" usually just produces a second broken attempt. repair_json fixes it deterministically, every time, the same way, with no second model call needed.
Tools
- repairjson** — fix malformed/invalid JSON (trailing commas, unquoted keys, unescaped quotes, truncated structures) and return the corrected, parsed result. Built on jsonrepair.
- validateregex** — test a regex pattern against one or more strings deterministically. Useful because models frequently write regex that compiles but doesn't match what they think it matches.
- validateagainstschema — validate any JSON data against a real JSON Schema (via ajv, the most widely used JS Schema validator) and get precise, per-field, human-readable error messages instead of a generic pass/fail.
Setup
1. Install Node.js (v18+) if you don't have it: https://nodejs.org
2. Clone and install:
git clone https://github.com/headlessherm-creator/json-mender-mcp.git
cd json-mender-mcp
npm install3. Point your MCP client at it:
{
"mcpServers": {
"json-mender": {
"command": "node",
"args": ["/path/to/json-mender-mcp/src/index.js"]
}
}
}Setup docs for common clients:
- Claude Desktop: https://modelcontextprotocol.io/quickstart/user
- Cursor: https://docs.cursor.com/context/model-context-protocol
- Claude Code: https://docs.claude.com/en/docs/claude-code/mcp
Why local
No fetch/http import anywhere in src/tools.js — every tool runs as pure local computation using jsonrepair and ajv, both well-established, actively maintained npm packages. Nothing you send through this server leaves your machine.
Keywords
JSON repair MCP server, fix broken JSON from LLM, malformed JSON parser, JSON schema validation MCP, regex tester MCP, local MCP server no API key, Claude MCP JSON tools, AI agent structured output validation.
Related tools
Same local-first philosophy, different problems:
- polymath-megablaster-mcp — deterministic math, date, unit conversion, networking
- hiring-mender-mcp — BambooHR + Greenhouse ATS write tools, one vocabulary
- helpdesk-mender-mcp — Zendesk + Freshdesk + Help Scout write tools, one vocabulary
License
MIT
Nothing above is checked by us. What we check is on the safety report.
Json Mender: common questions
- Is Json Mender MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Json Mender safety report
- How do I install Json Mender?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Json Mender need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Json Mender maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.2.1.
- How does Json Mender compare with other MCP servers?
- safety score 89/100 (higher than 80% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.