Menu

The server.json mistakes that get your MCP server rejected
📰

The server.json mistakes that get your MCP server rejected

DEV Community: webdev·Andrei·about 8 hours ago
#7JzVhmDZ
#devtowebdev#devto#dev#server#version
Reading 0:00
15s threshold

If you've published — or tried to publish — an MCP server to the official registry, you've met server.json , and the validation that quietly rejects it. The schema is small, but a handful of mistakes account for most of the failures. Here they are, checked against the current registry schema (2025-12-11).

The ones that actually trip people up

The description is too long. description is capped at 100 characters . A marketing paragraph is the single most common rejection — write one tight sentence.

No version at the root. The top-level version is required, and it's separate from a package's version. Easy to set the package version and forget the server one.

A package with no transport . Every entry in packages needs a transport — even a local stdio server:

{ "registryType" : "npm" , "identifier" : "@you/server" , "transport" : { "type" : "stdio" } }

Enter fullscreen mode

Exit fullscreen mode

People add it for HTTP remotes and leave it off stdio packages.

version is "latest" or a range.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.