MCP-REG-002
Namespace ownership is verifiable (GitHub or DNS TXT)
“Publishers must verify ownership of their namespace through GitHub, DNS, or HTTP challenges, preventing arbitrary spam submissions.” — spec anchor
How to fix this
TODO: verify against the live registry publishing docs before launch.
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-003version is present and valid semver
- MCP-REG-004Declared remote endpoint matches the probed URL