JSON to Types MCP server
online · 100% uptimeConvert JSON samples into TypeScript interfaces and Zod schemas, with inference caveats.
Little public usage data yet
Reviews
Write oneNobody has reviewed JSON to Types yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
JSON to Types tools (1)
write = sends, deletes, buys or postsjson_to_typesFreeConvert a JSON sample into TypeScript interfaces and a matching Zod schema, and report where a single sample cannot establish the real type. Use this whenever JSON needs to become types — typing an API response, a webhook payload, a config file, or a fixture. Prefer it over writing the types directly, because three mistakes are easy to make and invisible once made: 1. ARRAYS. Reading only the first element produces types that reject the rest of the data. This merges every element into a union. 2. NULL VS ABSENT. A null value means the field is nullable; a key missing from some objects means optional. Different types, routinely conflated. 3. EMPTY CONTAINERS. Nothing can be inferred from [] or {}. This emits unknown and says so instead of inventing a plausible shape. It is also far cheaper in output tokens than generating types inline for a large payload, and the result is deterministic. Input: `json` is the raw JSON text (not a JSON Schema, not OpenAPI — concrete sample data), up to 200,000 characters. `rootName` optionally names the top-level interface and defaults to "Root". Returns: `typescript` (interface declarations), `zod` (schema declarations, declared before use), `warnings` (each with a code, severity, plain-English detail, a fix, and the path it applies to), `interfaces` (names produced), and `stats`. Read the warnings before trusting the output — they are the part a model generating types inline cannot give you.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1466ms20/20
- Tool poisoning1 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancerepository not readable: repo not found3/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How JSON to Types compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,243 servers
- Tools
- 1
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,054 ms
- faster than 12% of 30,027 servers
What its tools let an agent do: 1 read
Install JSON to Types in Claude Code, Cursor or VS Code
claude mcp add --transport http json-to-types https://json-to-types.gumballtools.com/api/mcp
Grade history
- 2026-10-16restoreC → Bscore 75
JSON to Types: common questions
- Is JSON to Types MCP server safe?
- Mostly: it is graded B (75/100). Read the JSON to Types safety report
- How do I install JSON to Types?
- It runs remotely at json-to-types.gumballtools.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does JSON to Types need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is JSON to Types maintained?
- The latest release is v0.1.0.
- Is JSON to Types up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does JSON to Types compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,243 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.