JsonMend
by jsonmend.mike-tusa.workers.dev in AI models & inference
Repair broken JSON from LLM output and validate it against a JSON Schema.
https://jsonmend.mike-tusa.workers.dev/mcp- Tools
- 2
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 131 ms
- 234 ms slowest 5%
- Last check
- Passed
- 11 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"jsonmend": {
"type": "http",
"url": "https://jsonmend.mike-tusa.workers.dev/mcp"
}
}
}2 tools
- repair_json
Turn broken or messy JSON text into valid JSON. Strips Markdown code fences and prose before/after the JSON, removes comments and trailing commas, converts single/curly quotes, quotes unquoted keys, maps Python None/True/False, inserts missing commas, closes truncated…
- validate_json
Check JSON against a JSON Schema and get every error with its JSON Pointer path. Send the JSON either as text ("input"; broken text is repaired first, and the fixes are listed) or as an already-parsed value ("data"). Optional coerce converts "42" → 42, "true" → true, etc. toward…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 11 h ago | Passed | 200 | 117 ms |
| 24 h ago | Passed | 200 | 114 ms |
| 36 h ago | Passed | 200 | 91 ms |
| 2 days ago | Passed | 200 | 118 ms |
| 3 days ago | Passed | 200 | 146 ms |
Show 10 older checks
| 3 days ago | Passed | 200 | 102 ms |
| 3 days ago | Passed | 200 | 95 ms |
| 4 days ago | Passed | 200 | 128 ms |
| 4 days ago | Passed | 200 | 113 ms |
| 5 days ago | Passed | 200 | 111 ms |
| 5 days ago | Passed | 200 | 225 ms |
| 6 days ago | Passed | 200 | 109 ms |
| 6 days ago | Passed | 200 | 131 ms |
| 6 days ago | Passed | 200 | 95 ms |
| 7 days ago | Passed | 200 | 124 ms |