Remove outdated remote server URL match caveat

Follow-up to modelcontextprotocol#769, which removed the validation that remote server URLs
must match the server's namespace.

This commit updates `official-registry-requirements.md` to reflect the
current behavior.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: jonathanhefner

docs/reference/server-json/official-registry-requirements.md

@@ -10,7 +10,6 @@ While the [generic server.json format](./generic-server-json.md) defines the bas
 
 - **Namespace authentication** - Servers are published under appropriate namespaces
 - **Package ownership verification** - Publishers actually control referenced packages
-- **Remote server URL match** - Remote server base urls match namespaces
 - **Restricted registry base urls** - Packages are from trusted public registries
 - **`_meta` namespace restrictions** - Restricted to `publisher` key only
 
@@ -26,10 +25,6 @@ All packages must include metadata proving the publisher owns them. This prevent
 
 For detailed verification requirements for each registry type, see the [publishing guide](../../guides/publishing/publish-server.md).
 
-## Remote Server URL Match
-
-Remote servers must use URLs that match the publisher's domain from their namespace. For example, `com.example/server` can only use remote URLs on `example.com` or its subdomains.
-
 ## Restricted Registry Base URLs
 
 Only trusted public registries are supported. Private registries and alternative mirrors are not allowed.