chore(connector): migrate the registry namespace to com.tokencanopy - #1
Merged
Merged
Conversation
The listing moved from `run.agentdrive/agentdrive` to `com.tokencanopy/agentdrive`, published 2026-09-04 at 0.1.0 and serving the same endpoint, https://drive.mcp.tokencanopy.com/mcp. The old namespace was rooted in `agentdrive.run`, a retired domain. Because registry auth is DNS-verified against the namespace's domain, every future update to that entry would have required keeping a domain alive whose only remaining job is a 301 — so the namespace, not just the URL, had to move before the zone could ever be released. Two things learned doing it, both recorded in AGENTS.md because they are not obvious and they invert the migration order: A remote URL may be claimed by exactly ONE server name. Publishing the new namespace alongside the old fails with `remote URL ... is already used by server run.agentdrive/agentdrive`. Deprecating does NOT release that claim — only deletion does. So a namespace migration is delete-then-publish, and the delete is the irreversible step. It is not publish-then-deprecate, which is what you would reach for by default. `run.agentdrive/agentdrive` is now deleted at both versions. An unrelated `sh.agentdrive/agentdrive` operated by someone else remains in the registry at a different endpoint; the docs now name it so the two are not confused. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv
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.
What
The MCP Registry listing moved from
run.agentdrive/agentdrivetocom.tokencanopy/agentdrive, published 2026-09-04 at0.1.0, serving the same endpoint:This syncs
connector/server.json,AGENTS.md, anddocs/add-to-your-agent.mdto that.Why
The old namespace was rooted in
agentdrive.run— a retired domain whose only remaining job is a 301 to the marketing site. Registry auth is DNS-verified against the namespace's domain, so every future update to that entry would have required keeping that zone alive. The namespace, not just the URL, had to move before the domain could ever be released.It also disambiguates from an unrelated
sh.agentdrive/agentdriveoperated by someone else at a different endpoint.com.tokencanopyties the listing to the domain that actually serves it.Two constraints learned doing this
Both are recorded in
AGENTS.md, because they invert the migration order you'd reach for by default:run.agentdrive/agentdrive0.1.0and retrying the publish failed identically.So a namespace migration is delete-then-publish, and the delete is the irreversible step.
active ↔ deprecatedround-trips cleanly (also verified), which is what made it safe to test the deprecation path first and revert.Verified end state
run.agentdrive/agentdriveis deleted at both versions and no longer appears in search.🤖 Generated with Claude Code
https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv