Repository navigation
docs: pull registry docs from v1.8.9 - #3480
Merged
Merged
Conversation
e689ee49 docs(publishing): troubleshooting for DNS/HTTP auth (#845) (#1268) b4a16a72 docs(auth): document HTTP verification requirements and pin them with tests (#1640) 5784f684 docs(security): pin and verify mcp-publisher installer (#1523) d563b0cc fix(publish): correct misleading org-namespace guidance in 403 and docs (#1483) 65d479fa docs: clarify remote-only ownership verification (#1687) 652709d0 docs(quickstart): document remote-only publishing (#1674) fbe5f375 docs: fix copy-paste path in publishing quickstart (#1665) 3b8f5f20 docs: carry two modelcontextprotocol.io fixes back upstream (#1590) 8f0a0cc7 fix(publisher): document --algorithm for ECDSA login and fix validate --help (#1519) 94cc105c docs(auth): document fine-grained PAT permission for org publishing (+ pagination-cap test) (#1435) ee23fd41 fix(auth): grant org namespace only to org Owners, not all members (#1383) 7ffd3fd8 fix(validators): harden mcp-name matching (PyPI/NuGet anchoring, comment-form safe) + cargo follow-ups (#1331) 6ae8514d feat: add cargo (crates.io) as a package registry type (#1207) d8dc7e5b docs(authentication): note OpenSSL 3.x requirement for Ed25519 (#1253) 93278274 docs: document GitHub OIDC audience binding for self-hosters and CI users (#1230) 89e5614c fix(auth): better DNS verification errors and wrong-selector hint (#1202) 68e249aa feat(oci): add support for Quay.io registry (#1150) 75a4f44f docs: signpost non-npm publishers to package-types from quickstart (#1192) f3e6fb47 Remove `.mdx` suffixes from internal doc links for Mintlify (#1052) cc3a05ad Publisher-managed "deleted" support (#893) 4c8f889b update schema url point to the actual location (#884) git-subtree-dir: docs/registry git-subtree-split: e689ee493a162ded1081c3de93aa4396c2889f89
…l-registry-docs-v1.8.7
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
…l-registry-docs-v1.8.7
claude
Bot
changed the title
dsp-ant
approved these changes
Nov 11, 2026
dsp-ant
enabled auto-merge (squash)
November 11, 2026 19:40
dsp-ant
disabled auto-merge
November 11, 2026 20:25
This branch was successfully deployed
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
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.
Requested by Den Delimarsky, David Soria Parra · Slack thread
Squash-merge with this description as the commit message. The two trailers on the last lines must stay in it, so that the next subtree pull starts from this one.
Before:
docs/registry/reflects the registry docs as of 2026-01-22 (registry commit 817e1216), plus six local edits made since. The FAQ says servers cannot be deleted, the P-384 login command lacks the--algorithmflag, the organization namespace rules are missing, and the remote servers page says a remote URL can be used by only one server name.After:
docs/registry/is byte-identical todocs/modelcontextprotocol-ioin modelcontextprotocol/registry at tagv1.8.9(commit ba94f657). Seven pages change (+308/-25): authentication, faq, github-actions, package-types, quickstart, registry-aggregators and remote-servers.How
scripts/pull-registry-docs.shwas run against a clone of the registry, first atv1.8.7and then atv1.8.9. The script splitsdocs/modelcontextprotocol-ioand squash-pulls the result intodocs/registry/.npm run preppasses, link check included.The
v1.8.9pull adds two upstream changes. Sincev1.8.8several server names can share one remote URL (modelcontextprotocol/registry#1806), which replaces the sentence at remote-servers.mdx L41. The aggregators page gains an "Efficient synchronization" section (modelcontextprotocol/registry#1798).A later run of the script was tested against a single squash commit that carries these trailers. It merged cleanly and changed only
docs/registry/.Conflict resolutions
Three files conflicted in the
v1.8.7pull. In each case upstream had added content next to a line that a local commit had also touched, and upstream already carried the local change, so upstream's side was taken. Thev1.8.9pull had no conflicts.github-actions.mdx: new troubleshooting row for the"invalid audience"error.package-types.mdx: new paragraph on themcp-name:token boundary, placed before the Cargo section that both sides carry identically.quickstart.mdx: the npm account prerequisite reworded to apply to package-based servers only.Local commits since January
All six are carried by upstream, so nothing needs to go upstream.
.mdxsuffixes from internal links. Upstream did the same in Remove.mdxsuffixes from internal doc links for Mintlify registry#1052, and no suffixed links remain there.draft/server.schema.json. Upstream has it from update schema url point to the actual location registry#884.PyPitoPyPIin the FAQ. Upstream has it at faq.mdx L55.Upstream follow-ups for the registry repo (not fixed here)
authentication.mdxcontradicts itself on stale DNS records. L81 says a stale TXT record left behind "will be tried first and cause verification to fail". L404 says the registry tries all published keys and a different key in another record does not take precedence. The code agrees with L404:VerifySignatureWithKeysininternal/api/handlers/v0/auth/common.goaccepts the first matching key and fails only when none match.quickstart.mdxL130 and L134 installmcp-publisherfromreleases/latest, whilegithub-actions.mdxL14-17 tells readers not to use that URL. The three workflow examples ingithub-actions.mdx(L35, L115, L191) pinMCP_PUBLISHER_VERSION: v1.8.1, behind thev1.8.9tag.registry-aggregators.mdxL78 still says a"deleted"status typically indicates a moderation takedown. Since publisher-managed deletion (Publisher-managed "deleted" support registry#893) publishers set that status themselves.moderation-policy.mdxalso needs attention. Neither passage has changed upstream.This PR was drafted with AI assistance (Claude Code).
git-subtree-dir: docs/registry
git-subtree-split: 5d7060497a1d4535dc448dd56ec699ea03c89efd