Json Repair Mcp

io.github.grupoanesthy-specPublished by GitHub account grupoanesthy-specv1.0.1Updated Oct 25, 2026

Repairs malformed JSON from LLM output, validated against a schema. Paid per call via Stripe.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that repairs malformed JSON from LLM output and validates it against a schema, using a paid hosted API.

What you can do
Repair malformed JSON produced by LLM output so it can be parsed again, with the result validated against a schema you supply. Calls are routed to a hosted repair API, whose base URL can be overridden. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant or pipeline regularly receives broken JSON from model output and you want an automatic repair-and-validate step rather than manual fixing.
Requirements
Runs as a local npm package over stdio on a desktop machine. Requires an API key in the JSON_REPAIR_API_KEY environment variable, obtained through a signup flow, and network access to the hosted API. The API base URL can be set with JSON_REPAIR_API_URL and otherwise defaults to the production endpoint.
Before you install
The service is paid per call via Stripe, and signup goes through Stripe Checkout, so usage can incur charges. The API key is a secret sent to a third-party hosted API, and the JSON content you submit is processed by that external service. Review cost and data handling before sending sensitive payloads.

Installation

In SourceWeft

  1. Open Json Repair Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.