Skip to content

FixMyJSON MCP server

io.github.tonbifun/fixmyjsontonbifunstreamable-httpv0.4.0Scanned

Repair broken LLM JSON and check it against a JSON Schema. Flags cut-off output. Free trial.

1 tool: 1 change things.

Tools: 0 delete, 0 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the FixMyJSON MCP server can do

The FixMyJSON MCP server is published by the GitHub account tonbifun. It has 1 tool. It can create or change data (1 tool: repair_json), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 7, 2026, version 0.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

1 tool

Changes things 1Claude Code: ask
  • repair_jsonRepair malformed JSON produced by an LLM or agent (trailing commas, missing quotes, code fences, chatty text around the JSON, <think> blocks, double-encoded JSON) and check the res…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Repair malformed JSON produced by an LLM or agent (trailing commas, missing quotes, code fences, chatty text around the JSON, <think> blocks, double-encoded JSON) and check the result against a JSON Schema. Returns the repaired value, what was changed, what could not be fixed (unresolved_errors), and `truncated: true` when the input looks cut off (e.g. by a token limit) so you can retry instead of trusting it. It never invents missing data. Free trial, no signup: 20 calls per client per day, 20000 characters per call.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 503.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fixmyjson https://fixmyjson-api.onrender.com/mcp
claude mcp add --transport http fixmyjson https://fixmyjson-api.onrender.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__fixmyjson__repair_json"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fixmyjson. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tonbifun/fixmyjson/verify?hash=85186480f615bb8dcc173e3912ff00a3cf55aaa8f3b13c00931f924071f7bf30" | jq -e '.changed == false'

Pinned hash 85186480f615, from Nov 7, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.tonbifun/fixmyjson/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.tonbifun/fixmyjson
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.tonbifun/fixmyjson.svg)](https://radar.anlyon.com/servers/io.github.tonbifun/fixmyjson)

Source: MCP Registry. Synced Nov 16, 2026, 05:18 UTC.

FixMyJSON MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FixMyJSON MCP server safe?

No scan can promise that. What its definitions show: 1 tool, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FixMyJSON MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FixMyJSON MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the FixMyJSON MCP server have?

1 tool: 1 write. repair_json.

Does the FixMyJSON MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the FixMyJSON MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FixMyJSON MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 7, 2026.