MCP-REG-004
Declared remote endpoint matches the probed URL
“A remote server MUST be publicly accessible at its specified URL.” — spec anchor
How to fix this
Make sure the remote endpoint declared in `server.json` is the URL the server is actually reachable at. A remote server must be publicly accessible at the URL it advertises.
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-003version is present and valid semver