mcp-registry/dev.fly.json-canon-x402/json-canon · v0.2.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs 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.
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
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 →
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 →
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 →
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
{
"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)"
}{
"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)"
}{
"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 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.
csv_to_json ~374 tokenspdf_tables ~363 tokenspdf_text ~280 tokensvalidate_json ~243 tokensjson_patch ~229 tokensStatic 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fdev.fly.json-canon-x402%2Fjson-canon?ref=badge)
<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>
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.
Compare: most reliable data servers · most reliable knowledge servers · most reliable finance servers · most reliable files servers
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.
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"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
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.
JSON Canon MCP server advertises 10 tools, including csv_to_json, get_pricing, json_diff, json_patch, mx_clabe.
Point your MCP client at this streamable-http endpoint: https://json-canon-x402.fly.dev/mcp
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.
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.