Skip to main content

​
E-MCP-004

what doctor prints (broken)server.json is invalid: <the exact schema errors doctor found>
Your repo has published a server.json, and it fails validation against the MCP registry’s schema. check mcp/server-json · error_code E-MCP-004 · doctor exits 1

​
What you’re seeing

Doctor only runs this check when your composition opens the MCP door and a server.json file exists at the repo root — a project with no MCP door is never graded on a file of that name. server.json is the official MCP registry artifact: the document that lets a registry list your door as a discoverable server.

​
Why

Doctor parses the file and validates it against the registry’s schema. Every field the schema rejects is named in the printed message, one after another, so the line after server.json is invalid: is never generic. A file that predates a schema change, or one hand-edited into an invalid shape, fails here.

​
The fix

Regenerate the file from the live door instead of hand-patching individual fields:
If you maintain server.json by hand, fix the fields the message lists and re-run doctor.

E-MCP-005

server.json remote mismatch

E-MCP-006

server.json invalid JSON

E-MCP-003

server card