Skip to content

chore(connector): record the published registry version 0.1.0 - #14

Merged
jiashuoz merged 1 commit into
mainfrom
chore/connector-registry-version
Sep 4, 2026
Merged

chore(connector): record the published registry version 0.1.0#14
jiashuoz merged 1 commit into
mainfrom
chore/connector-registry-version

Conversation

@jiashuoz

@jiashuoz jiashuoz commented Sep 4, 2026

Copy link
Copy Markdown
Member

What

The MCP Registry entry has been corrected. run.agentdrive/agentdrive 0.1.0 is live and serves the canonical transport:

https://drive.mcp.tokencanopy.com/mcp

#13 fixed the URL in connector/server.json but left version at 0.0.1. The registry will not accept a republish without a version bump, so the publish went out as 0.1.0 and this file fell a version behind. This brings them back into agreement — it is a one-line change.

Registry state, verified live

v0.0.1  latest=False  status=deprecated  -> https://api.agentdrive.run/mcp
v0.1.0  latest=True   status=active      -> https://drive.mcp.tokencanopy.com/mcp

A default ?version=latest lookup returns only 0.1.0.

0.0.1 was deprecated rather than deleted: it's a real historical version, and deprecating it stops a version-pinned client resolving a host that no longer exists (api.agentdrive.run is NXDOMAIN).

Note for future readers

Editing this file does not publish anything. The live listing is updated with mcp-publisher, authenticated by a DNS-verified key on the namespace's domain — which for run.agentdrive/* means a TXT record on agentdrive.run, a domain that has otherwise been retired. That coupling is the argument for eventually moving the namespace to com.tokencanopy/agentdrive; it is not addressed here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv

The MCP Registry entry was corrected on 2026-09-04. `run.agentdrive/agentdrive`
0.1.0 is now live and serves the canonical transport:

  https://drive.mcp.tokencanopy.com/mcp

PR #13 fixed the URL in this file but left `version` at 0.0.1, which the
registry will not accept as an update — a republish needs a new version. The
publish therefore went out as 0.1.0 and this file was left behind it. Bring
them back into agreement.

The previous 0.0.1 entry, which pointed at the retired `api.agentdrive.run/mcp`
(NXDOMAIN), is now marked `deprecated` in the registry rather than deleted: it
is a real historical version, and deprecating it keeps a version-pinned client
from resolving a dead host. A default `version=latest` lookup returns only
0.1.0.

Note that editing this file does not itself publish anything. The live listing
is updated by `mcp-publisher`, authenticated by a DNS-verified key on the
namespace's domain.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01W1nxC2LaqTPrix7CL4Ehuv
@jiashuoz
jiashuoz merged commit f972d0a into main Sep 4, 2026
4 checks passed
@jiashuoz
jiashuoz deleted the chore/connector-registry-version branch September 4, 2026 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant