Is the JSON Canon MCP server down?

mcp-registry/dev.fly.json-canon-x402/json-canon · v0.2.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:58 UTC · handshake 329ms

As of 2026-11-22 16:58 UTC, the JSON Canon MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
460
outages (90d)
0
tools
10

Pay-per-call x402 tools (USDC/Base): JSON validate, CSV, diff, PDF, Mexican RFC/CURP/CLABE.

Point your MCP client at this streamable-http endpoint: https://json-canon-x402.fly.dev/mcp

Agent-readiness: B (86/100)

B (86/100): 0 error(s), 2 warning(s) across 10 tool(s); ~2,233 tokens of tool definitions.
Scores higher than 43% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~2,233 tokens per session — more than 55% of servers.
86 → 86 since 2026-11-19
no tool-poisoning patterns
Descriptions69
Safety hints100
Schemas75
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (3)

3 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →

Tools: json_diff, json_patch, validate_json

3 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: csv_to_json, pdf_tables, pdf_text

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.fly.json-canon-x402%2Fjson-canon/fixes

json_diff 1 change
{
  "name": "json_diff",
  "description": "Compare two JSON documents and return the RFC 6902 JSON Patch that turns source into target, plus canonical SHA-256 of each side. Price: 0.01 USDC per successful call on Base via x402 (pass the signed payment in _meta['x402/payment']; failed calls are not charged). HTTP equivalent: POST https://json-canon-x402.fly.dev/v1/json-diff.",
  "inputSchema": {
    "type": "object",
    "required": [
      "source",
      "target"
    ],
    "properties": {
      "source": {
        "description": "Original JSON value (any type).",
        "type": "string"
      },
      "target": {
        "description": "New JSON value (any type).",
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "JSON diff (RFC 6902 patch)",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "JSON diff (RFC 6902 patch)"
}
json_patch 1 change
{
  "name": "json_patch",
  "description": "Apply an RFC 6902 JSON Patch to a JSON document and return the result and its canonical SHA-256. Failed 'test' ops return 409 and are not charged. Price: 0.01 USDC per successful call on Base via x402 (pass the signed payment in _meta['x402/payment']; failed calls are not charged). HTTP equivalent: POST https://json-canon-x402.fly.dev/v1/json-patch.",
  "inputSchema": {
    "type": "object",
    "required": [
      "document",
      "patch"
    ],
    "properties": {
      "patch": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "op",
            "path"
          ],
          "properties": {
            "op": {
              "type": "string"
            },
            "from": {
              "type": "string"
            },
            "path": {
              "type": "string"
            },
            "value": {}
          }
        },
        "description": "RFC 6902 operations (add, remove, replace, move, copy, test). Max 10,000."
      },
      "document": {
        "description": "JSON value to patch (any type).",
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Apply JSON Patch (RFC 6902)",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Apply JSON Patch (RFC 6902)"
}
validate_json 1 change
{
  "name": "validate_json",
  "description": "Validate a JSON instance against an optional JSON Schema and return RFC 8785 canonical JSON plus SHA-256. Price: 0.01 USDC per successful call on Base via x402 (pass the signed payment in _meta['x402/payment']; failed calls are not charged). HTTP equivalent: POST https://json-canon-x402.fly.dev/v1/validate.",
  "inputSchema": {
    "type": "object",
    "required": [
      "instance"
    ],
    "properties": {
      "schema": {
        "type": "object",
        "description": "JSON Schema to validate instance against. Optional. If omitted, the instance is accepted and only canonicalized.",
        "additionalProperties": true
      },
      "instance": {
        "description": "JSON value to validate. Any JSON type is accepted.",
        "type": "string"
      },
      "canonicalize": {
        "type": "boolean",
        "default": true,
        "description": "If true (default), return RFC 8785 JCS canonical JSON, its SHA-256 hex digest, and byte length."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Validate + canonicalize JSON",
    "readOnlyHint": true,
    "openWorldHint": false,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Validate + canonicalize JSON"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.fly.json-canon-x402/json-canon"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.fly.json-canon-x402/json-canon"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fdev.fly.json-canon-x402%2Fjson-canon.svg)](https://glimind.com/server/mcp-registry%2Fdev.fly.json-canon-x402%2Fjson-canon?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.fly.json-canon-x402%2Fjson-canon?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fdev.fly.json-canon-x402%2Fjson-canon.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:eb8807da2aabc736…, first seen 2026-11-19, included at leaf 342869 of 384,678. Version history · verify what your client received.

Tools (10)

Compare: most reliable data servers · most reliable knowledge servers · most reliable finance servers · most reliable files servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the JSON Canon MCP server down right now?

As of 2026-11-22 16:58 UTC, the JSON Canon MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does JSON Canon MCP server provide?

JSON Canon MCP server advertises 10 tools, including csv_to_json, get_pricing, json_diff, json_patch, mx_clabe.

How do I install JSON Canon MCP server?

Point your MCP client at this streamable-http endpoint: https://json-canon-x402.fly.dev/mcp

Is the JSON Canon MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of JSON Canon MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve