Serverdex Tools

MCP server.json validator

Before you publish an MCP server to the official registry, paste its server.json here. It's checked against the official registry schema (2025-12-11) — right in your browser, nothing is uploaded — so you catch the problems that get a submission rejected first.

The mistakes it catches

description is too long

It must be 100 characters or fewer. Long marketing blurbs are the most common rejection.

missing version at the root

The top-level version is required and is separate from a package's version — easy to forget.

transport left off a package

Every entry in packages needs transport, even for a local stdio server: {"type": "stdio"}.

version is "latest" or a range

Package version must be a concrete version. "latest" is rejected, and ranges like ^1.2.3 are discouraged.

name has the wrong shape

It needs exactly one slash, reverse-DNS style — e.g. io.github.you/my-server.

a remote without type and url

Each entry in remotes needs both a type (streamable-http or sse) and a url.

How it works

Validation runs against the official registry JSON Schema (2025-12-11), the same file the Model Context Protocol registry uses — not our own rules. The schema is permissive, so extra fields you add are fine; only real schema violations are reported.

Everything happens in your browser — your server.json never leaves the page. We update the pinned schema version as the registry publishes new ones.