docs: clarify remote-only ownership verification - #1687
Merged
Merged
Conversation
Follow-up to #1674. - Document in remote-servers.mdx that no authentication method verifies control of the remote URL, and that each remote URL can belong to only one server name - Note that `mcp-publisher init` always generates a `packages` entry that remote-only servers must replace with `remotes` - Tell remote-only publishers they can skip the Node.js prerequisite - Drop the duplicate description-length note from the remote-only section Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #1674, covering the remaining gaps from #1656.
remote-servers.mdx: new "Ownership Verification" section. The Registry verifies control of the namespace inname, but no authentication method (GitHub, DNS, HTTP) verifies control of the remote URL. Suggests DNS/HTTP authentication when the URL is on a domain you control. Also documents that each remote URL can belong to only one server name (validateNoDuplicateRemoteURLs).mcp-publisher initalways generates apackagesentry (it defaults to npm), which remote-only servers must replace withremotes.descriptionnote. The Step 4 note remains, and remote-only readers pass through Step 4.Validation
go run tools/validate-examples/main.gogit diff --check