Convert JSON samples into TypeScript interfaces and Zod schemas, with inference caveats.

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 859 ms, 95th percentile 1,031 ms.

When we called tools/list it returned 1 tool, including json_to_types, over MCP protocol revision 2025-11-25.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 9% and higher on readiness than 38%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (1)

As returned by the server's own tools/list when we called it.

json_to_types: Convert 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…

MCP readiness

B · 78/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 80.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1297 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	5/10	Lists 1 tool(s) with descriptions.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1297 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-12.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness: Higher than 38% of peers; This listing 78 · peer median 81
Latency: Faster than 9% of peers; This listing 1,011 ms · peer median 349 ms

Where it loses the most points, and how to win them back

Tool declaration −5 — Declare every tool with a description and input schema.
Now: Lists 1 tool(s) with descriptions.
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-09-07 wellknown since 2026-09-23 ↗ agenstry since 2026-10-22 ↗ capkey since 2026-10-26 ↗

How to connect

MCP endpoint (streamable-http)

https://json-to-types.gumballtools.com/api/mcp

JSON-RPC initialize probe

curl -X POST https://json-to-types.gumballtools.com/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://json-to-types.gumballtools.com

Source code

https://github.com/bwalvoord/gumball