Developer · Remote MCP server
Jsonaut
Repair malformed JSON from LLM/agent output; optional JSON Schema coercion. Free + x402 paid.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.shoggi211/jsonaut- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-02
- Updated
- 2026-07-02
- Publisher
- shoggi211 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/shoggi211) · how
- Website
- jsonaut.jsonaut-shaurya.workers.dev
- Repository
- github.com/shoggi211/jsonaut
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://jsonaut.jsonaut-shaurya.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- jsonaut 0.1.0 · protocol 2025-06-18
- Tools discovered
- 4:
repair_json,validate_json,extract_json,infer_schema - Checked on
- 2026-10-05
How to connect Jsonaut
Jsonaut is a remote MCP server: there is nothing to install. Its endpoint is https://jsonaut.jsonaut-shaurya.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| JshookmcpMCP server for JavaScript analysis, security auditing, browser automation and hooks. | Local · stdio |
| JSON ContractsJSON contract registry and validator for structured LLM and agent outputs. | Local · stdio |
| JSON Repair & Agent UtilitiesRepair malformed JSON, DNS lookup, extract URLs, base64, case, hash, time. Pay per call USDC Base. | Remote · HTTPLive check: ✗ no handshake |
| JSON to TypesConvert JSON samples into TypeScript interfaces and Zod schemas, with inference caveats. | Remote · HTTPLive check: ✓ handshake |
| JsonFabricaGenerate realistic, relational synthetic JSON test data from templates, via the JsonFabrica API. | Local · stdio |
| JSONPad documentationJSONPad docs, API, SDK and CLI references, and offline checkers for write rules and flows. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| JSONShelfDeterministic JSON repair, validate, example-gen, schema-coerce for agents. Zero LLM, sub-10ms. | Remote · HTTPLive check: ✓ handshake |
| jsonshimRecovers malformed LLM JSON. MCP build: 218/300 on MALFORMED-300 (library build 282/300). | Local · stdio |