MCP-REG-003
version is present and valid semver
“The MCP Registry recommends semantic versioning, but supports any version string format.” — spec anchor
How to fix this
Give `version` in `server.json` a valid semantic version string. The registry accepts any format, but semver is what its tooling and its consumers expect.
How the validator checks this
This rule is catalogued from the specification but is not yet checked automatically. No probe emits a finding for it, so it never appears in a report as pass, warn or fail. It is documented here because it is a real requirement of the specification — it is simply not one this validator can confirm for you yet.
Check your own server against this rule
The validator makes real protocol requests and reports this rule as pass, warn or fail alongside the other 78. Validate a server or read how the check works.
Other Registry readiness rules
- MCP-REG-001server.json present and valid against the registry schema
- MCP-REG-002Namespace ownership is verifiable (GitHub or DNS TXT)
- MCP-REG-004Declared remote endpoint matches the probed URL