Mend
REMOTE · MEND.CLAWHARD.COM
Repair broken JSON without changing values, find the exact error, outline or query big payloads.
Available components
Last scanned (3 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 905 tokens (~90/item across 10 items; 4 tools + 6 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 3 Nov 26 0
- Tool “mend_outline_json” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mend.clawhard.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=clawhard.com | CN=WE1,O=Google Trust Services,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 81f62eb21d3b6f60e7f73ba92dc3d96 |
| SANs: clawhard.com, mend.clawhard.com, *.mend.clawhard.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mend.clawhard.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| clawhard.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mend.clawhard.com/mcp | Verified | 200 | |
| http (plaintext) | http://mend.clawhard.com/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mend_check_json Validate JSON and locate the exact error ~93
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 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to validate. |
No output schema declared.
No examples provided.
mend_outline_json Outline the structure of a large JSON payload ~146
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 needed. Follow with mend_query_json to pull only the values you need. Up to 100,000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | integer | – | How many levels to expand. Default 4. |
| max_items | integer | – | How many array items to show when items differ. Default 6. |
| text | string | yes | The JSON (or JSON-ish text). |
No output schema declared.
No examples provided.
mend_query_json Extract values from JSON by path ~155
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 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| max | integer | – | Maximum matches to return. Default 50. |
| path | string | yes | Path such as $.users[*].email, data.items[0], $..id, $.list[-1], $.list[1:3]. |
| text | string | yes | The JSON (or JSON-ish text). |
No output schema declared.
No examples provided.
mend_repair_json Repair broken or LLM-generated JSON ~247
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, text around it, or output that was cut off. Deterministic repair: returns valid, formatted JSON plus a list of every fix with line and column. Values are never rewritten, so big numbers, number formatting and key order stay exactly as written (re-asking a model to "fix the JSON" changes data and costs tokens). If the text is already valid it says so. Up to 100,000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | integer | – | Spaces per indent level in the output. Default 2. Use 0 for one minified line. |
| sort_keys | boolean | – | Sort object keys alphabetically. Default false (keep the original order). |
| text | string | yes | The broken JSON, or any text that contains JSON (a chat reply, a log line, a code block). |
No output schema declared.
No examples provided.
How do I install the Mend MCP server?
Mend is a hosted endpoint at https://mend.clawhard.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mend.clawhard.com
claude mcp add --transport http com-clawhard-mend 'https://mend.clawhard.com/mcp'
What is the Mend MCP server?
Mend is an MCP server listed in the public MCP registry as com.clawhard/mend. Repair broken JSON without changing values, find the exact error, outline or query big payloads. This page covers its hosted endpoint (https://mend.clawhard.com/mcp).
Is the Mend MCP server safe to use?
Mend scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mend MCP server expose?
Mend exposes 4 tools: mend_repair_json, mend_check_json, mend_outline_json, mend_query_json. Their descriptions and schemas cost roughly 641 tokens of context every time the server is loaded.
Does the Mend MCP server require authentication?
No. We connected to Mend without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mend MCP server still maintained?
Mend is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.