feat: migrate MCP Registry identity to dev.zhenjia

[lifeodyssey]

What changed

• changes the canonical MCP Registry identity to dev.zhenjia/share-html
• adds the branded /agents website link while retaining the bot-safe workers.dev MCP endpoint
• switches publication to zhenjia.dev DNS authentication via a production Environment secret
• verifies the branded entry before deprecating every version of the legacy GitHub identity
• makes reruns safe for already-published, deprecated, and deleted Registry states
• pins the migration order and identity in regression tests

Why

The Registry namespace should represent the product domain rather than the repository owner. The old identity cannot be unpublished, so the workflow performs an ordered namespace migration: publish and verify the branded identity first, then mark the legacy identity deprecated with a migration message.

Validation

• npm test — 508 passed
• npm run typecheck
• npm run build
• npx wrangler deploy --dry-run
• actionlint .github/workflows/publish-mcp.yml .github/workflows/ci.yml
• official mcp-publisher v1.7.9 validate server.json
• git diff --check

Summary by CodeRabbit

• New Features

  • Added a branded MCP Registry identity and agent-facing website link.
  • Updated discovery metadata to reflect the new registry identity.
  • Enhanced publishing verification and migration handling for legacy registry entries.

• Documentation

  • Updated publishing instructions, authentication details, migration guidance, and security warnings.

• Tests

  • Added coverage for branded metadata and publishing workflow requirements.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6197dbe7-c402-413b-bb85-3df8f0520095

📥 Commits

Reviewing files that changed from the base of the PR and between 8f1d741 and 203790d.

📒 Files selected for processing (6)

• .github/workflows/publish-mcp.yml
• README.md
• server.json
• src/worker/discovery.ts
• tests/discovery.test.ts
• tests/worker-index.test.ts

---

📝 Walkthrough

Walkthrough

The MCP Registry identity changes from io.github.lifeodyssey/share-html to dev.zhenjia/share-html, with a new agents URL. Publishing now authenticates the branded namespace, verifies the published record, and deprecates the legacy registry identity.

Changes

MCP Registry identity and publishing

Layer / File(s)	Summary
Branded manifest contract server.json, src/worker/discovery.ts, tests/discovery.test.ts, tests/worker-index.test.ts	Manifest metadata and runtime discovery output use dev.zhenjia/share-html and the /agents website URL; tests assert the updated values.
Publish and legacy migration workflow .github/workflows/publish-mcp.yml, README.md, tests/discovery.test.ts	The workflow authenticates and verifies the branded entry, deprecates legacy versions, and validates the migration sequence; documentation describes the new credentials and confirmation flow.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant DNS
  participant MCPPublisher
  participant RegistryAPI
  GitHubActions->>RegistryAPI: Inspect branded entry
  GitHubActions->>DNS: Validate namespace key
  GitHubActions->>MCPPublisher: Authenticate and publish branded metadata
  MCPPublisher->>RegistryAPI: Create or update branded record
  GitHubActions->>RegistryAPI: Verify active latest record
  GitHubActions->>MCPPublisher: Authenticate for legacy migration
  MCPPublisher->>RegistryAPI: Deprecate legacy versions
  GitHubActions->>RegistryAPI: Verify legacy records are deprecated or deleted

Loading

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/branded-mcp-registry

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →