com.clawhard/mend · v1.0.0 · productivity
Mend is healthy: it completed an MCP handshake in 257 ms and exposes 4 tools.
Repair broken JSON without changing values, find the exact error, outline or query big payloads.
Endpoint: https://mend.clawhard.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 257 ms |
| Last checked (UTC) | 2026-11-03T02:10:27.047Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-03T02:10:27.047Z | Healthy | 257 |
mend_repair_json | Use when JSON from an LLM, API, log, config or copy-paste fails to parse (JSON.parse error, "Unexpected token", "Expecting property name"), or the user pastes JSON with trailing commas, single quotes, unquoted keys, comments, Python True/False/None, NaN, missing commas or brackets, a ```json fence, |
mend_check_json | Use when you need to know whether text is strictly valid JSON, and if not, exactly where it breaks. Strict RFC 8259 check (the same accept/reject as JSON.parse). Returns line, column, the offending line with a caret and whether Mend can repair it. Use mend_repair_json to fix it. Up to 100,000 charac |
mend_outline_json | Use when you are about to read a big JSON response, log or export into context, before loading it: returns a compact outline of the structure (keys, types, array lengths, one example per repeated shape) so you can plan a query without spending tokens on the whole document. Repairs the JSON first if |
mend_query_json | Use when you need specific fields from a JSON document without reading all of it: $.users[0].name, $.items[*].id, $.a.b[-1], $.list[1:3], $..email (recursive). Returns each match with its exact path, type and value. Repairs the JSON first if needed, so broken input still works. Up to 100,000 charact |