You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e2397a6
Browse filesBrowse the repository at this point in the historyBrowse files
Allow remote URLs to be shared across server names (#1806)
A publisher can currently block an endpoint's operator from listing it
under their own namespace simply by registering the remote URL first.
The registry authenticates namespaces but does not verify remote URL
ownership, so registration order cannot establish the canonical
publisher.
This change allows different server names to reference the same remote
URL on both `/v0` and `/v0.1`. It removes the conflict check from
publication, admin metadata edits, single-version restores, and
all-version restores. Namespace authorization, URL validation,
name/version uniqueness, and per-name version history remain intact.
Existing records, response schemas, and database indexes are unchanged;
no data migration is needed. The existing `remotes_ms` log field is
retained at zero.
The original uniqueness rule accompanied namespace/hostname matching in
#180 and #306; #769 later removed hostname matching.
## Downstream compatibility
This changes a previously documented behavioral guarantee, even though
the API shape is unchanged. Consumers that use a remote URL as a unique
key, or resolve it to a single canonical listing, must support multiple
matching server names. Records should be keyed by name/version (and
registry when combining sources), with each listing's metadata, headers,
and template variables kept separate. A shared endpoint does not
establish publisher ownership or endorsement.
The publishing guide and changelog explain this change. Review the
compatibility implications and coordinate rollout with downstream
consumers. Re-enabling uniqueness after shared URLs have been accepted
could block those servers' subsequent publications, edits, and restores.
Discovery grouping and endpoint ownership verification are outside this
PR.
## Validation
Updates the indirect `github.com/klauspost/compress` dependency from
v1.20.1 to v1.20.2 to fix GO-2026-6865, which was reported by CI's
vulnerability scan. Local `govulncheck ./...` and the CI vulnerability
scan pass with the update.
- Added database-backed regressions for independent metadata, version
histories, latest-only pagination, encoded listings, admin edits, and
single/all-version restores to active or deprecated.
- Added HTTP publish coverage on both API versions proving shared URLs
succeed while unauthorized namespaces, duplicate name/version pairs, and
invalid remote URLs still fail.
- Confirmed the new publication, edit, and active-restore regressions
fail against the original service implementation and pass with this
change.
- Passed `go test -race -coverprofile=coverage.out -covermode=atomic
./internal/... ./cmd/...` using an isolated local PostgreSQL 17
instance.
- Passed `make lint` with golangci-lint v2.14.0, `make validate build`,
and `git diff --check`.
- CI passed all checks, including `make test-all` (with Docker/ko
integration tests), build/lint/validation, vulnerability scanning, and
CodeQL. The Docker/ko integration harness was not run locally.
---------
Co-authored-by: Copilot Autofix powered by AI <[email protected]>
Copy file name to clipboardExpand all lines: docs/modelcontextprotocol-io/remote-servers.mdx
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,9 @@ When you publish, the Registry verifies that you control the namespace in the se
38
38
39
39
If your remote URL is on a domain you control, consider using DNS or HTTP authentication so the server name reflects that domain. This lets users see that the server name and remote URL belong to the same publisher.
40
40
41
-
Each remote URL can be used by only one server name. Publishing fails if another server already uses the same URL.
41
+
Multiple server names can reference the same remote URL. An existing listing does not reserve that URL or prevent another publisher from listing it under a namespace they control. Sharing a URL does not grant permission to publish, edit, or change the status of another publisher's listing.
42
+
43
+
Consumers should identify registry records by server name and version, not by remote URL. A URL lookup may match multiple server names, each with its own metadata, headers, and template variables. Do not merge configurations or infer publisher ownership or endorsement from a shared URL.
Copy file name to clipboardExpand all lines: docs/reference/api/CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,16 @@ Changes to the REST API endpoints and responses.
4
4
5
5
## Unreleased
6
6
7
+
### ⚠️ BREAKING CHANGES
8
+
9
+
#### Remote URLs may be shared across server names
10
+
11
+
The official registry no longer rejects publishing, admin metadata edits, or restoring deleted versions because another server name references the same remote URL. This applies to both `/v0` and `/v0.1`. Namespace authorization, remote URL validation, and uniqueness of server name/version pairs remain unchanged. Existing records and API response schemas are unchanged; no data migration is required.
12
+
13
+
**Downstream compatibility:** This relaxes a previously documented publishing restriction and changes the guarantee that a remote URL belongs to only one server name. Consumers that index records by remote URL or select a single canonical listing from a URL must support multiple matching server names. Identify records by server name and version (and registry when combining sources), and preserve each listing's metadata and configuration separately. A shared URL does not establish ownership or endorsement.
14
+
15
+
Operators should communicate this change to downstream consumers before rollout. Re-enabling the restriction after shared URLs have been published could block subsequent publications, edits, or restores for those servers.
0 commit comments