# Mend (remote · mend.clawhard.com)

Repair broken JSON without changing values, find the exact error, outline or query big payloads.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mend.clawhard.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-clawhard-mend/mend.md), [page](https://verifymcp.io/servers/com-clawhard-mend/mend)

## Channel facts

- Endpoint: `https://mend.clawhard.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 905 tokens (~90/item across 10 items; 4 tools + 6 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-clawhard-mend 'https://mend.clawhard.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-clawhard-mend": {
      "url": "https://mend.clawhard.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-clawhard-mend": {
      "type": "http",
      "url": "https://mend.clawhard.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-clawhard-mend]
url = "https://mend.clawhard.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-clawhard-mend": {
      "type": "remote",
      "url": "https://mend.clawhard.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-clawhard-mend --url 'https://mend.clawhard.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-clawhard-mend:
    url: "https://mend.clawhard.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-clawhard-mend": {
      "Transport": "http",
      "Url": "https://mend.clawhard.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-clawhard-mend -t streamable-http -u 'https://mend.clawhard.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-clawhard-mend": {
      "type": "http",
      "url": "https://mend.clawhard.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 70, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-11-03 (score 69, 0)

- [security] Tool “mend_outline_json” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 69)

First indexed and scored.

## MCP tools (4)

### `mend_repair_json` (~247 tokens)

Repair broken or LLM-generated 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, 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.

Input parameters:

- `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, required): The broken JSON, or any text that contains JSON (a chat reply, a log line, a code block).

### `mend_check_json` (~93 tokens)

Validate JSON and locate the exact error

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.

Input parameters:

- `text` (string, required): The text to validate.

### `mend_outline_json` (~146 tokens)

Outline the structure of a large JSON payload

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.

Input parameters:

- `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, required): The JSON (or JSON-ish text).

### `mend_query_json` (~155 tokens)

Extract values from JSON by path

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.

Input parameters:

- `max` (integer): Maximum matches to return. Default 50.
- `path` (string, required): Path such as $.users[*].email, data.items[0], $..id, $.list[-1], $.list[1:3].
- `text` (string, required): The JSON (or JSON-ish text).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-clawhard-mend/mend#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69

## Common questions

### 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.

## Links

- Remote endpoint: https://mend.clawhard.com/mcp
- Website: https://mend.clawhard.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-clawhard-mend/mend.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-clawhard-mend/mend.json
- HTML version of this page: https://verifymcp.io/servers/com-clawhard-mend/mend