JSON Repair MCP Server

by cedrickouma Your server? Claim it

answering

JSON Repair is answering right now. Last checked 7 min ago. 26 installs a week from npm.

MCP server (stdio): repair broken/malformed JSON via the AgentForge API

Installs per day peak 25 · avg 7 · +32% w/w

a month agotoday

Uptime history 48 days of history · worst day 95%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

733 ms

Response time

average over 24h

Installs / week

npm and PyPI

JSON Repair does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add json-repair --transport http https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "json-repair": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.json-repair]
url = "https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "json-repair": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "json-repair": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp"
    }
  }
}

This one needs environment variables set before it will start: AGENTFORGE_BASE_URL (AgentForge APIM gateway base URL), AGENTFORGE_API_KEY (APIM subscription key (Ocp-Apim-Subscription-Key / x-api-key)). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp	streamable-http	needs key	657 ms	7 min ago

Alternatives to JSON Repair

same job, measured the same way

Schema Validate

by cedrickouma

MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API

30 installs/wk answering

Openapi Lint

by cedrickouma

MCP server (stdio): lint OpenAPI specs with Spectral via the AgentForge API

25 installs/wk answering

Fetch Extract

by cedrickouma

MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

26 installs/wk answering

URL Alive Check

by cedrickouma

MCP server (stdio): check if URLs are alive (status, redirects, latency) via the AgentForge API

25 installs/wk answering

MCP Podman

by crunchtools

MCP server for Podman container management via the Podman REST API

84 installs/wk local only

Rlg MCP

by sebastienrousseau

MCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio.

local only

OpenSTAAD MCP Server

by bentleysystems

MCP server for Bentley STAAD.Pro via the OpenSTAAD API

local only

Nerve Rpc

by reagost

MCP server for Nerve blockchain JSON-RPC & REST API for AI Agents

51 installs/wk local only

JSON Repair — questions

Answers built from our own checks of this server.

Why is there no tool list for JSON Repair?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is JSON Repair working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 733 ms. The bar chart above shows every period we have measured.

How do I connect JSON Repair?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does JSON Repair need an API key?

Yes. Every time we knock, JSON Repair answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is JSON Repair?

It answers our handshake in 733 ms on average, which is faster than 16% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use JSON Repair?

The npm package agentforge-json-repair-mcp was installed 26 times in the last week. Week over week that is +32%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.