The MCP registry checks a server.json against a schema and against proof of ownership. Name, version, description and package proof cause most refusals.
A server.json file is refused by the official MCP registry for two different kinds of reason. Some fields fail the published JSON Schema: a description that is too long, a version written as a range, a name with the wrong shape. Others pass the schema and then fail a check the registry runs at publish time, which asks whether the person publishing really controls the name and the package. The first kind can be caught with a validator. The second kind needs a look at the package itself, and it is where most of the confusion lives. This guide goes through both, field by field, so a file can be checked before the publish command is run.
Read the full report on AISkills402: https://aiskills402.com/blog/mcp-registry-server-json-fields?utm_source=devto&utm_medium=social
Top comments (0)