mcpbeat Sign in

Mend MCP Server

answering

Mend is answering right now. Last checked 8 min ago. It exposes 4 tools.

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

Uptime history 5 hours of history
5 hours agonow
100.0%
Uptime 24h
17 of 17 checks
4
Tools
read from the server
88 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Mend every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add mend --transport http https://mend.clawhard.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mend.clawhard.com/mcp
~/.codex/config.toml
[mcp_servers.mend]
url = "https://mend.clawhard.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mend": {
      "url": "https://mend.clawhard.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mend": {
      "type": "http",
      "url": "https://mend.clawhard.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mend
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 characters.
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 needed. Follow with mend_query_json to pull only the values you need. Up to 100,000 characters.
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 characters.
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, 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.

Endpoints

URLTransportStateLatencyChecked
https://mend.clawhard.com/mcp streamable-http answering 140 ms 8 min ago

Alternatives to Mend

same job, measured the same way
E
Extract Insurance
by extractinsurance

Insurance documents into JSON, with the quote and page behind every value.

1 563 installs/wk local only
Vayl
by ac12644

Reconciling memory for AI agents: a changed fact retires the old value, with history and approval.

257 installs/wk local only
JsonMend
by workers-mike-tusa-jsonmend

Repair broken JSON from LLM output and validate it against a JSON Schema.

2 tools answering
Schema Compatibility MCP
by mrfentmen

Compare local JSON schema shape fingerprints without returning property names, values, paths, or...

55 installs/wk local only
SEO Records Corrector
by seorecords

Fixes the SEO of any public page: each correction with its value, source and exact HTML tag.

2 tools answering
Extcord
by extcord

Agent utilities: read big pages without filling context, exact math, dates, parsing. Free.

11 tools answering
Skim MCP
by helloderekg

Lossless skim-then-expand reading of big files, repos, and command output with far fewer tokens

102 installs/wk local only
MCP Check Links
by webmoleai

Find broken links, missing meta tags, and redirect chains on any website.

48 installs/wk local only

Mend — questions

Answers built from our own checks of this server.

What can Mend do?
It exposes 4 tools, read directly from the server on our last check. Among them: mend_check_json, mend_outline_json, mend_query_json, mend_repair_json. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Mend working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 17 of 17 checks got a reply (100.0%), average response time 88 ms. The bar chart above shows every period we have measured.
How do I connect Mend?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Mend need an API key?
No. Mend completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Mend?
It answers our handshake in 88 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.